When developing safety critical rail control software, achieving compliance with safety standards such as CENELEC EN50128 is a significant part of the project. Traditionally, this involves a number of manual steps such as reviewing verification documents, making test plans and reports and, of course, testing itself.
These activities are typically carried out at a later stage of the project, where delays can significantly impact the overall schedule and any issues discovered are costly to address. Furthermore, the highly experienced staff who have the qualifications needed to perform these tasks are often a bottleneck resource.
The solution is to consider safety, and how it is demonstrated, from the start of the project, and to use more automation throughout the verification process. Much of the work of achieving compliance with safety standards can be replaced with Formal Verification. A technique based on mathematical proofs that gives 100% coverage. Since Formal Verification gives full coverage and is fully automated, not only will it increase safety confidence but it will also help reduce the overall cost for safety assessment.
What you will learn in this guide
In this guide, you will learn how to use Formal Verification to meet prevailing safety requirements with full confidence. All while reducing effort, increasing quality, and reducing the risk for project delays in the process.
On the following pages, we will summarize the safety requirements for rail control software set out by the prevailing CENELEC EN 50128 standard, discuss the advantages of using Formal Verification versus traditional system testing methods, and take a closer look at how Formal Verification impacts the verification and validation process and safety approval in rail control projects. Finally, we will explore how Formal Verification is used in practice and offer some recommendations for the implementation process.