Validating quality attribute requirements via execution‐based model checking

Abstract

SUMMARY This paper is concerned with the correct specification and validation of quality attribute requirements (QARs) that crosscut through a diverse set of complex system functions. These requirements act as modifiers of system level functional requirements and thus have substantial influence on the eventual architectural selection. Because system designers traditionally address these requirements one quality attribute at a time, the process frequently results in QARs that contain subtle conflicting behaviors. This paper presents an approach to QAR‐induced behavior validation and conflict detection via execution‐based model checking early in the software development process. It explores the concept of conflicts between requirements with temporal and sequencing behaviors and presents an automated approach for discovering such conflicts. Published 2012. This article is a US Government work and is in the public domain in the USA.

Model checking aircraft controller software: a case study

“…After we had finished the complete model of the SFCU software, including the environment input module and the periodic control module, we ran some simulations to check the behavior of the model in the file sfcu-sci-t1.pml, containing the PROMELA programs in Listings 6,7,8,9,10 and 11. Then we verified some general safety properties, such as the absence of invalid array indexes, deadlocks and infinite loops. These properties could be checked using the verification mode of SPIN by default, thus we did not need to state these properties as assertions or LTL formulae.…”

“…After 30 years' development, model checking has become a practical technology with a mature theoretical foundation . For example, formal verification and model checking have been applied to various verification projects of critical systems , such as the MILS system , the high‐performance computing software , the Storm Surge Barrier Control System , the European Train Control System , the Flight Control Systems of Airbus , spacecrafts , satellites and other embedded software .…”

“…After 30 years' development, model checking has become a practical technology with a mature theoretical foundation [6,7]. For example, formal verification and model checking have been applied to various verification projects of critical systems [8,9], such as the MILS system [10], the high-performance computing software [11], the Storm Surge Barrier Control System [12,13], the European Train 991 support user-defined properties that are specified as LTL formulae, although they support assertions. Third, as we mentioned in the requirements, we need to create an abstraction of the system.…”

Automatic builder of class diagram (ABCD): an application of UML generation from functional requirements

“…In fact, requirements engineering has become a real discipline where a huge variety of approaches, techniques, and tools have been proposed . In this context, the aim of this study is to propose a new approach that should facilitate the automatic mapping from textual requirements to UML class diagram with high accuracy.…”