Standards · Railway

EN 50716 — Railway applications

Adopted at the end of 2023 by CENELEC, EN 50716:2023 describes the requirements for the development, deployment and maintenance of railway software — control-command and signalling applications, and applications on board rolling stock. It replaces EN 50128:2011 and EN 50657:2017.

High-speed train in a station
What the standard requires

Static analysis, dynamic testing and coverage

For the analysis and testing of software components, static analysis — including control flow and data flow analysis —, dynamic analysis and testing and test coverage are highly recommended at all integrity levels, from SIL 1 to SIL 4.

The use of coding standards is highly recommended for basic integrity, SIL 1 and SIL 2 — and becomes mandatory for SIL 3 and SIL 4.

At all levels, the standard highly recommends limiting the size and complexity of functions, subroutines and methods.

Signal box
Table A.21

Test coverage required by SIL

For structure-based testing — white-box testing —, the standard sets the following levels.

Coverage criterion Basic integrity SIL 1 SIL 2 SIL 3 SIL 4
1Statement coverageRHRHRHRHR
2Branch coverage—RRHRHR
3Compound conditions (condition coverage)—RRHRHR
4Data flow—RRHRHR
5Path coverage—RRHRHR

HR highly recommended · R recommended · — not required.

For SIL 3 and SIL 4, coverage at component level must be measured according to one of these combinations: branches (2) and compound conditions (3); or branches (2) and data flow (4); or paths (5); or coverage measured at integration level on one or more of criteria 2, 3, 4 or 5.

Other coverage criteria may be chosen, depending on the software architecture and the programming language, provided that the choice is justified.

Tool support

Measuring the coverage required

Statement, branch and condition coverage can be analyzed with Testwell CTC++ (the tool even measures the highest coverage levels, MC/DC and MCC). Testwell CTC++ is suited to C, C++ and Java projects.

Learn more about Testwell CTC++ → Request a free evaluation

Certification

TÜV SÜD certificate for Testwell CTC++ Code Coverage Analyzer

The Testing Laboratory for Safety Components of TÜV SÜD Rail GmbH has certified that Testwell CTC++ is:

  • suitable to be used in safety-related development according to IEC 61508:2010 (for any SIL);
  • qualified to be used in a standard-compliant development process according to ISO 26262:2018 (for any ASIL);
  • suitable to be used in safety-related development according to EN 50716:2023 (for any SIL);
  • suitable to be used in safety-related development according to IEC 62304:2006+A1:2015 (for any software safety class).

View the TÜV SÜD certificate (PDF) →

Certificate, Safety Package and qualification process →

For any question about using Testwell CTC++ in the development of safety-critical systems, contact us.

TÜV SÜD certificate for Testwell CTC++
Testwell CTC++ on video

Lighter tool qualification

EN 50716 classifies tools according to their influence on the software and requires you to justify the confidence placed in them. The animation shows how the TÜV SÜD certification of Testwell CTC++ and its Safety Package lighten this demonstration.

The 13 Testwell CTC++ animations →
Coding standards

Coding standards and complexity: continuous evidence with TiCS

As stated above, EN 50716 makes coding standards mandatory at SIL 3 and SIL 4, and highly recommends, at all levels, static analysis and limiting the size and complexity of the code. This still has to be demonstrated, for every version delivered.

TiCS centralizes this demonstration: checking of the rules of your coding standard (MISRA C/C++ or in-house rules) by your analyzers, size and complexity metrics, compiler warnings — in a single dashboard, by subsystem and by version.

  • Deviations by rule and by severity, from the subsystem down to the line of code.
  • Size and complexity thresholds checked at every build.
  • Quality gates in the integration pipeline: no new violation enters the main branch.
  • History useful for the verification reports and for the assessor.

TiCS replaces neither the verifier nor the reports required by the standard: it provides their objective, continuous measurement. The tool classification (classes T1 to T3) remains to be established in your project.

Discover TiCS → Evaluate TiCS on a pilot repository

TiCS on video

Deviations, ready for the audit

In railway, every deviation from the coding rules must be justifiable to the assessor. The animation shows how a deviation is requested, approved by a second person and kept in the history.

The 14 TiCS animations →
Train driver's cab Passengers in a station Urban transit train
Sector

Railway

References, testimonials and uses of Testwell CTC++ in rail transport.

See the sector page →

Other standards

The standards landscape

DO-178C, ISO 26262, IEC 61508, IEC 62304, ISO 25119: each standard sets its own coverage requirements.

See all standards →