End-to-End Bi-Directional Traceability from Stakeholder Reqs to Unit Verification

A primary failure point during ASPICE audits is the inability to prove continuous traceability. Traceability must operate in both directions:

Forward Traceability (Completeness): Demonstrates that 100% of customer stakeholder requirements (SYS.1/SYS.2) have been translated into system architectural blocks (SYS.3), refined into software requirements (SWE.1), designed into architectural components (SWE.2), implemented in code units (SWE.3), and validated through test cases (SWE.4-6 and SYS.4-5). Backward Traceability (Justification): Demonstrates that every line of code in the production repository, every software component, and every hardware test fixture directly derives from an authorized, baseline requirement—guaranteeing zero unauthorized or untested feature creep.

ASPICE Cert automates this graph using persistent cryptographic hashes attached to requirement IDs, Git commits, static analysis logs, and test execution outputs.