The architecture rests on the aircraft and system functions, their functional interfaces and the requirements that the safety objectives call for, and implementation choices and problems are a main source of derived and new safety-driven requirements. Plans and standards for capturing requirements are developed so the set is consistent and the team shares the same expectations, especially for model-based formats. Where requirements are represented by models, planning identifies the use of models, the intended tools and their use, and modeling standards and libraries giving a common understanding of the modeling language, with readable content, unambiguous mapping of symbols and names to actual signals and interfaces, and layered development. If system models are taken further to capture item requirements and generate embedded code or hardware description language, the software and hardware guidance (DO-178C, DO-254) applies from allocation until the item comes back for system verification, with DO-331 covering model-based software.
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.