Testing, Evidence & Improvement
Show what the design achieves—and what each student has learned.
Start with a traceable requirement
A useful requirement identifies a measurable property, target, conditions, and verification method. “The device should be fast” is vague. “Under the agreed test conditions, the device shall complete a cycle within X seconds” can be tested once the team establishes a justified value for X.
Verification and validation
Verification asks whether the design meets its specified requirements. Validation asks whether it addresses the intended user need in the intended context. A laboratory test can support verification while leaving usability in actual operation unresolved.
| Record | What it should make clear |
|---|---|
| Requirements matrix | Requirement source, target, method, result, and status. |
| Test procedure | Equipment, calibration, conditions, sample plan, safety, and stopping rules. |
| Analysis | Baseline comparison, uncertainty, variation, exclusions, and limitations. |
| Decision log | What changed, why it changed, and the evidence behind the choice. |
| Final handoff | Operating limits, maintenance needs, outstanding issues, and permitted uses. |
Avoid overstating the result
A single successful run does not establish reliability. Select repeated trials appropriate to the question and report variation. Explain how measurement uncertainty affects a pass/fail decision near a threshold. A simulated result needs evidence that the model is appropriate for the intended use.
Assess learning separately from the product
A shared team report may not reveal individual understanding. Faculty can combine artifacts with individual questioning, design notebooks, peer feedback, and contribution records. External reviewers can offer useful perspectives, but faculty retain grading and assessment authority.
An adaptable educational rubric might distinguish incomplete, developing, proficient, and advanced work. Define those levels using observable evidence—for example, whether alternatives are merely named or quantitatively compared against justified criteria. Programs should set their own performance expectations and evaluation procedures.
Close the improvement loop
After the course, identify patterns: weak requirements, late purchasing, unsupported standards claims, or insufficient testing. Record a specific improvement, an owner, and when its effect will be reviewed. Archive evidence under university retention and privacy rules.
Download the verification matrix · Read the ABET alignment guide.