Design Verification Test Plans: Proving Hardware Meets Its Requirements
By the time a design is ready for verification, the team usually believes it works. Verification is about proving it, requirement by requirement, under the stated conditions, with evidence someone else can review. The tool for this is a design verification test plan: a document listing each requirement, how it will be verified, the pass criteria and the result. This article explains how to build one that is complete without being unmanageable.
At a glance
- Traceable
- Every requirement links to at least one test, and every test links back to a requirement.
- Pass/fail
- Each test has an objective acceptance criterion written before the test is run.
- Worst case
- Tests cover the limits of supply, temperature and load, not just nominal conditions.
- 4 methods
- Inspection, analysis, demonstration and test: the standard ways to verify a requirement.
The problem
Testing without a plan tends to exercise what the team expects to work, at nominal conditions, on whichever units are available. It produces confidence but not evidence, and requirements that were never checked surface after release.
The other failure is a plan written after testing, with pass criteria chosen to fit the results. It satisfies a checklist but proves nothing, and experienced reviewers recognise it.
Write the pass criteria before you run the test. A criterion chosen afterwards is a description, not a verification.
Building the plan
Start from the requirements specification and give every requirement a verification method. Not everything needs a bench test: dimensions can be verified by inspection, a lifetime calculation by analysis, and a user feature by demonstration. Reserve formal testing for measurable performance.
For each test, record the setup, equipment, sample size, conditions and acceptance criterion. Test at the extremes the requirement states, such as minimum and maximum supply and temperature, because that is where margins run out.
What good looks like
Build a traceability matrix linking each requirement to its verification method, test procedure and acceptance criterion.
Review the plan with design engineers to confirm the conditions and criteria match the requirements and the equipment is available.
Run the tests on design-representative units, record results and deviations, and close the matrix with a verification report.
| Req ID | Requirement | Method | Acceptance |
|---|---|---|---|
| PWR-01 | Operate from 9 to 36 V DC | Test | Full function at 9 V and 36 V |
| ENV-03 | Operate from -20 to +60 °C | Test | Full function at both limits after soak |
| MEC-02 | Enclosure within 120 x 80 x 30 mm | Inspection | Measured dimensions within drawing |
| REL-01 | Battery life at least 12 months | Analysis | Life calculated from measured currents |
| UI-04 | Status shown at power-up | Demonstration | Indicator observed in each mode |
From requirement to report
- Requirement: Measurable and identified
- Method: Inspect, analyse, demonstrate or test
- Procedure: Setup, conditions, criterion
- Execution: Recorded results
- Report: Matrix closed, deviations resolved
What it changes
Complete Coverage
No requirement reaches release unverified.
Objective Evidence
Results can be reviewed by customers, auditors and test labs.
Known Margins
Worst-case testing shows how close the design is to its limits.
Controlled Changes
The matrix shows which tests to repeat after a design change.
Where to go next
Use calibrated equipment and record its identity with the results. Evidence from an unidentified instrument is weak evidence.
Keep verification separate from validation. Verification shows the design meets its requirements; validation shows the requirements meet the user’s needs.
Problems this prevents
- Requirements never checked before release
- Pass criteria chosen after the results
- Testing only at nominal conditions
- Unclear which tests to repeat after a change
Discuss your project
Email support@aavico.com or use Get in Touch when the website finishes loading.