EN 50716:2023 - Railway Applications - Requirements for Software Development
The CENELEC cross-sector standard for railway software (November 2023), which replaces EN 50128:2011 for command, control and signalling and EN 50657:2017 for software on board rolling stock, with conflicting national standards withdrawn by 2026-10-30. Five software integrity levels from Basic Integrity to SIL 4 decide which techniques and documents apply; it sets role independence and competence, lifecycle documentation, testing, verification, validation, independent assessment, quality assurance, change control and tool classes T1 to T3, the development phases from requirements to final validation, application data for configurable systems, and deployment and maintenance, with normative technique tables (Annex A) and role specifications (Annex B). Built from the complete English text.
EN 50716:2023 - Railway Applications - Requirements for Software Development is a compliance framework from European Union and EFTA (CENELEC), adopted nationally as BS EN, I.S. EN, NEK EN, SIST EN, CEI EN, NP EN, HRN EN, EVS-EN and BAS EN 50716; applied by railway assessors internationally with 8 domains and 46 controls that map to 4 other frameworks. The largest domains are Annex A: Criteria for the selection of techniques and measures – EN 50716:2023 - Railway Applications - Requirements for Software Development (18 controls), Clause 6: Software assurance – EN 50716:2023 - Railway Applications - Requirements for Software Development (7 controls), Clause 7: Software development – EN 50716:2023 - Railway Applications - Requirements for Software Development (7 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (8)
Annex A: Criteria for the selection of techniques and measures – EN 50716:2023 - Railway Applications - Requirements for Software Development
Annex B: Key software roles and responsibilities – EN 50716:2023 - Railway Applications - Requirements for Software Development
| Code | Title |
|---|---|
| en-50716-2023-railway-applications-requirements-for-software-development::B | Annex B (normative): key software roles and responsibilities |
Clause 4: Software integrity levels conformance – EN 50716:2023 - Railway Applications - Requirements for Software Development
| Code | Title |
|---|---|
| en-50716-2023-railway-applications-requirements-for-software-development::4 | Software integrity levels conformance |
Clause 5: Software management and organization – EN 50716:2023 - Railway Applications - Requirements for Software Development
| Code | Title |
|---|---|
| en-50716-2023-railway-applications-requirements-for-software-development::5.1 | Organization and independence of roles |
| en-50716-2023-railway-applications-requirements-for-software-development::5.2 | Personnel competence and responsibilities |
| en-50716-2023-railway-applications-requirements-for-software-development::5.3 | Lifecycle issues and documentation |
Clause 6: Software assurance – EN 50716:2023 - Railway Applications - Requirements for Software Development
| Code | Title |
|---|---|
| en-50716-2023-railway-applications-requirements-for-software-development::6.1 | Software testing |
| en-50716-2023-railway-applications-requirements-for-software-development::6.2 | Software verification |
| en-50716-2023-railway-applications-requirements-for-software-development::6.3 | Software validation |
| en-50716-2023-railway-applications-requirements-for-software-development::6.4 | Software assessment |
| en-50716-2023-railway-applications-requirements-for-software-development::6.5 | Software quality assurance |
| en-50716-2023-railway-applications-requirements-for-software-development::6.6 | Modification and change control |
| en-50716-2023-railway-applications-requirements-for-software-development::6.7 | Support tools and languages |
Clause 7: Software development – EN 50716:2023 - Railway Applications - Requirements for Software Development
| Code | Title |
|---|---|
| en-50716-2023-railway-applications-requirements-for-software-development::7.1 | Lifecycle and documentation for software |
| en-50716-2023-railway-applications-requirements-for-software-development::7.2 | Software requirements |
| en-50716-2023-railway-applications-requirements-for-software-development::7.3 | Architecture and design |
| en-50716-2023-railway-applications-requirements-for-software-development::7.4 | Component design |
| en-50716-2023-railway-applications-requirements-for-software-development::7.5 | Component implementation and testing |
| en-50716-2023-railway-applications-requirements-for-software-development::7.6 | Integration |
| en-50716-2023-railway-applications-requirements-for-software-development::7.7 | Overall software testing / Final validation |
Clause 8: Development of application data – EN 50716:2023 - Railway Applications - Requirements for Software Development
Clause 9: Software deployment and maintenance – EN 50716:2023 - Railway Applications - Requirements for Software Development
| Code | Title |
|---|---|
| en-50716-2023-railway-applications-requirements-for-software-development::9.1 | Software deployment |
| en-50716-2023-railway-applications-requirements-for-software-development::9.2 | Software maintenance |
Your Compliance Coverage
If you comply with EN 50716:2023 - Railway Applications - Requirements for Software Development, you already cover:
EN 50126 / EN 50128 / EN 50129 - Railway Applications RAMS
85%
39 controls mapped
Compare →ISO 26262:2018 - Functional Safety for Road Vehicles
78%
36 controls mapped
Compare →IEC 62304:2015 Medical Device Software Lifecycle Processes
46%
21 controls mapped
Compare →+ 1 more: DO-178C / ED-12C - Software Considerations in Airborne Systems (39%)
See all 4 mapped frameworks ↓Maps to 4 other frameworks
Coverage is not the same as your position
This page shows what EN 50716:2023 - Railway Applications - Requirements for Software Development overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is EN 50716:2023 - Railway Applications - Requirements for Software Development and who does it apply to?
EN 50716:2023 - Railway Applications - Requirements for Software Development is a compliance framework from European Union and EFTA (CENELEC), adopted nationally as BS EN, I.S. EN, NEK EN, SIST EN, CEI EN, NP EN, HRN EN, EVS-EN and BAS EN 50716; applied by railway assessors internationally with 8 domains and 46 controls. The CENELEC cross-sector standard for railway software (November 2023), which replaces EN 50128:2011 for command, control and signalling and EN 50657:2017 for software on board rolling stock, with conflicting national standards withdrawn by 2026-10-30. Five software integrity levels from Basic Integrity to SIL 4 decide which techniques and documents apply; it sets role independence and competence, lifecycle documentation, testing, verification, validation, independent assessment, quality assurance, change control and tool classes T1 to T3, the development phases from requirements to final validation, application data for configurable systems, and deployment and maintenance, with normative technique tables (Annex A) and role specifications (Annex B). Built from the complete English text. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does EN 50716:2023 - Railway Applications - Requirements for Software Development actually require?
EN 50716:2023 - Railway Applications - Requirements for Software Development has 46 controls organised across 8 domains. The largest domains are Annex A: Criteria for the selection of techniques and measures – EN 50716:2023 - Railway Applications - Requirements for Software Development (18 controls), Clause 6: Software assurance – EN 50716:2023 - Railway Applications - Requirements for Software Development (7 controls), Clause 7: Software development – EN 50716:2023 - Railway Applications - Requirements for Software Development (7 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of EN 50716:2023 - Railway Applications - Requirements for Software Development do I already cover?
EN 50716:2023 - Railway Applications - Requirements for Software Development maps to 4 other compliance frameworks. The top mapping partners are EN 50126 / EN 50128 / EN 50129 - Railway Applications RAMS (85% coverage), ISO 26262:2018 - Functional Safety for Road Vehicles (78% coverage), IEC 62304:2015 Medical Device Software Lifecycle Processes (46% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement EN 50716:2023 - Railway Applications - Requirements for Software Development?
Start your EN 50716:2023 - Railway Applications - Requirements for Software Development compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about EN 50716:2023 - Railway Applications - Requirements for Software Development requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 46 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 727 frameworks.
Get Started Free →Free forever — no credit card required