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.1.3: 10.1.3 Hardware validation plan

The validation plan describes how derived requirements are validated: the validation methods (analyses, reviews, tests) with references, the validation data to be produced, and the validation environment (analysis and test equipment, tools).

Maintained by Gerard Blokdyk

What else in your programme already covers this

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

SAE ARP4754B / ED-79B - Guidelines for Development of Civil Aircraft and Systems · 2 controls

  • 5.4.2 5.4.2 Validation process and validation plan
  • 5.4.7 5.4.7 Validation data

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 2 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware controls