The manufacturer verifies and documents that the software requirements implement the system requirements including those for risk control, do not contradict one another, avoid ambiguity, are stated so that test criteria can be established and tests performed, can be uniquely identified, and are traceable to system requirements or another source; no formal specification language is required. Applies to classes A, B and C.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.