The SRS sets usability targets and quality-in-use requirements for the software, possibly with measurable criteria for effectiveness, efficiency and satisfaction and for avoiding harm, in named contexts of use (9.6.13). It specifies static numerical requirements (such as terminals supported, simultaneous users, and the amount and type of information handled, sometimes under a capacity heading) and dynamic numerical requirements (such as numbers of transactions and tasks and amounts of data processed within given periods under normal and peak workload), all stated in measurable terms, for example a stated percentage of transactions completing within a stated time (9.6.14).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.