It "specifies the process and technical requirements for the development of software for programmable electronic systems for use in railway control and protection applications". The scope of these standards is summarized in the following figure: EN defines five software safety integrity levels, from SIL 0 lowest to SIL 4 highest , and specifies a variety of techniques and measures that support sound software engineering throughout the software life cycle. The standard identifies whether the techniques and measures are recommended, or highly recommended, based on the SIL. One of the major contributions in the version of EN is the specification of the requirements for tool qualification. Three classes of tools are defined: T1, T2 and T3. The T1 class applies to tools that affect neither the verification nor the final executable.

Author:Kizahn Mauk
Language:English (Spanish)
Published (Last):24 January 2018
PDF File Size:20.62 Mb
ePub File Size:9.36 Mb
Price:Free* [*Free Regsitration Required]

To win sustaining business in this market, you must be able to demonstrate high levels of reliability and system integrity to the railway authorities.

Whether the target application is deployed onboard or trackside, safety, security and reliability are tantamount. But achieving a proper software safety integrity level assessment can be time-consuming and costly.

Increasingly, rail software manufacturers apply EN as the development standard of choice to expedite the delivery of their systems as well as ensure their safety and reliability. To minimise both development schedule and overall development costs, rail software manufacturers are recognising that they can be more competitive if they leverage automated technologies that help them comply with the standard.

LDRA helps developers of security- and safety-critical railway systems meet these software quality and test requirements: Requirements Traceability.

TBmanager is the only requirements traceability solution that supports the tracing of requirements, development, and verification artifacts and activities throughout the entire software development life cycle. This bidirectional traceability ensures complete coverage and impact analysis through all phases of development, from a requirement through development to verification, and the production of evidence and documentation in a comprehensive requirements traceability matrix. TBmanager inherently supports requirements-based testing, a fundamental technique to mitigate risk in rail application development.

Code Inspection. Manual inspection is no longer an option as it is both time-consuming and error-prone. Static analysis has been recognised as an industry best practice for quickly and efficiently improving overall code quality. Coding Standards Compliance. TBvision helps your team develop and enforce the coding standard that is right for you from in-house best practices and guidelines to industry coding standards or a combination of in-house and industry standards. Unit and System Testing. TBrun provides rigorous unit testing early in the development lifecycle as advocated by regulatory guidelines.

TBrun automates the generation and execution of requirements-driven tests both on the host platform as well as the embedded target, and produces the necessary verification evidence for regulatory bodies.

TBrun also supports regression testing, saving time and money when requirements or code change during the software development life cycle. Automated Test Case Generation. The TBeXtreme module provides automated test case generation that saves test generation time in comparison to manual methods. This module helps improve code quality while alleviating the onerous nature and inherent inaccuracies prevalent in a manual unit testing process. Structural Coverage Analysis. All of this can be shown and reported graphically, enhancing the process of producing verification evidence.

Tool Qualification. In addition, associated documentation for the development and verification of the product is provided, including plans, procedures, and expected results.

Secure Code. Integration with Model-based Design. The LDRA tool suite augments model-driven development environments through automated standards compliance checking and automated verification and coverage analysis, at the model, source, and object code levels. LDRA provides a powerful, cost-effective, and flexible tool suite for railway software development The LDRA tool suite is the most complete software verification and validation solution for the development of rail system software.

The tools support the entire process from requirements through deployment, and help eliminate or reduce labour-intensive and error-prone activities.


EVS-EN 50128:2011/A1:2020

Quantitative Risk Analysis In some situations the qualitative risk analysis or the ALARP principle is insufficient: The safety people are torn and disagrees internally. Consequently, it is time to use the heavier "quantitative risk analysis"-tool. The fault tree is integrated into Excel and models a scenario, where a passenger is trapped between closing doors. All numbers and technical barriers are hypothetical.


What is EN 50128?



UNE-EN 50128:2012



EN 50126 / IEC 62278


Related Articles