Hardware and software integration tests are specified during design and development to ensure compatibility in the safety-related programmable electronics, stating integration levels, test cases and data, test types, test environment (tools, support software, configuration description), and completion criteria; separating developer-premises activities from those needing the user's site; and distinguishing merging software onto the target hardware, connecting interfaces like sensors and actuators, and applying the system to the EUC. Integration follows that specification; changes during integration are impact-analysed for affected modules and re-verification; test cases and expected results are documented; and results state whether objectives and criteria were met, the reasons for any failure, and the impact analysis of any resulting software change.
This control maps to 2 controls across 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.