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.15: Table A.15: suitable programming languages

Detailed table for choosing a programming language (textual, diagrammatic or modelling). Documented and defined operational semantics is R at Basic Integrity, HR at SIL 1 and 2 and M at SIL 3 and 4; support for modular approaches, commenting, a strong type system with checking, static analysis, testing and test coverage metrics are each R at Basic Integrity and HR at SIL 1 to 4. The choice follows the requirements of 7.3; D.54 explains how to judge suitability. EN 50716 replaced EN 50128's list of named languages with these generic criteria.

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.

  • 5.1.12 5.1.12 Identification and avoidance of common software defects
  • 6:5.4 5.4 General topics for the product development at the software level

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.