Formal Methods in Industrial Software Standards Enforcement

Model‐based quality assurance of protocol documentation: tools and methodology

“…Moreover, the model and test‐suite development is not part of an industrial scale process. From the same group also comes work for deriving formal specifications from standards 15, applying a process for gathering requirements from an English document similar to the PQAP's. However, this work does not yet apply a full tool chain down to MBT from these requirements.…”

“…Spec Explorer is often classified as finite state machine testing, though there are only some commonalities: notably its guarded‐update machines are similar to those found in EFSM notations, and that similar traversal techniques for the final step are applied in both domains. The approach is actually closer to labelled transition systems (LTS) based testing and IOCO 15, except that Spec Explorer uses alternating simulation with buffering as the conformance notion. Alternating simulation has been introduced by Alur et al 11, and is used in other tools 17.…”

Model-Based Testing of Safety Critical Real-Time Control Logic Software

“…We got added evidence that an important advantage of a model based testing technology complemented with a strong process of formalization of requirements consists in possibility to reveal bugs at earlier stages [7]. In particular, some problems concerning correctness, unambiguity and completeness [16,17] of the decision control algorithms were revealed.…”

Verification of Operating System Components

“…UniTESK was used for conformance test suite creation for Core part of Linux Standard Base (LSB), which describes system libraries and almost coincides with POSIX, in OLVER Project [10], where 1532 functions of LSB Core was formally specified and tested. The same method was applied in conformance test suite development for ARINC-653 part 1 standard [11] describing 54 functions.…”