The safety system is integrated to its specified design and tested against the specified integration tests, demonstrating that every module interacts correctly in its intended function and that unintended functions are excluded by design. Software integration follows Part 3, 7.5. Integration test documentation states results and whether the design-phase objectives and criteria were met, and records reasons for and corrections of any failure. Changes during integration undergo impact analysis identifying affected subsystems and elements and the re-verification needed. Records cover the test specification version, acceptance criteria, system version tested, tools and equipment with calibration data, each test result, discrepancies, and the analysis and continue-or-change decision. Table B.3 techniques are used to avoid integration faults.
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.