Integration of sequential scenarios

Abstract

We give a formal relation-based definition of scenarios and we show how different scenarios can be integrated to obtain a more global view of user-system interactions. We restrict ourselves to the seqzlenlial case, meaning that we suppose that there is only one user (thus, the scenarios we wish to integrate cannot occur concurrently). Our view of scenarios is state-based, rather than event-based, like most of the other approaches, and can be grafted to the well-established specification language Z. Also, the end product of scenario integration, the specification of the functional aspects of the system, is given as a relation; this specification can be refined using independently developed methods. Our formal description is coupled with a diagram-based, transition-system like, presentation of scenarios, which is better suited to communication between clients and specifiers.

A Scenario Construction Process

“…Desharnais et al [51] describe a state-oriented relational approach to scenario and applies it to sequential scenarios. Scenarios here are atomic descriptions, in a Z style, of the interaction between the system and the environment represented by a triple (T, Re, Rs), where T is a space and Re and Rs are disjoint relations on T. The approach assumes that the scenarios fulfil certain consistency descriptions.…”

An Object-Oriented Approach to UML Scenarios Engineering and Code Generation

“…Some, such as Dano [28] and the SCR method [29], use a tabular notation for capturing scenarios, whereas others, such as Whittle and Schumann [30] and ourselves, use SequenceDs or CollDs. In contrast, Deharnais [31] describe scenarios with relations. For the specification description, a variety of notations are used.…”

An algebra of product families

“…Also, the literature regarding the sequential completion method for the development of software systems proposes a variety of solutions to the view reconciliation problem [9,39,42]. The views considered there are partial descriptions (e.g., scenarios or use-cases) of the functional requirements of a system.…”

“…To build up the overall specification of the system, these partial views are integrated and in this process any inconsistencies among them are detected. In [9] we find a relational approach to the integration of sequential scenarios, which are scenarios involving a single user. The integration is possible if the scenarios are consistent (from a behaviour perspective).…”