Formal verification of non-functional requirements of overall instrumentation and control architectures

Polina Ovsiannikova, Antti Pakonen, Dmitry Muromsky, Maksim Kobzev, Viktor Dubinin, Valeriy Vyatkin

Research output: Contribution to journalArticleScientificpeer-review

14 Downloads (Pure)

Abstract

The design of safety-critical cyber-physical systems requires a rigorous check of their operation logic, as well as an analysis of their overall instrumentation and control (I&C) architectures. In this article, we focus on the latter and use formal verification methods to reason about the correctness of an I&C architecture represented with an ontology, using the example of a nuclear power plant design. A safe nuclear power plant must comply with the defense-in-depth principle, which introduces constraints on the physical and functional components of the I&C systems it consists of. This work presents a method for designing nonfunctional requirements using function block diagrams, its definition using logical programming, and demonstrates its implementation in a graphical tool, FBQL. The tool takes as input an ontology representing the I&C architecture to be checked and allows visual design of complex nonfunctional requirements as well as explanation of the results of the checks.

Original languageEnglish
Pages (from-to)616-631
Number of pages16
JournalIEEE Open Journal of the Industrial Electronics Society
Volume5
Early online date12 Jun 2024
DOIs
Publication statusPublished - 2024
MoE publication typeA1 Journal article-refereed

Keywords

  • Computer architecture
  • Formal verification
  • Function block diagrams
  • I&C architecture
  • Industrial electronics
  • Instruments
  • Ontologies
  • Power generation
  • Safety
  • logical programming
  • non-functional requirements
  • ontology
  • safety-critical systems
  • nonfunctional requirements
  • Function block diagrams (FBDs)
  • instrumentation and control (I&C) architecture

Fingerprint

Dive into the research topics of 'Formal verification of non-functional requirements of overall instrumentation and control architectures'. Together they form a unique fingerprint.

Cite this