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.2: Table A.2: Software Requirements Specification (7.2)

Table A.2 lists three techniques for making the requirements specification clear and precise: modelling (Table A.17), structured methodology (D.52) and decision tables (D.13), each R at Basic Integrity and SIL 1 and 2 and HR at SIL 3 and 4. The specification describes the problem in natural language plus whatever formal or semi-formal notation is needed, and at least one of the three techniques is chosen to suit the integrity level.

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.2 Table A.2: software requirements specification (7.2)
  • 8:6.4.1 6.4.1 Specification of safety requirements

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.