Hardware Traceability
Section 09: Hardware Certification (DO-254)
Definition
The documented association between hardware requirements, design elements, implementation artifacts, and verification activities throughout the DO-254 lifecycle. Traceability demonstrates that every requirement has been implemented in the design and verified, and that every design element and verification activity traces to a requirement.
Where This Shows Up
Bidirectional traceability is required in DO-254: forward traceability (from requirements to design and verification) ensures completeness, while reverse traceability (from design and verification back to requirements) ensures that no unintended functionality exists. Traceability is typically maintained in a requirements management tool or traceability matrix. Gaps in traceability indicate missing verification coverage or unrequired functionality, both of which must be resolved before certification. At DAL A and B, complete bidirectional traceability is required; at DAL C, forward traceability is typically sufficient.
Primary Sources
Section 6.3 — Traceability, defines the traceability requirements across the hardware lifecycle.
Artifacts Produced
Document or database linking system requirements to hardware requirements, hardware requirements to design, and hardware requirements to verification procedures and results.
Related Terms
Need help navigating certification?
Understanding the terminology is the first step. If you need expert guidance on DO-178C, DO-254, ARP4754B, or any aspect of FAA, EASA, or TCCA certification, our team is here to help.