Automatic verification of railway interlocking systems: a case study
FMSP '98 Proceedings of the second workshop on Formal methods in software practice
Verification of a safety-critical railway interlocking system with real-time constraints
Science of Computer Programming
Modelling large railway interlockings and model checking small ones
ACSC '03 Proceedings of the 26th Australasian computer science conference - Volume 16
An Automated Approach for the Interpretation of Counter-Examples
Electronic Notes in Theoretical Computer Science (ENTCS)
Practical declarative model transformation with tefkat
MoDELS'05 Proceedings of the 2005 international conference on Satellite Events at the MoDELS
Model-Driven engineering in a large industrial context — motorola case study
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Development of model based tools to support the design of railway control applications
SAFECOMP'07 Proceedings of the 26th international conference on Computer Safety, Reliability, and Security
Modelling railway interlocking tables using coloured petri nets
COORDINATION'10 Proceedings of the 12th international conference on Coordination Models and Languages
| Hi-index | 0.00 |
Railroad interlocking software drives specialised micro-devices, known as interlocking controllers. These controllers primarily actuate railroad points and change signal aspects in real-time, based on sensor and timer input. Due to their central function in railroad control, interlocking controllers and their firmware are safety-critical. The firmware programs, which mimic physical relays, are written in variants of domain-specific programming languages based on ladder logic. The programs have to comply with a more abstract specification of allowable states of sections of railroad track and equipment, known as a control table. The translation of a track layout and associated control tables into ladder logic-based code is manual, and hence subject to costly review and rework cycles. In this report, we describe a case study that uses a model-driven tool-chain as an automated alternative to the existing process. The two domain languages, control table and ladder logic, were modelled and transformations were implemented between the two models, and from model to program text. We report on implementation challenges, and describe the outlook and scalability of the approach in this application domain.