Developing the system architecture and allocating the system requirements to items go hand in hand and are repeated in cycles; requirements arising from allocation may concern the system or the item, and each cycle clarifies derived requirements and the rationale for allocation, the process finishing when every requirement fits the final architecture so that the items carry out all intended system functions. Candidate system architectures may be compared on technology readiness, schedule, producibility, contracts, economics, experience and precedent, then assessed iteratively by functional and performance analyses, with the PASA and PSSA establishing feasibility against the top-level safety objectives. The result is a system architecture whose items each carry their allocated requirements, including the safety requirements and the assurance levels set by the PASA and PSSA.
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.