The outcome of planning is documented in one development assurance plan or a collection of plans that addresses every planning element of Table 1, is structured to help coordination with the Certification Authority, and, when several plans are used, may carry a top-level summary across them. The plan or plans identify what the development covers, including any change to, or reuse of, systems, equipment or items already certificated on an earlier product; the processes and methods for each planning element; the key events marking the planned development cycle; the organizational structure, roles and responsibilities; and the means of finding and dealing with unintended behaviors. Processes and events are described in enough detail to show their significance, timing, dependencies and expected results, and for complex systems the specific processes used to manage that complexity at aircraft or system level are described.
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.