EN 50716:2023 - Railway Applications - Requirements for Software Development
Annex A: Criteria for the selection of techniques and measures – EN 50716:2023 - Railway Applications - Requirements for Software Development

EN 50716:2023 - Railway Applications - Requirements for Software Development A.1: Table A.1: lifecycle issues and documentation (5.3)

Table A.1 grades 47 documents by integrity level. At Basic Integrity: the quality assurance, configuration management, verification and validation plans, the Software Requirements and Overall Software Test Specifications, interface specifications (overall boundary only), source code, Overall Software Test Report, Software Validation Report, Release Note, Application Requirements and Test Specifications, Application Test Report, source code of application data, both application integration test documents, the Application Release Note and Software Change Records are HR; the planning verification report, requirements verification report, architecture and design specifications, both integration test specifications, the architecture and design verification report, the three integration reports, the Application Preparation Plan, Application Architecture and Design, Application Data Verification Report, the three deployment documents and the maintenance plan, maintenance records and maintenance verification report are R; the three component design documents, component test and code verification reports, Tools Validation Report, Application Preparation Verification Report and the assessment plan and report carry no grade. At SIL 1 to 4 every one of the 47 is HR. The verification plan's content can be reduced at Basic Integrity to 6.2.4.9 a) to d) and f). Documents may be merged under the combination rules in clause 5.3.2 (items 12 and 13); the three application documents 29 to 31 may drop to R depending on where verification happens; and architecture and design content matters at Basic Integrity for long-term maintenance, possibly held in the requirements specification.

Maintained by Gerard Blokdyk

What else in your programme already covers this

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.

  • 50128:A.1 Table A.1: lifecycle issues and documentation (5.3)
  • 5.1.8 5.1.8 Documentation planning
  • 8:10.4 10.4 Documentation management

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.

Other controls in Annex A: Criteria for the selection of techniques and measures – EN 50716:2023 - Railway Applications - Requirements for Software Development

Query this from an agent

The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.