Software units are verified against the unit design and the software safety requirements using the methods of Table 7 (walk-through, pair programming, inspection, semi-formal and formal verification, control flow analysis, data flow analysis, static code analysis, static analyses based on abstract interpretation, requirements-based test, interface test, fault injection test, resource usage evaluation, back-to-back comparison test between model and code), with test cases derived per Table 8 (analysis of requirements, equivalence classes, boundary values, error guessing) and structural coverage measured per Table 9 (statement, branch, MC/DC by ASIL); the software compliance book reproduces Tables 7, 8 and 9 with their ASIL recommendations (static code analysis recommended at ASIL A and highly recommended at B to D). Its aims, per the SGS quotation, are evidence that the unit design meets the allocated requirements, that the safety measures from the safety-oriented analyses are implemented, that the unit conforms to its design with the required ASIL and that it contains no unwanted functions or properties; the audited activities are the verification methods, test case derivation and structural coverage at unit level. Requirement text not held.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.