Aim: judge on evidence that each phase's outputs (process, documents, software or application) fulfil its requirements and plans for completeness, correctness and consistency, managed by the Verifier. Outputs are the Software Verification Plan, the verification reports and the Software Planning Verification Report. The Verifier writes the verification plan, which may be split into child plans as needs become clear; it describes the verification activities, records all criteria, techniques and tools, including a set chosen from Tables A.5, A.6 and A.7 justified against 4.8 to 4.10, describes the reviewing and testing that establish correctness and consistency against each phase's input, and defines the retention format of results. Each phase must show it satisfies the requirements for function, performance and safety. The plan covers choice of strategies and techniques (favouring readily analysable ones), choice and documentation of activities, evaluation of results and of safety and robustness requirements, roles, the functional test coverage required, and the structure of each verification step (requirements 7.2.4.22, architecture and design 7.3.4.41 and 7.3.4.42, components 7.4.4.13, source code 7.5.4.10, integration 7.6.4.13). Once the quality assurance, configuration management, verification, validation and maintenance plans exist, the Verifier checks them for readability, traceability and their specific content, internal consistency and coherence with each other, and records it in the planning verification report. Each verification report follows the plan and records the items verified and their configuration with verifier names, non-conformances, poorly suited components, data, structures or algorithms, errors found, adherence to or deviation from the plan with its criticality, whether techniques were used correctly, assumptions, and a results summary.
This control maps to 7 controls across 4 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 7 it maps to, and the evidence behind each claim, over MCP and REST.