Ready for testing: ensuring conformance to industrial standards through formal verification

Sergio Feo-Arenis*, Bernd Westphal, Daniel Dietsch, Marco Muñiz, Siyar Andisha, Andreas Podelski

*Corresponding author for this work

Research output: Contribution to journalJournal articleResearchpeer-review

16 Citations (Scopus)

Abstract

The design of distributed, safety-critical real-time systems is challenging due to their high complexity, the potentially large number of components, and complicated requirements and environment assumptions that stem from international standards. We present a case study that shows that despite those challenges, the automated formal verification of such systems is not only possible, but practicable even in the context of small to medium-sized enterprises. We considered a wireless fire alarm system, regulated by the EN 54 standard. We performed formal requirements engineering, modeling and verification and uncovered severe design flaws that would have prevented its certification. For an improved design, we provided dependable verification results which in particular ensure that certification tests for a relevant regulation standard will be passed. In general we observe that if system tests are specified by generalized test procedures, then verifying that a system will pass any test following those test procedures is a cost-efficient approach to improve the product quality based on formal methods. Based on our experience, we propose an approach useful to integrate the application of formal methods to product development in SME.

Original languageEnglish
JournalFormal Aspects of Computing
Volume28
Issue number3
Pages (from-to)499-527
Number of pages29
ISSN0934-5043
DOIs
Publication statusPublished - 2016

Keywords

  • Certification tests
  • Dependability
  • Model Checking
  • Safety-critical systems
  • SME
  • Verification

Fingerprint

Dive into the research topics of 'Ready for testing: ensuring conformance to industrial standards through formal verification'. Together they form a unique fingerprint.

Cite this