The software elements are integrated per the architectural design and the integration verified against it using the methods the standard recommends by ASIL (requirements-based test, interface test, fault injection, resource usage evaluation, back-to-back test), with structural coverage at the function and call level and the verification of freedom from interference and timing; the software compliance book restates the integration verification methods. Its aims, per the SGS quotation, are to lay down the integration sequence and assemble the software elements step by step into the finished embedded software, to check the architectural safety measures, and to evidence that the integrated units and components meet the architecture's requirements and contain no unwanted functions or properties; structural coverage at the architectural level is among the audited activities. Requirement text not held.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.