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.5: Table A.5: software component analysis and testing (6.2 and 7.4)

Table A.5 grades seven component-level techniques. Dynamic analysis and testing (expanded in Table A.13) is HR at Basic Integrity to SIL 2 and M at SIL 3 and 4; interface testing is HR at every level (overall boundary only at Basic Integrity); static analysis (Table A.19), code coverage (Table A.21) and performance testing (Table A.18) are HR at SIL 1 to 4; formal proof is R at SIL 1 and 2 and HR at SIL 3 and 4; metrics are R at SIL 1 to 4. Approved combinations: SIL 3 and 4, formal proof with dynamic testing and code coverage, or static analysis with dynamic testing and code coverage; SIL 1 and 2, static analysis with code coverage, or dynamic testing with code coverage.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 2 controls across 2 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.5 Table A.5: verification and testing (6.2 and 7.4)
  • 6:9.4 9.4 Software unit verification

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 2 it maps to, and the evidence behind each claim, over MCP and REST.