Ana M. Fernández  A UML diagram that depicts: ◦ interactions between objects. ◦ how the business currently works by showing how various.

Slides:



Advertisements
Similar presentations

Advertisements

Object-Oriented Analysis and Design CHAPTERS 15: UML INTERACTION DIAGRAMS 1.
System Sequence Diagrams
Interaction Diagram Notation From Chapter 15 of Craig Larman, Applying UML and Patterns John Dalesandro.
THE OBJECT-ORIENTED DESIGN WORKFLOW UML2 Sequence Diagrams.
Lecture 3 CS171: Game Design Studio 1I UC Santa Cruz School of Engineering 11 January.
1 © Wolfgang Pelz UML2 UML Part Two. 2 © Wolfgang Pelz UML2 Chapters Four & Twelve Interaction Diagrams.
Object Collaborations. Objectives: Object Interaction (cont.) You will be able to:  Use sequence diagrams to detail object interactions.
Dynamic modeling using UML
Sequence Diagram. What is Sequence Diagram?  Sequence Diagram is a dynamic model of a use case, showing the interaction among classes during a specified.
Sequence diagram example T120B029P pavasaris.
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.
SENG 403 SENG 403 – Winter  Brief introduction to SSD  Example (A sales systems (Cashier))  Example (Monopoly game) SENG 403 – Winter 2012.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Sequence Diagram Tutorial
CS3773 Software Engineering
Class, Sequence and UML Model.  Has actors and use cases.
מידול התנהגותי 1. Today’s Session Sequence Diagrams State Machines 2.
1 CSC 450 Slides adapted from slides created by Robert B. France UML Behavioral Models.
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.
System Sequence Diagrams. Recap When to create SSD? How to identify classes/instances? Use case descriptions UML notations for SSD.
Chapter 5 – System Modeling
1 On to Object Design Chapter 14 Applying UML and Patterns.
1 Sequence Diagrams (Based on Stevens and Pooley (2006, Chapters 9, 10) and Fowler (2004, Chapter 4)) David Meredith Aalborg University.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML Sequence Diagrams.
Chapter 4: UML Interaction Diagrams. Objective Provide a reference for frequently used UML interaction diagram notation- sequence and communication diagrams.
1 UML Sequence Diagrams UML Distilled, Third Edition, Chapter 4 M. Fowler.
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.
Drawing System Sequence Diagrams
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.
Sequence Diagrams CSIS3600. Sequence Diagrams A sequence diagram shows an interaction arranged in time sequence. In particular, it shows the objects participating.
Object Oriented Analysis and Design Sequence Diagrams.
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.
Chapter 3: Introducing the UML
Communication Diagrams Lecture 8. Introduction  Interaction Diagrams are used to model system dynamics  How do objects change state?  How do objects.
 The Sequence Diagram models the collaboration of objects based on a time sequence.  It shows how the objects interact with others in a particular scenario.
More on UML 1. 1.Use-case diagram 2.Class diagram [Object diagram] (static) 1.1 Domain/analysis model – of reality 1.2 Design model – of decisions 3.
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.
Basics of RSA Rational Software Architect. What is RSA? Comprehensive Modeling and Development environment that leverages the Unified Modeling Language.
UML Activity and Sequence Diagrams David Millard
Sequence diagrams Lecture 5. Main terms  Interaction  Life line  Activation  Executable behavior and derived behavior  Messages  Trajectory  Frame.
Sequence Diagrams CECS 343 Mimi Opkins.
UML Interaction Diagrams
UML SEQUENCE DIAGRAM.
Chapter 11: Collaboration Diagram - PART1
Sequence and Collaboration Diagrams
Sequence Diagram.
Prepared By Sidra Noureen
Sequence Diagram.
Sequence Diagrams.
UML Sequence Diagrams.
Object Oriented Analysis and Design
Princess Nourah bint Abdulrahman University
System Sequence Diagrams
Superior University, Lahore
Week 12: Activity & Sequence Diagrams
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Unified Modelling Language
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
Interaction Diagrams A Lot of UML!
Interaction diagrams Interaction diagrams are models that describe how groups of objects collaborate in some behavior. Typically, an interaction diagram.
UML Interaction diagrams
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
Chapter 4 Sequence Diagrams
Presentation transcript:

Ana M. Fernández

 A UML diagram that depicts: ◦ interactions between objects. ◦ how the business currently works by showing how various business objects interact.  Purpose: 1. Model flow of control 2. Identify synchronization 3. Illustrate typical scenarios

 The focus is less on messages themselves and more on the order in which messages occur.  The diagram conveys this information along 2 dimensions: ◦ the vertical dimension shows, top down, the time sequence of messages/calls as they occur, ◦ the horizontal dimension shows, left to right, the object instances that the messages are sent to.

 Instance Name : Class Name ◦ Underlined  specific instance (Bill, Fred) ◦ Not underlined  kind of instance or role (buyer, seller)

 Message =a line to the receiving object with: ◦ a solid arrowhead (if a synchronous call operation) ◦ a stick arrowhead (if an asynchronous signal)  The message/method name is placed above the arrowed line.  Return message = dotted line with an open arrowhead back to the originating lifeline (above the return value from the operation).

 To model mutually exclusive choice between two or more message sequences (if then else)  The word "alt" is placed inside the frame's namebox.  Operands are separated by a dashed line.

 To model a sequence that, given a certain condition, will occur; otherwise, the sequence does not occur (If then).  The word “opt" is placed inside the frame's namebox.

 To model a repetitive sequence.  The word “loop" is placed inside the frame's namebox (add the minimum and maximum of iterations)

 To model parallel processing activities.  The word “par" is placed inside the frame's namebox.  Break up the frame  horizontal operands separated by a dashed line.

 Messages: ◦ Synchronous ◦ Asynchronous ◦ Return  Alternative  Option  Loop  Pararell