1 Kyung Hee University Interaction Diagrams Spring 2001.

Slides:



Advertisements
Similar presentations
UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student.
Advertisements

1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
Software Engineering COMP 201
Systems Analysis and Design in a Changing World, Fourth Edition
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
THE OBJECT-ORIENTED DESIGN WORKFLOW UML2 Sequence Diagrams.
Essentials of class models. 2 A very simple class model In UML, a class is shown in a class diagram as a rectangle giving its name.
7M822 UML Sequence Diagrams 2 December 2010.
1 © Wolfgang Pelz UML2 UML Part Two. 2 © Wolfgang Pelz UML2 Chapters Four & Twelve Interaction Diagrams.
Essentials of interaction diagrams Lecture 23 & 24.
Essentials of interaction diagrams Lecture Outline Collaborations Interaction on collaboration diagrams Sequence diagrams Messages from an object.
Dynamic modeling using UML
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
03/12/2001 © Bennett, McRobb and Farmer Use Case Diagrams Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
SE-565 Software System Requirements More UML Diagrams.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
Unified Modeling Language
SEQUENCE DIAGRAM Prepared by: T. Fatimah Alageel.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
UML Collaboration Diagram. Recap System Sequence Diagrams (SSD) UML for SSD Examples.
Interactions. 2 Objects communicate with each other by sending messages. Sending a message is another name for a member function call. –Some C++ examples.
Interaction diagrams Sequence and collaboration diagrams.
Introduction to Interaction Diagrams Used to illustrate the dynamic behaviour of a community of objects that collaborate by passing messages in order to.
10/16/2015CPSC , CPSC , Lecture 61 Software Engineering, CPSC , CPSC , Lecture 6.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 9: Interaction.
1 Modeling interactions and behavior Lecturer Dr. Mai Fadel.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
UML Class Diagram Trisha Cummings. What we will be covering What is a Class Diagram? Essential Elements of a UML Class Diagram UML Packages Logical Distribution.
Collaboration Diagrams CSIS3600. What is a Collaboration Diagram Collaboration diagrams illustrate interactions between objects The collaboration diagram.
Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Interaction and Communication Diagrams Patrick Bailey Keith Vander Linden Calvin College.
Sequence diagram in UML Martin Palkovik. Sequence diagram  It is a graphic representation of system operations based on chronology - a time sequence.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Interaction Diagrams Interaction Diagrams allow the designer to show how groups of objects collaborate in some behavior. –Interaction Diagrams will show.
Interaction Diagram Notation
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour UML Sequence Diagram.
Object-Oriented Analysis and Design 1 Mira Balaban & Arnon Sturm Object-Oriented Analysis and Design Session 3a: Behavioral Modeling - Interactions.
Use Case realization How classes collaborate to realize use cases or system functionality.
1 Kyung Hee University Diagram Editor : Design View Spring 2001.
1 Kyung Hee University Statecharts Spring Kyung Hee University Specifying Objects’ Behaviour  Interaction diagrams show message-passing behaviour.
1 Kyung Hee University Constraints Spring Kyung Hee University Graphical Notations  Graphical notations are well suited for displaying structural.
1 Kyung Hee University Modeling with Objects Spring 2001.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Collaboration diagrams. Purpose A collaboration diagram is an alternate way to show a scenario. A collaboration diagram shows the objects and relationships.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 3: Introducing the UML
Diagram Editor : Use Case VIew
Class Diagram Lecture # 1. Class diagram A Class Diagram is a diagram describing the structure of a system shows the system's classes Attributes operations.
Communication Diagrams Lecture 8. Introduction  Interaction Diagrams are used to model system dynamics  How do objects change state?  How do objects.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
1 Object Oriented Analysis System modeling = Functional modeling + Object modeling + Dynamic modeling Functional modeling = Use cases Object modeling =class.
ITEC1301 Object-Oriented Systems Construction Lecture Notes #4 1.
Project 2: Phase 1 Submission 7 Late submissions 10% 10 No submissions 14% Better than project 1 phase 3 submissions 10-point bonus: If you catch the deadline.
Systems Analysis and Design in a Changing World, Fourth Edition
UML Diagrams By Daniel Damaris Novarianto S..
Interactions.
Collaboration Diagrams
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Chapter 11: Collaboration Diagram - PART1
Communication DIAGRAM
Interactions.
Requirements To Design In This Iteration
Interaction diagrams.
Unified Modelling Language
Interaction diagrams Interaction diagrams are models that describe how groups of objects collaborate in some behavior. Typically, an interaction diagram.
UML Interaction diagrams
Communication DIAGRAM
Presentation transcript:

1 Kyung Hee University Interaction Diagrams Spring 2001

