Overview

Two questions, deliberately kept separate

Verification checks the product against its specification. Validation checks the specification against the actual need. A product can pass every verification test and still be wrong, which is why we keep the two activities distinct.

Across hardware, firmware and the integration between them, we build a coverage picture: what has been verified, by what method, with what result, and what remains an accepted risk. Gaps are stated rather than left implicit.

That coverage picture is what makes a release decision defensible. It also becomes the baseline against which future changes are re-verified, so a small modification does not quietly invalidate earlier testing.

Engineering principles

  • Verification: does it meet the specification
  • Validation: was the specification right
  • Coverage stated, gaps named
  • Baseline retained for future change

Validation scope

Where validation effort is spent

Each area answers a different class of question about the product.

Hardware validation

Rails, signals, timing, thermal behaviour and margin measured against the design intent across the operating range.

Coverage model

What gets verified, and how

AreaTypical methodEvidence produced
Power and supply behaviourMeasurement across load, temperature and start-up conditionsRail measurements, sequencing traces, margin data
Signal behaviourInstrumented measurement of critical nets and interfacesWaveform captures against expected characteristics
Firmware functional behaviourSpecification-based testing on target hardwareTest results per requirement, including error paths
TimingWorst-case measurement under representative loadResponse and jitter measurements against budgets
IntegrationCombined hardware and software exercisesResults for startup, fault, recovery and concurrent load
ReliabilityExtended and cyclic operationRun duration, failure records and analysis

Validation process

Building a defensible verification picture

Structured so that a release decision can be made on evidence rather than on how the last demo went.

  1. Requirement review

    Requirements examined for testability; anything that cannot be measured is rewritten until it can be.

  2. Verification planning

    Method chosen per requirement: inspection, analysis, measurement or test, with the rationale recorded.

  3. Test development

    Procedures, fixtures and automation built where repetition or precision justifies the effort.

  4. Execution

    Testing carried out on representative units with conditions and results captured as they occur.

  5. Failure analysis

    Failures driven to root cause, with the distinction between design, build and test faults made explicit.

  6. Coverage reporting

    A traceable view of what is verified, what is outstanding and what risk is being accepted.

  7. Regression baseline

    The verification set retained so future changes can be re-checked against a known reference.

Applications

When formal validation is worth the effort

Validation effort should scale with consequence, not with project size.

Requirement traceabilityMeasurementOn-target testingFailure analysisRegression baselineCoverage reporting
Application 01
Products approaching a production release decision
Application 02
Designs where field failure carries high cost or risk
Application 03
Equipment operating in demanding environments
Application 04
Products with regulatory or customer evidence requirements
Application 05
Designs undergoing significant change or modernisation
Application 06
Projects inherited from another team needing an independent picture

FAQ

Testing and validation questions

How validation work is usually structured and delivered.

Next step

Approaching a release decision without a clear coverage picture?

We can build the verification map, run the gaps and tell you what risk you are actually carrying.