The software requirements process turns the system requirements allocated to software into high-level requirements, with trace data linking the two. Table A-2 objective 1, described in 5.1.1.a; applies at levels A, B, C, D, no independence required; activities 5.1.2.a to 5.1.2.g, 5.1.2.j, 5.5.a; outputs Software Requirements Data, Trace Data. Trace data became a life cycle data item (11.21) and the association must work in both directions.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.