Skip to main content

Why Traceability Matters

Traceability is a critical requirement for automotive functional safety standards:
  • ISO 26262 Part 8, Clause 6 requires bidirectional traceability from concept phase (hazards and safety goals) through all design phases to verification and validation
  • AIAG-VDA FMEA methodology links failure modes to design characteristics and control plans
  • IATF 16949 / APQP requires traceability from customer requirements through process controls to product verification
  • Compliance audits rely on traceability matrices to demonstrate complete coverage

Traceability Model in TestAuto2

diagram The traceability model supports:
  • Upstream links — trace requirements back to their sources (customer needs, hazards, safety goals)
  • Downstream links — trace requirements forward to implementation (design, characteristics, failure modes)
  • Verification links — link requirements to test cases that verify they are met
  • Validation links — link top-level requirements to system-level validation tests

Key Concepts

Forward traceability follows the flow from customer requirements down to test cases (top-down decomposition). Backward traceability traces from test cases back to requirements (bottom-up verification). Both directions are required for ISO 26262 compliance.
All requirements classified as SC (Safety Critical) must be fully traced through all levels of the V-model with no gaps. The Safety Readiness Scorecard highlights SC/CC traceability completeness as a key metric.

Common Tasks