DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware
Section 10: Hardware design life cycle data – DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware

DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware 10.4.1: 10.4.1 Traceability data

Traceability links the requirements, the detailed design, the implementation and the verification data so as to support configuration control, modification and verification. The data includes the correlation between allocated system requirements and hardware requirements; between hardware requirements and detailed design data; between the detailed design data and the item or assembly actually built; linking requirements (derived ones included) and detailed design data to verification procedures and results; and the results of a traceability analysis.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 3 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • 4.6.2 4.6.2 Item design and build
  • 5.4.2.5 5.4.2.5 Validation matrix
  • A-3.6 High-level requirements traced to system requirements

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Section 10: Hardware design life cycle data – DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware

Query this from an agent

The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.