Basic protocols, message sequence charts, and the verification of requirements specifications

Abstract

Message sequence charts are a widely used notation to express requirements specifications of multi-agent systems. The semantics of message sequence charts can be defined algebraically in the theory of agents and insertion functions. Using this algebra, one can split message sequence chart scenarios into sets of Hoare triples consisting of precondition, the specification of a finite process, and a postcondition. We refer to such triples as "basic protocols." In this paper, we discuss tools to prove properties of systems described as basic protocols, such as the completeness (at each of its stages the system behavior has a possible continuation) and consistency (at each stage the system behavior is deterministic) of the specification, or the correspondence of the specified behavior to given scenarios. Together, these tools constitute a powerful environment for the formal verification of requirements specifications expressed through message sequence charts. *

Incremental approach to the technology of test design for industrial projects

“…Если каждому UCM элементу сопоставить тройку Хоара [11] или помеченный базовый протокол Летичевского [12], то поведенческая модель может быть представлена в виде неко-торой транзиционной системы S. Поведение системы S в состоянии α обозначается как S α . А.А.…”

Technology Aspects of State Explosion Problem Resolving for Industrial Software Design

“…In VRS/TAT technology Use Case Maps (UCM) notation [4] ( Fig.1) is used for high-level description of the model, while tools for automation of checking and generation work with model in basic protocols language [5]. (Fig.1) contains two interacting instances model description.…”

Distributed Testing of Multicomponent Systems

“…The tool helps to create the UCM model, add required information to metadata and translate it to base protocols (BP) [6]. One of the most important parts of the tool is UCM analysis module.…”

“…All of the above allows these specifications to be tested and verified.  Requirements checking with verification methods [6]. Generated test suite executable file set consists of one or more testing units and one control unit.…”

“…This paper reviews the technology of automated software testing based on automated generation of the test suite from the formal specifications of the system in Use Case Maps notation. Also it briefly outlines the usage of symbolic verification technique (UCM Specification Translator or UST and VRS [6]). Finally, the architecture of distributed testing system (TestCommander) is described, which allows automatic test suite execution and adjustment according to the SUT architecture.…”