Aim: describe the software from the most abstract level down to detailed refinements, as the frame for demonstrating the safety achieved and for later maintenance. The document requirements of Table A.1 are met to the extent the integrity level requires. Table A.1 is ordered as an idealised waterfall, not a schedule to follow strictly: phases may overlap, provided verification and validation show that inputs and outputs, documents and software, stay consistent inside and across phases.
This control maps to 3 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 3 it maps to, and the evidence behind each claim, over MCP and REST.