IA Day 16 —
Test Against All Specifications
Close the evidence gaps: the strongest Criterion D work evaluates the fidelity model against all design specifications and intended-user needs.
By the end of class, you should be able to…
Audit every specification
Find missing, weak or duplicated evidence.
Choose appropriate tests
Use performance data and intended-user testing where relevant.
Evaluate—not merely state
Explain what results mean relative to the requirement.
Close or acknowledge gaps
Strengthen the evidence without inventing results.
Evaluate the testing against all design specifications and intended-user needs.
That does not mean every requirement needs the same test. It means every requirement needs an appropriate, honest evidence trail.
| Spec | Priority | Evidence already collected | Strength | Action today |
|---|---|---|---|---|
| S1 | Essential | Performance test | Strong | None / verify |
| S2 | Essential | User comment only | Weak | Add task observation / metric |
| S3 | Desirable | None | Gap | Choose appropriate evidence |
Function / performance
Measured task results, loads, movement, fit, error count or other appropriate performance data.
Usability / ergonomics
Intended-user observation, task performance, reach/clearance/comfort evidence.
Aesthetics
Targeted user feedback, comparison to stated aesthetic requirement and visual evidence.
Manufacture / material / safety
Drawing/CAD/material evidence, justified constraints, relevant tests or limitations—depending on the specification.
“S2 passed.”
A conclusion with little visible reasoning.
Result → requirement → implication
Explain how the evidence compares with S2, what remains limited, and whether further refinement is needed.
The mini-lesson is short. The evidence-making is the lesson.
Mark strong / weak / missing evidence.
Start with essential requirements and intended-user needs.
Do not rely on memory—save measurements, photos and feedback.
Record what each result means and whether refinement is still required.
Every claim comes from a real test/source/observation.
No requirement disappears because it is inconvenient.
Intended-user evidence appears where appropriate.
A model limitation is explained rather than hidden.
Before you leave…
IA Day 17 — Formal Design Drawings for a Manufacturer
Keep the evidence chain moving: user → research → decision → test.
IA Criterion D highest-band descriptor: a fidelity model thoroughly addressing the problem statement that evaluates testing against all design specifications and the needs of the intended user. Design specifications should include relevant UX/user needs and other suitable attributes, components, constraints, environment, functions, safety, aesthetics and manufacture requirements.