For simple custom devices the planning documents propose a process covering definition of the device functions, complete verification of those functions by tests and analyses, configuration management including problem reporting and instructions to reproduce the device, and assessment of build conformance. The verification case review and timing verification objectives also apply, tool objectives apply where tools are used, reuse follows DO-254 11.1 with the PDH clarifications, and COTS IP objectives apply where COTS IP is used. Data may be combined with other hardware data.
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.
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 1 it maps to, and the evidence behind each claim, over MCP and REST.