Each problem is investigated and its causes identified where possible, its relevance to safety evaluated using the software risk management process, the outcome of investigation and evaluation documented, and change requests created for the actions needed or the rationale for taking no action documented; a problem need not be corrected if it is not relevant to safety. 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.