Timedora
Free Online Flashcard Deck

Design Evaluation and Iteration Free Online Flashcards

Study Design Evaluation and Iteration with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

How should a team interpret an evaluation finding before acting on it?

Back

Record observations and measurements, identify the affected users, tasks, and evaluation conditions, then connect the findings to relevant needs, requirements, or design assumptions.

02
Front

How can a team compare design alternatives transparently?

Back

Compare alternatives using explicit criteria, such as accessibility, safety, feasibility, cost, or schedule, and explain trade-offs when an option improves one measure but weakens another.

03
Front

What should be defined before a design test begins?

Back

State the test question and prototype purpose, identify participants or conditions, and specify what evidence would support a decision.

04
Front

What does evidence-based design iteration do?

Back

Use test evidence to compare the design with user needs and requirements, choose changes, and test the revised design. The evidence may also show that the problem or a requirement needs refinement.

05
Front

How should a team choose a prototype for a test?

Back

Choose a prototype that fits the question: sketches can test understandability, mock-ups can test layout, and working prototypes can test performance or integration.

06
Front

What information makes a design decision traceable later?

Back

A decision log can preserve the decision date, problem addressed, evidence and limitations, alternatives and criteria, rationale and trade-offs, impacts, and unresolved risks or follow-up actions.

07
Front

What action can follow a contextualized evaluation finding?

Back

Decide whether to keep, revise, add, clarify, or remove a requirement; change the design; or gather more evidence. Define a test or analysis to check the chosen change.

08
Front

How can iteration change the definition of the problem?

Back

Iteration can expose requirements that are unclear, incomplete, or based on mistaken assumptions, allowing the team to improve both the solution and its understanding of the problem.

09
Front

When should stakeholders be included in a design decision?

Back

Include affected stakeholders when their needs or expertise are relevant to the decision.

10
Front

How should a team prioritize test findings?

Back

Prioritize findings by their effects on user needs, requirement compliance, safety, and project constraints. Select changes and check that they do not create problems elsewhere.

11
Front

What must a team consider when changing a requirement?

Back

Keep requirements clear, consistent with stakeholder needs, and verifiable. Record why they change and consider effects on related requirements, interfaces, safety, cost, schedule, and verification plans.

12
Front

When can a team stop iterating or move forward?

Back

Keep revising while important questions remain unresolved. Move forward when agreed criteria are met, remaining risks are acceptable, and further testing is unlikely to change the decision.