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.3: Table A.3: software architecture (7.3)

Table A.3 grades 19 architecture techniques, none graded at Basic Integrity except fully defined interface (HR, overall boundary only), modelling (R) and structured methodology (R). At SIL 1 and 2 defensive programming, fully defined interface and structured methodology are HR; at SIL 3 and 4 fully defined interface (external interfaces) is M and defensive programming, fault detection and diagnosis, error detecting codes, failure assertion programming, diverse programming, memorising executed cases, software error effect analysis, graceful degradation, modelling and structured methodology are HR. Safety bag, recovery block and retry mechanisms are R throughout from SIL 1; error correcting codes carry no grade; backward recovery, forward recovery, artificial intelligence and machine learning, and dynamic reconfiguration are NR at SIL 1 to 4. Approved combinations: SIL 3 and 4, either defensive programming, diverse programming, fully defined interface and structured methodology plus one of error detecting codes, failure assertion, memorising executed cases or modelling, or defensive programming, error detecting codes, fully defined interface and structured methodology plus one of fault detection, failure assertion, memorising executed cases, error effect analysis or modelling; SIL 1 and 2, defensive programming, fully defined interface and structured methodology plus one of fault detection, error detecting codes, failure assertion, diverse programming, memorising executed cases, error effect analysis or modelling. Some items may be settled at system level; error detecting codes may follow EN 50159; techniques are independent of processing technology.

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.3 Table A.3: software architecture (7.3)
  • 6:7.4 7.4 Software architectural design

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.