The SRS summarizes the major functions the software will perform, organized so that a first-time reader understands them, possibly taken from the allocating section of a higher-level specification and described with use cases, user stories, scenarios or textual or graphical views of logical relationships (not a design) (9.6.5); describes the general characteristics of the intended user groups that influence usability, such as education, experience, disabilities and technical expertise, as reasons for later specific requirements (9.6.6); describes other limitations on the supplier's options: regulatory requirements and policies, hardware limitations, interfaces to other applications, parallel operation, audit and control functions, higher-order language requirements, signal handshake protocols, quality requirements, criticality of the application, safety and security considerations, physical and mental considerations, and limits imposed by other systems, real-time demands from a controlled system among them (9.6.7); and lists the assumptions and dependencies whose change would change the requirements, such as availability of an operating system on the target hardware (9.6.8).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.