The project defines how system elements interface and interact with one another and with outside systems or entities; interface requirements, whether mechanical, electrical, data or envelope, are written up thoroughly in specifications or interface control documents, kept traceable to both sides of each interface and built into the architecture definition, with models usable to control them. Requirements are partitioned, aligned and allocated to architectural entities and system elements, so that each candidate architecture is stated as requirements on the elements that make up the system; traceability between requirements and the architecture, its elements and interfaces is established and maintained, and the verification and validation criteria for each element are written down at the moment its derived requirements are created.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.