Activities should produce a high-level description including safety-related architectural constraints (covering design errors, functional, over-stress, reliability and robustness defects) and constraints the implementation places on software or other parts of the system; identify major components and their contribution to the hardware safety requirements, including the impact of unused functions; feed derived requirements, including interface definitions, back to requirements capture; feed back omissions and errors; and identify reliability, maintenance and test features. A design review is the usual way to reach consensus that the objectives are met.
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.