If already covered by Part 2 system validation, it need not be repeated. Validation follows the software validation plan, with any split of responsibility documented. Results are documented, recording per safety function a retraceable sequence of activities, the plan version, the function validated with its plan reference, tools and equipment with calibration data, results and discrepancies; for discrepancies, the analysis and the decision to continue, or to raise a change request and go back to an earlier phase are recorded. Testing is the main validation method, supplemented by analysis, animation and modelling; the software is exercised by simulating normal input signals, anticipated occurrences and undesired conditions requiring system action; and documented results and pertinent documentation are passed to the system developer. Software tools meet 7.4.4. The tests must show that every specified software safety requirement is correctly met and that the software does nothing unintended; test cases and results are kept for later analysis and independent assessment as the SIL requires; and the result states pass, or the reasons for failure.
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.