Planning should define the life cycle, transition criteria and the sequencing and feedback between processes; define and explain the design methods and the rationale for verification methods; identify any design standards and acceptable deviations; set how hardware design and supporting processes coordinate with system, software and certification activities; define the activities of each process at a controllable level; choose the design environment (tools, procedures, software, hardware), specifying the sequence when tools are used in combination for credit, and apply Section 11.4 tool assessment; identify how deviations from plans that affect certification are handled; describe how hardware, baselines and life cycle data are identified, managed and controlled; where subcontractors are used, say how the objectives will be met; describe process assurance policies; describe verification and process assurance independence and responsibilities in the PHAC; and record the means of compliance in the PHAC and communicate it to the authority early.
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.