The system requirements specification, produced in line with the project's policies and organized as its information management policies allow, gives the reasons for building or changing the system (9.5.2); fixes its scope by naming it, summarizing the needs analysis already completed as a short, plain statement of the user's problem and of what the system is and is not meant to do, and describing its application with the top-level benefits, objectives and goals stated as precisely as possible (9.5.3); and gives a system overview: the system context with its major elements including human elements and their interactions, with diagrams and narrative defining every significant interface crossing the boundary; the major system functions, conditions and constraints; and each type of user, operator and maintainer by function, location and device, with numbers, nature of use and capabilities, kept consistent with the SRS (9.5.4).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.