Industrialising a proof-based verification approach of computerised interlocking systems

S. Behnia, A. Mammar, J. M. Mota, N. Breton, P. Caspi, P. Raymond

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

This paper describes the formal verification of an interlocking system.We have formally proved the non-derailing and non-collision safety properties for an existing interlocking system operating on Paris Metros line 3Bis. These high-level properties have first been refined to an intermediate level permitting their expression in terms of the control systems inputs and outputs. The resulting properties have then been formalised in the Prover iLock Verifier engines internal language. The Prover iLock Verifier engine is a COTS commercialised by Prover Technology. For this project some specific features have been added to the engine to provide certified proofs that can be used, instead of testing, in the SIL-4 qualification process of interlocking systems.

Original languageEnglish
Title of host publicationComputer System Design and Operation in the Railway and Other Transit Systems - Computers in Railways XI
Pages143-152
Number of pages10
DOIs
Publication statusPublished - 1 Dec 2008
Externally publishedYes
Event11th International Conference on Computer System Design and Operation in the Railway and Other Transit Systems, COMPRAIL 2008 - Toledo, Spain
Duration: 15 Sept 200817 Sept 2008

Publication series

NameWIT Transactions on the Built Environment
Volume103
ISSN (Print)1743-3509

Conference

Conference11th International Conference on Computer System Design and Operation in the Railway and Other Transit Systems, COMPRAIL 2008
Country/TerritorySpain
CityToledo
Period15/09/0817/09/08

Keywords

  • Environment modelling
  • Formal verification
  • Interlocking application
  • Proof certification

Fingerprint

Dive into the research topics of 'Industrialising a proof-based verification approach of computerised interlocking systems'. Together they form a unique fingerprint.

Cite this