Behavior Modeling with Interaction Diagrams in a UML and OCL Tool

Abstract

This contribution discusses system modeling with UML behavior diagrams. We consider statecharts and both kinds of interaction diagrams, i.e., sequence and communication diagrams. We present new implementation features in a UML and OCL modeling tool: (1) Sequence diagram lifelines are extended with states from statecharts, and (2) communication diagrams are introduced as an alternative to sequence diagrams. We assess the introduced features and propose a systematic set of features which should be available in both kinds of interaction diagrams. We emphasize the role that OCL can play for such a feature set.

Extracting frame conditions from operation contracts

“…More precisely, the following models have been considered: (1) the running example from this paper (i.e., the Smartphone model from Fig. 1), (2) a model representing a toll collecting system (TollCollect, [19]), (3) a model representing a scheduling process, e.g., of a CPU (Scheduler, [20]), (4) a model representing the process of lending books (Library, [21]), (5) a model representing the civil status of human beings (Civil Status, [22]), (6) a model representing a traffic light preemption (TrafficLight, [23]), and (7) a model representing an access system at an (Airport_CML, [24]). …”