The SRS specifies the attributes the software must have, for example: reliability, the factors establishing the required reliability at delivery; availability, the factors ensuring a defined availability level such as checkpoint, recovery and restart; security, safeguarding the software against access, use, change, destruction or disclosure whether accidental or malicious, which may require particular cryptographic techniques, specific logs or history data sets, assignment of functions to different modules, restricted communication between areas of the program, integrity checks on critical variables and data privacy; maintainability, attributes such as modularity, interfaces or complexity limits (not generic good design practice); and portability, such as the share of elements and of code that is host-dependent, a proven portable language, a particular compiler or language subset, or a particular operating system.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.