2 Kyung Hee University Introduction  Class diagrams are used to specify the static structure of a system  Object diagrams are used to illustrate potential states of the system are typically used only for illustrative purposes  To specify an interaction, it must be stated which messages will be sent, in which order, and under which circumstances. collaboration diagrams and sequence diagrams are referred to as interaction diagrams two types of diagram provide alternative ways of expressing the same information

3 Kyung Hee University Collaborations  Interactions are illustrated by adding messages to an object diagram  In order to achieve the required generality, interaction diagram in UML are based on the general notion of a collaboration, rather than on object diagrams.  A collaboration is a general description of the ways in which objects can be linked together in order to support the behavior to be supported.  Collaborations are related to class diagrams, as both of them specify ways in which objects can be linked together.

4 Kyung Hee University Collaborations (cont’d)  Collaborations specify only those which are relevant to a particular type of interaction. whereas class diagrams specify all the possible object structures in a system  Collaborations are defined not simply in terms of classes, but rather in terms of the roles that instances of those classes can play in various interactions

5 Kyung Hee University Classifier Roles  Collaborations consists of roles  A role describes a particular way in which an object can participate in an interaction.  A classifier role describes a role that objects can play in interactions  Notation for a classifier role : the name of the role and its base class

6 Kyung Hee University Association Roles  A collaboration consists of a number of classifier roles connected by association roles It consists of three classifier roles, linked by two association roles  for finding the cost of a part in the stock control program

7 Kyung Hee University Transient Links  An association between two classes implies that instances of the classes can be linked and messages sent between them.  Short lived links are known as transient links situations in which objects are able to communicate to distinguish transient links from links that are instances of associations.

8 Kyung Hee University Transient Links  Parameter ‘part’ is used as the name of the corresponding classifier role, and the association role connecting to the assembly object is labeled with the appropriate stereotype to indicate that this link exists because of the parameter that was passed.

9 Kyung Hee University Interaction Diagram  Sequence diagram showing classifier roles only, but making the sequencing of messages very clear.  Collaboration diagram showing classifier and association roles, and superimposing messages on association roles  The major difference between the two forms of diagram is the way they show the order in which message are sent.

10 Kyung Hee University Sequence Diagrams  The classifier roles involved in the interaction are displayed at the top of the diagram Each role has a dashed line, known as its lifeline Activation : the period of time during which an object is processing a message designated as a narrow rectangle whose top is connected to a message.

11 Kyung Hee University Collaboration Diagrams  Unlike sequence diagram, collaboration diagrams show association as well as classifier roles messages sequencing cannot be shown graphically

12 Kyung Hee University Collaboration Diagrams (cont’d)  Hierarchical numbering of messages reflecting explicitly the structure of nested activations

13 Kyung Hee University Object Creation The relationship between orders and order lines is one of composition, because we assume that when an order is destroyed all lines of that order are also destroyed.

14 Kyung Hee University Object Creation (cont’d)  Object creation on a sequence diagram

15 Kyung Hee University Object Creation (cont’d)  Object creation on a collaboration diagram In order to distinguish elements that are created during the course of an interaction from those which existed at the start, classifier and association roles corresponding to new objects and links are annotated with the property ‘new’.

16 Kyung Hee University Object Destruction  Messages which cause the destruction of objects are labeled with the stereotype ‘destroy’.

17 Kyung Hee University Object Destruction (cont’d)  Object deletion on a collaboration diagram

18 Kyung Hee University Iterated Messages  Showing a collaboration which uses this notation to show that an assembly involved in an interaction can contain zero or more components.  Classifier roles and multiplicity

19 Kyung Hee University Iterated Messages (cont’d)  In order to find out the cost of an assembly, a message must be sent to each of the components, no matter how many there are.  To emphasize the fact that a single symbol could correspond to multiple messages, notation is added to message label to indicate an iterated message send.  Iterated message passing on a collaboration diagram

20 Kyung Hee University Iterated Messages (cont’d)  Iteration diagram passing on a collaboration diagram

21 Kyung Hee University Multiobjects  An alternative way of showing multiplicity information associated with a classifier role is to use a multiobject. a multipoint represents a collection of objects of the base type of the multiobject  Showing multiplicity with a multiobject

22 Kyung Hee University Multiobjects (cont’d)  Showing an order object sending a message to a collection of order lines, asking for the line which corresponds to the catalogue entry with part number ‘n’.

23 Kyung Hee University Multiobjects (cont’d)  Finding the total cost of an order

24 Kyung Hee University Conditional Messages  A boolean expression written in square brackets

25 Kyung Hee University Conditional Messages (cont’d)  Condition messages on collaboration diagrams

26 Kyung Hee University Conditional Messages (cont’d)  Alternative messages on a sequence diagram

27 Kyung Hee University Conditional Messages (cont’d)  Messages to Self

28 Kyung Hee University Conditional Messages (cont’d) Recursive activations are not shown so explicitly on collaboration diagram but, each recursive activation gives rise to an extra level of hierarchy in the numbering of subsequent messages