IA Day 13 —
Criterion D Launch
Plan the physical fidelity model and the multiple model–test–refine cycles that will turn your selected idea into the intended solution.
By the end of class, you should be able to…
Read Criterion D
Know what “develop a fidelity model” requires.
Plan the physical model
Choose fidelity based on the design questions.
Plan multiple cycles
Make testing and refinement visible over time.
Connect every test
Tie testing to specifications and intended-user needs.
You need a physical fidelity model for testing and evaluation.
Digital CAD, drawings and simulations can support the development process, but the guide explicitly requires a physical fidelity model as part of the design project.
Geometry
Foam/card/3D print can test size, reach, clearance or fit.
Interaction
A working mock-up can reveal grip, movement, confusion or errors.
Structure / performance
A physical model or suitable simulation can test load/deflection/strength assumptions.
Appearance / communication
CAD or higher-fidelity surfaces can support form, proportion and visual feedback.
| Specification | Design uncertainty | Model / test | Data to collect | User involved? | Decision rule |
|---|---|---|---|---|---|
| S1 | What might fail? | How will you test? | Measure / observe | Who? | What result triggers refinement? |
| S2 | What is unknown? | Appropriate fidelity | Evidence | How? | Pass / revise logic |
The mini-lesson is short. The evidence-making is the lesson.
Bring Criterion C into a clear starting point for D.
Map major specifications to a model/test and evidence type.
Materials, scale, functional features, tools, safety and user access.
Build only as much fidelity as needed to answer the first questions.
It can be tested with the intended user.
There is room for evidence-based change.
Every test has a reason.
You know what data / feedback to capture.
Before you leave…
IA Day 14 — Fidelity Model Build & Test: Cycle 1
Keep the evidence chain moving: user → research → decision → test.
IA Criterion D: develop and annotate iterative fidelity models through multiple testing and refinement cycles to arrive at the intended redesigned solution; test against design specifications and intended-user needs. The design project requires a physical fidelity model for testing and evaluation. B2.1.12–13: iterative model-test-refine and feasible models at appropriate fidelity generating performance data with end-users.