For Level A and B functions using previously developed hardware, after the Section 11.3 assessment, the FFPs it implements are analysed against the service experience to show the reused functionality was sufficiently exercised in previous use (3.2.1). Where Level A or B FFP functions were not exercised, were exercised inadequately or lack service data, another method or added verification covers them (3.2.2). The data (3.2.3) includes the 11.3.2 assessment, the FFPs assured by service experience with sufficiency justification, FFPs with insufficient data and the tests and analyses used to complete them, FFPs and operating conditions not demonstrated that need architectural mitigation or advanced verification, and traceability (10.4.1) between service data, verification and each FFP.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.