Software integration tests are specified during design and development, stating the division into manageable integration sets, test cases and data, test types, environment, tools, configuration and programs, completion criteria, and corrective action on failure. The software is tested to that specification, showing that all modules and elements interact correctly for their intended function and perform no unintended functions. Results are documented with whether objectives and criteria were met and reasons for any failure, and any change during integration undergoes impact analysis identifying affected modules and the re-verification and re-design required.
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.