modelling interactions and behaviour. © lethbridge/laganière 2005 chapter 8: modelling...

Modelling Interactions and Behaviour

Chapter 8: Modelling Interactions and Behaviour 2© Lethbridge/Laganière 2005

Interaction Diagrams

Interaction diagrams are used to model the dynamic aspects of a software system

• They help you to visualize how the system runs.

• An interaction diagram is often built from a use case and a class diagram.

—The objective is to show how a set of objects accomplish the required interactions with an actor.


Interactions and messages

• Interaction diagrams show how a set of actors and objects communicate with each other to perform:

—The steps of a use case, or

—The steps of some other piece of functionality.

• The set of steps, taken together, is called an interaction.

• Interaction diagrams can show several different types of communication.

—E.g. method calls, messages send over the network

—These are all referred to as messages.


Elements found in interaction diagrams

• Instances of classes

—Shown as boxes with the class and object identifier underlined

• Actors

—Use the stick-person symbol as in use case diagrams

• Messages

—Shown as arrows from actor to object, or from object to object


Creating interaction diagrams

You should develop a class diagram and a use case model before starting to create an interaction diagram.

• There are two kinds of interaction diagrams:

—Sequence diagrams

—Collaboration diagrams


Sequence diagrams – an example


Sequence diagrams

A sequence diagram shows the sequence of messages exchanged by the set of objects performing a certain task

• The objects are arranged horizontally across the diagram.

• An actor that initiates the interaction is often shown on the left.

• The vertical dimension represents time.

• A vertical line, called a lifeline, is attached to each object or actor.

• The lifeline becomes a broad box, called an activation box during the live activation period.

• A message is represented as an arrow between activation boxes of the sender and receiver.

—A message is labelled and can have an argument list and a return value.


Sequence diagrams – same example, more details


Sequence diagrams – an example with replicated messages

• An iteration over objects is indicated by an asterisk preceding the message name


Sequence diagrams – an example with object deletion

• If an object’s life ends, this is shown with an X at the end of the lifeline


Communication diagrams – an example


Communication diagrams

Communication diagrams emphasise how the objects collaborate in order to realize an interaction

• A communication diagram is a graph with the objects as the vertices.

• Communication links are added between objects

• Messages are attached to these links.

—Shown as arrows labelled with the message name

• Time ordering is indicated by prefixing the message with some numbering scheme.


8.2 State Diagrams

A state diagram describes the behaviour of a system, some part of a system, or an individual object.

• At any given point in time, the system or object is in a certain state.

—Being in a state means that it is will behave in a specific way in response to any events that occur.

• Some events will cause the system to change state.

—In the new state, the system will behave in a different way to events.

• A state diagram is a directed graph where the nodes are states and the arcs are transitions.


State diagrams – an example

• tic-tac-toe game


States

• At any given point in time, the system is in one state.

• It will remain in this state until an event occurs that causes it to change state.

• A state is represented by a rounded rectangle containing the name of the state.

• Special states:

—A black circle represents the start state

—A circle with a ring around it represents an end state


Transitions

• A transition represents a change of state in response to an event.

—It is considered to occur instantaneously.

• The label on each transition is the event that causes the change of state.


State diagrams – an example with conditional transitions


State diagrams – an example of transitions with time-outs and conditions


Activities in state diagrams

• An activity is something that takes place while the system is in a state.

—It takes a period of time.

—The system may take a transition out of the state in response to completion of the activity,

—Some other outgoing transition may result in:- The interruption of the activity, and

- An early exit from the state.


State diagram – an example with activity


Actions in state diagrams

• An action is something that takes place effectively instantaneously

—When a particular transition is taken,

—Upon entry into a particular state, or

—Upon exit from a particular state

• An action should consume no noticeable amount of time


State diagram – an example with actions


State diagrams – another example


State diagram – an example with substates


8.3 Activity Diagrams

• An activity diagram is like a state diagram.

—Except most transitions are caused by internal events, such as the completion of a computation.

• An activity diagram

—Can be used to understand the flow of work that an object or component performs.

—Can also be used to visualize the interrelation and interaction between different use cases.

—Is most often associated with several classes.

• One of the strengths of activity diagrams is the representation of concurrent activities.


Activity diagrams – an example


8.4 Implementing Classes Based on Interaction and State Diagrams

• You should use these diagrams for the parts of your system that you find most complex.

—I.e. not for every class

• Interaction, activity and state diagrams help you create a correct implementation.

• This is particularly true when behaviour is distributed across several use cases.

—E.g. a state diagram is useful when different conditions cause instances to respond differently to the same event.


Example: The CourseSection class

States:

• ‘Planned’:closedOrCancelled == false && open == false

• ‘Cancelled’:closedOrCancelled == true &&

registrationList.size() == 0

• ‘Closed’ (course section is too full, or being taught):closedOrCancelled == true &&

registrationList.size() > 0



States:

• ‘Open’ (accepting registrations):open == true

• ‘NotEnoughStudents’ (substate of ‘Open’):open == true &&

registrationList.size() < course.getMinimum()

• ‘EnoughStudents’ (substate of ‘Open’):open == true &&

registrationList.size() >= course.getMinimum()



Class diagram



public class CourseSection{ // The many-1 abstraction-occurrence association (Figure 8.2) private Course course; // The 1-many association to class Registration (Figure 8.2) private List registrationList;

// The following are present only to determine the state // (as in Figure 8.19). The initial state is 'Planned‘ private boolean open = false; private boolean closedOrCanceled = false;



public CourseSection(Course course){ this.course = course; registrationList = new LinkedList();}

public void openRegistration(){ if(!closedOrCanceled) // must be in 'Planned' state { open = true; // to 'OpenNotEnoughStudents' state }}



public void closeRegistration(){ // to 'Canceled' or 'Closed' state open = false; closedOrCanceled = true; if (registrationList.size() < course.getMinimum()) { unregisterStudents(); // to 'Canceled' state }}

public void cancel(){ // to 'Canceled' state open = false; closedOrCanceled = true; unregisterStudents();}


Example: The CourseSection classpublic void requestToRegister(Student student){ if (open) // must be in one of the two 'Open' states { // The interaction specified in the sequence diagram of Figure 8.4 Course prereq = course.getPrerequisite(); if (student.hasPassedCourse(prereq)) { // Indirectly calls addToRegistrationList new Registration(this, student); } // Check for automatic transition to 'Closed' state if (registrationList.size() >= course.getMaximum()) { // to 'Closed' state open = false; closedOrCanceled = true; } }}



// Private method to remove all registrations // Activity associated with 'Canceled' state. private void unregisterStudents() { Iterator it = registrationList.iterator(); while (it.hasNext()) { Registration r = (Registration)it.next(); r.unregisterStudent(); it.remove(); } } // Called within this package only, by the constructor of // Registration to ensure the link is bi-directional void addToRegistrationList(Registration newRegistration) { registrationList.add(newRegistration); }}

modelling interactions and behaviour. © lethbridge/laganière 2005 chapter 8: modelling...

Documents

modelling interactions

messages interaction

kinds of interaction

behaviour8 sequence

use case diagrams messages

behaviour3 interactions

required interactions

lifeline slide