Validation may combine reviews, simulation, prototyping, modelling, analysis, service experience, engineering assessment and testing. Activities should identify the derived requirements needing validation; set and satisfy completion criteria for each (validated at some level by review, analysis or test; the method fits the requirement, especially for safety; results correct and discrepancies explained, or consistent with the requirement where no expected result was predefined); evaluate derived requirements for safety impact, for completeness (all defined attributes necessary and all necessary attributes defined) and for correctness (unambiguous, no errors in attributes) against the allocated system requirements; establish traceability between derived requirements and validation activities and results; and feed back omissions and errors.
This control maps to 4 controls across 3 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 4 it maps to, and the evidence behind each claim, over MCP and REST.