Development assurance planning includes early and continuing coordination with the Certification Authority to establish communication and to agree how the aircraft, systems, equipment and items will be shown to meet regulations and industry standards, reducing uncertainty and misinterpretation. Topics for coordination include: a description of how functions relate, how things are physically laid out and how data are exchanged; regulatory gaps for new aircraft types or new technologies; the planning elements for the application, covering the scope and any tailored, eliminated or substituted processes with rationale, the integral processes (with requirements management detail on safety requirements), how certification interacts with the system requirements, the design and the main safety assessment work, any planned reuse of processes, methods or data from an approved product, the plan for detecting implementation errors through tests, inspections or other verification of normal and failed-state behavior, and the roles of each group from aircraft to item level including supplier roles and aircraft safety group involvement in derived and safety requirement reviews; the aircraft and system FHAs; the PASA and PSSA as the project matures; and the list of data to be submitted and data retained under configuration control. A summary of development assurance outputs (4.7) may be provided to show compliance.
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.