The item design and build processes, for electronic hardware and software, give traceability to the requirements allocated to the items. Where item implementation runs in parallel with requirements allocation and architecture definition, enough discipline is applied to capture derived requirements and to achieve all function requirements in the implementation. Outputs include the procedures for integrating the item, released drawings for the hardware, the software code and its life cycle data, the development assurance records, any early breadboard or prototype units, and articles for laboratory or flight testing, with DO-178C and DO-254 providing the detailed guidance.
This control maps to 2 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.
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.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.