Engineers usually verify a design meets its technical requirements through a structured verification and validation (V&V) process that traces each requirement to evidence.
1) Start with clear, testable requirements
A requirement needs to be measurable (e.g., “withstand 2 kN load with factor of safety 1.5,” “latency < 50 ms,” “efficiency > 92% at 1 kW”). If it isn’t testable, engineers rewrite or refine it.
2) Create a requirements traceability matrix (RTM)
They map every requirement to one or more planned verification methods and later to the results. Typical verification methods are:
- Test (measure performance on hardware/software)
- Analysis (math/physics-based calculation, simulation)
- Inspection (visual/attribute check, dimensional checks)
- Demonstration (show function works without detailed measurements)
3) Build a verification plan and test procedures
This defines:
- What will be tested and at what conditions (normal, worst-case, edge cases)
- Instrumentation and calibration needs
- Sample size / repetitions and acceptance criteria
- Pass/fail thresholds and how data will be recorded
- Safety, quality, and configuration control (exact version of the design)
4) Use modeling and analysis early
Before full prototypes, teams often verify many requirements with:
- Hand calculations (stress, thermal, power budgets, timing)
- Simulation (FEA/CFD, circuit simulation, system models)
- Tolerance and sensitivity analyses
This helps catch issues cheaply and reduces the number of prototype spins.
5) Prototype and run bench/functional tests
Engineers then test real builds to confirm behavior matches requirements:
- Functional tests (does it do the required tasks?)
- Performance tests (throughput, strength, accuracy, range, efficiency)
- Environmental tests (temperature, vibration, shock, humidity, EMI/EMC)
- Reliability tests (life testing, accelerated aging, HALT/HASS)
- Software tests (unit/integration/system/regression, load and security testing)
6) Verify manufacturing and quality requirements
Even if one prototype passes, the design must be producible:
- Incoming inspection criteria and supplier qualification
- Process capability (e.g., Cp/Cpk), yield and variation control
- End-of-line tests and acceptance test procedures
7) Document results and manage changes
They produce objective evidence:
- Test reports with raw data, uncertainties, and deviations
- Nonconformance reports and corrective actions
- Updated RTM showing each requirement “verified” with linked evidence
If the design changes, engineers re-run impacted tests (regression testing / re-verification).
8) Distinguish verification vs validation
- Verification: “Did we build it right?” (meets written requirements)
- Validation: “Did we build the right thing?” (meets user needs/use cases, often via field trials)
In practice, proving a design meets technical requirements is about traceability (every requirement has a planned method) plus objective evidence (test/analysis/inspection results) under controlled conditions.