Table A.1 grades the 46 lifecycle documents by software safety integrity level: planning (software quality assurance plan, software planning verification report, configuration management plan, verification plan, validation plan), software requirements (specification, overall software test specification, requirements verification report), architecture and design (architecture specification, design specification, interface specifications, integration and software/hardware integration test specifications, architecture and design verification report), component design (component design specification, component test specification, component design verification report), component implementation and testing (source code and supporting documentation, component test report, source code verification report), integration (two integration test reports, integration verification report), overall testing and final validation (overall software test report, validation report, tools validation report, release note), systems configured by application data (application requirements specification, application preparation plan, application test specification, application architecture and design, application preparation verification report, application test report, source code of application data or algorithms, application data verification report), deployment (release and deployment plan, deployment manual, release notes, deployment records, deployment verification report), maintenance (maintenance plan, change records, maintenance records, maintenance verification report) and assessment (assessment plan, assessment report). Every document is HR at SIL 1 to 4; at Basic Integrity the plans, the requirements specification, the overall test specification, the interface specifications, the source code, the overall test report, the validation report, the release note, the application requirements and test specification, the application test report, the application data source and verification report, the release notes and the change records are HR, most others R, and the component design set, the component test and source code verification reports, the tools validation report, the application preparation verification report and the assessment plan and report are not required. Notes: for Basic Integrity the verification plan may cover only items a) to d) and f) of 6.2.4.9; the interface specification is HR only at the boundary of the whole software; documents may be combined as allowed by 5.3.2.12-13; the application preparation plan, test specification and architecture may be R or HR depending on where verification takes place; architecture and design specifications matter at Basic Integrity for long-term maintenance.
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.