The integrated software and hardware are analysed and tested to confirm they meet the software requirements specification, stressing the functional and safety aspects in line with the SIL, and it is checked whether the software suits its intended application. The overall software is tested against the overall software test specification, showing that all requirements of the software requirements specification are carried out correctly, with the overall software test report per 6.1 (7.7.4.1 to 7.7.4.4; Table A.7); validation per 6.3 is performed on the overall software by the validator, exercising the software with the inputs of normal running, foreseeable events and unwanted conditions that call for a system response, and the software validation report records the results, the requirements coverage, the configuration of everything used and the discrepancies and corrective actions (7.7.4.5 to 7.7.4.11). A release note accompanies the delivered software, identifying the version and configuration, the discrepancies and detected errors from validation, and the application conditions and constraints on use (7.7.4.12, with 8.4.8.8 and 9.1.4.4 for the deployment information).
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.