Planning defines how functional and airworthiness requirements become a hardware item with acceptable evidence that it will perform its intended functions safely. Its objectives are that the hardware life cycle processes are defined, standards are selected and defined, the environments for development and verification are chosen or defined, and the means of compliance with the assurance objectives, including the Section 2.3.4 strategies, are proposed to the certification authority.
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.