The StRS explains the way the system backs the business activities and the setting in which it does so, as system processes derived from the business process structure, each uniquely named and numbered and shown as an activity sequence (9.4.10); how each business policy or rule is expected to end up as functional requirements in the system and software specifications, every rule carrying a unique name and number cited from the process descriptions (9.4.11); the system conditions and functional requirements imposed when conducting the business process, which may become performance requirements in the SyRS (9.4.12); the operational modes and states supporting operation (9.4.13); and the quality level the system must reach in operation, covering aspects like performance and compatibility, reliability and security, maintainability and portability (9.4.14).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.