High-level requirements that do not come directly from system requirements, or that specify behaviour beyond them, are marked as derived, given the reason they exist and handed to the system processes, the system safety assessment among them. Table A-2 objective 2, described in 5.1.1.b; applies at levels A, B, C, D, no independence required; activities 5.1.2.h, 5.1.2.i; outputs Software Requirements Data. The revision moved the definition of derived requirements onto content (behaviour beyond the higher level) rather than traceability alone and added the rationale for each.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.