Development assurance planning sets out how the aircraft or system will be developed so that it meets its requirements with a level of confidence matching the certification basis, taking modifications to existing aircraft or systems into account. Its aims are to define the activities of each development assurance process covering the requirements, FDALs and IDALs; to define the life cycle with the relationships, order, feedback paths and transition criteria between processes; to choose the development environment, methods and tools for each process; to set development standards consistent with the safety objectives; and to produce plans meeting the objectives of every integral process. Planning elements, which may be written at different times, are kept consistent so that together they form one complete plan, and reviewers read them that way; the planning covers each element listed in Table 1, namely development, the safety program, capture and validation of requirements, verification of the implementation, configuration management and process assurance, considers the iterative nature of design and manages the links and feedback between elements. Planning is re-entered for derivatives or in-service modifications.
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.