Traceability process for large OO projects

Proceedings of the 5th ACM International Conference on Distributed Event-Based System

et al. 2011

Scenarios are useful in modeling external behavior of a system, and design patterns are useful in bridging from what is required to how to build it in a given context. Together, scenarios and design patterns, can be a basis for an effective approach to modeling and evaluating alternative designs of event-driven reactive systems. However, both techniques are informal and imprecise for purposes of evaluating implementations. Here we demo a tool based on a precise model of scenarios and design patterns that allows for executing and evaluating a system's implementation relative to required scenarios and design alternatives.

Section: Precision Modeling Of Scenarios and Design Patterns: A Necesmentioning

confidence: 99%

A scenario and design pattern based tool for modeling and evaluating implementations of event-based reactive systems

Radonjic

Bashardoust

Proceedings of the 5th ACM International Conference on Distributed Event-Based System

et al. 2011

“…Semantically, however, these three views overlap considerably [3,4]. That is, they present much of the same conceptual information from different perspectives and with varying levels of detail.…”

Section: Introductionmentioning

confidence: 99%

“…In particular, the behavioral view expresses the complete behavior of each component (or class) of a system in terms of states and transitions, typically organized into hierarchical state machines [5]. Conversely, the interactions view captures how system requirements map onto sequences of responsibilities to be executed by components [3,4,6]. Such sequences are generally referred to as scenarios.…”

Section: Introductionmentioning

confidence: 99%

On the Importance of Inter-scenario Relationships in Hierarchical State Machine Design

Bordeleau

Fundamental Approaches to Software Engineering

2001

Abstract. One of the most crucial and complicated phases of system development lies in the transition from system behavior (generally specified using scenario models) to the detailed behavior of the interacting components (typically captured by means of communicating hierarchical finite state machines). This transition constitutes the focus of this paper. Our standpoint is that in order to succeed with this transition, it is not sufficient to grasp the details of individual scenarios, but also to understand the relationships that exist between the scenarios. Our claim is that different types of scenario relationships result in different hierarchical state machine structures. We identify and describe four different types of scenario relationships: containment dependency, alternative dependency, temporal dependency, and functional dependency. We also illustrate how such scenario relationships can be expressed in UML using stereotypes and how they guide the design of the corresponding hierarchical state machines.

“…For example, in the context of the ATM system, a "fast cash" ATM machine (i.e., a machine that only allows for withdraw and account update) can easily be assembled from existing state machines, with only minor modifications. • Because it associates a role state machine with each scenario, the State Machine Integration pattern allows establishing a strong traceability relation [7,11] between the structure of a hierarchical state machine and the scenarios that it must satisfy. Also other patterns defined in [2] (see Figure 1) allow establishing a traceability relationship between specific types of inter-scenario relationships and state machine structure.…”

Section: Consequencesmentioning

confidence: 99%

A scenario-based approach to hierarchical state machine design

Bordeleau

Proceedings Third IEEE International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC 2000) (Cat. No. PR0060

Selić³

Self Cite

One of the most crucial and complicated phases of realtime system development lies in the transition from system behavior (generally specified using scenario models) to the behavior of interacting components (typically captured by means of communicating hierarchical finite state machines). It is commonly accepted that a systematic approach is required for this transition. In this paper, we overview such an approach, which we root in a hierarchy of "behavior integration patterns" we have elaborated. The proposed patterns guide the structuring of a component's behavior, and help in integrating the behavior associated with new scenarios into the existing hierarchical finite state machine of a component. One of these patterns is discussed at length here.