Oeritte: User-Friendly Counterexample Explanation for Model Checking

Polina Ovsiannikova*, Igor Buzhinsky, Antti Pakonen, Valeriy Vyatkin

*Corresponding author for this work

Research output: Contribution to journalArticleScientificpeer-review

2 Downloads (Pure)

Abstract

Thorough verification is a part of the design process of instrumentation and control systems if they must comply with crucial safety requirements. Model checking can be applied to the formal model of such a system to reason about its correctness based on the specification provided. When a violation occurs, the model checking tool outputs the proof of the violation in the form of a failure trace, which represents a state sequence of system model transitions where the requirement does not hold. This sequence, however, even for modular systems, is a mere table of values. Due to the lack of any insights into the inner model processes and structures that caused a problem, the debugging process of the formal model becomes time and effort consuming. The tool presented in this paper, Oeritte, is aimed at assisting the analyst in this challenge. It implements a method for automatic visual counterexample explanation which includes reasoning both over the falsified LTL formula and over the NuSMV function block diagram of the formal model of the system. The tool is applied to an industrial-sized safety control system of a nuclear power plant.

Original languageEnglish
Article number9405616
Pages (from-to)61383-61397
Number of pages15
JournalIEEE Access
Volume9
DOIs
Publication statusPublished - 15 Apr 2021
MoE publication typeA1 Journal article-refereed

Keywords

  • Counterexample explanation
  • counterexample visualization
  • Delays
  • function block diagram
  • Input variables
  • Model checking
  • NuSMV
  • Power generation
  • Safety
  • Tools
  • user-friendly model checking
  • Visualization

Fingerprint

Dive into the research topics of 'Oeritte: User-Friendly Counterexample Explanation for Model Checking'. Together they form a unique fingerprint.

Cite this