Software integration and software/hardware integration are carried out and it is demonstrated that software and hardware work together correctly to carry out their intended functions. Software integration progressively combines previously tested components into a composite whole so that interfaces and the assembled software are proven before system integration; the software integration test report states the outcome and whether the integration test specification's objectives and criteria were achieved, failures with reasons, in auditable form with machine-readable results, and which items, in which configuration, were integrated (7.6.4.1 to 7.6.4.5). Software/hardware integration merges the software onto the target hardware and integrates the system as the software/hardware integration test specification defines, distinguishing activities at the developer's premises from those needing the user's site, with tools and facilities available early; any modification during integration is subject to an impact study identifying every affected component and the necessary re-verification; the software/hardware integration test report states results against the specification, the verifier's satisfaction with it as a record of the tests, and the identity and configuration of everything involved (7.6.4.6 to 7.6.4.9). Both reports are verified in the software integration verification report (7.6.4.10 to 7.6.4.13). Techniques of Table A.6.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.