DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware
Section 2: System aspects of hardware design assurance – DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware

DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware 2.1.3: 2.1.3 Information flow between the hardware and software life cycles

Information exchanged between the hardware and software processes may include derived requirements that hardware/software integration needs (protocols, timing constraints, addressing schemes at the interface), cases where hardware and software verification must be coordinated, incompatibilities found between hardware and software (which may go through a reporting and corrective action system), and safety assessment data that should also reach the system processes.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 1 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.

  • 4.6.1.3 4.6.1.3 Information flow between hardware and software life cycle processes

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 2: System aspects of hardware design assurance – DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware

Query this from an agent

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