The SyRS defines the functional requirements for system operation (9.5.5); usability targets and quality-in-use requirements, possibly with criteria for effectiveness, efficiency and satisfaction that can be measured, and for avoiding harm from use, in named contexts (9.5.6); the critical performance conditions and their capabilities, covering dynamic actions or changes such as rates, velocities, movements and noise levels, quantified endurance criteria such as the minimum total service life, how long an operating session lasts and the planned rate of use, and performance per operational phase and mode (9.5.7); and the interface requirements among system elements, including the human element, and with external entities including other systems, with interdependencies and constraints such as communication protocols, special devices, standards and fixed formats, recognizing that interfaces may carry information both ways (9.5.8).
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.