Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is an Actor, the one who initiated the Use Case Each.

Slides:



Advertisements
Similar presentations
System Sequence Diagrams
Advertisements

Ana M. Fernández  A UML diagram that depicts: ◦ interactions between objects. ◦ how the business currently works by showing how various.
Jan 15, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale.
Design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must.
Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is typically an Actor, the one who initiates Each.
Sequence Diagram Objects are represented horizontally across the top of the diagram Each object has a lifeline some exist before and/or after some are.
Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together to achieve some functionality.
Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects show the flow of control across many objects used to.
Jan Ron McFadyen1 Consider a simple cash-only Process Sale scenario 1. Customer arrives at a POS checkout with goods and/or services to purchase.
Sept Ron McFadyen Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together.
Drawing System Sequence Diagrams
Slide 6C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
Sept Ron McFadyen Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is typically an Actor,
THE OBJECT-ORIENTED DESIGN WORKFLOW UML2 Sequence Diagrams.
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 Outline Collaborations Interaction on collaboration diagrams Sequence diagrams Messages from an object.
Introduction to the Sequence Diagrams with stereotypes Department of Information Systems and Computation (DSIC) Valencia Polytechnic University.
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.
Lab 6 CPIT 250 System Analysis and Design.
Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is typically an Actor, the one who initiates Each.
7M822 UML Sequence Diagrams 5 October 2009.
UML. Overview of UML Diagrams Structural : element of spec. irrespective of time Class Component Deployment Object Composite structure Package Behavioral.
LECTURE 5 SEQUENCE DIAGRAM 1. INTRODUCTION – SYSTEM SEQUENCE DIAGRAM A system sequence diagram is a fast and easily created artifact that illustrates.
SEQUENCE DIAGRAM Prepared by: T. Fatimah Alageel.
INFO 620Lecture #51 Information Systems Analysis and Design Sequence and Collaboration Diagrams INFO 620 Glenn Booker.
CS3773 Software Engineering
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.
1 Sequence Diagrams (Based on Stevens and Pooley (2006, Chapters 9, 10) and Fowler (2004, Chapter 4)) David Meredith Aalborg University.
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.
Computer Science 340 Software Design & Testing UML Sequence Diagrams.
Group 2 work What is sequence diagram ? What is sequence diagram ? Why do we use it ? Why do we use it ? What is basic notation of SD? What is basic notation.
Sequence diagram in UML Martin Palkovik. Sequence diagram  It is a graphic representation of system operations based on chronology - a time sequence.
Information Systems Engineering Interaction Diagrams: Sequence Diagram Collbortion Diagram.
Drawing System Sequence Diagrams
Sequence Models.
Interaction Diagrams Interaction Diagrams allow the designer to show how groups of objects collaborate in some behavior. –Interaction Diagrams will show.
A Student Guide to Object- Oriented Development Chapter 10 Designing objects and classes.
Sequence Diagrams Sequence; Interaction Diagrams Behavioral Diagrams
Interaction Diagram Notation
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour UML Sequence Diagram.
COMP-350 Object-Oriented Analysis and Design Drawing System Sequence Diagrams Reference: Larman, Chapter 9.
1 Objectives: Sequence Diagram 1. You will able to create a sequence diagram. 2. Assign objects in sequence diagrams to classes 3. Map messages to operations.
Object Oriented Analysis and Design Sequence Diagrams.
1 Examining Execution Sequences Introducing Sequence Diagrams.
UML Diagrams CSC 422 Kutztown University Dr. Daniel Spiegel.
CSCI-383 Object-Oriented Programming & Design Lecture 12.
Collaboration diagrams. Purpose A collaboration diagram is an alternate way to show a scenario. A collaboration diagram shows the objects and relationships.
Interaction Diagram An interaction diagram is a graphical representation of interactions between objects. Sequence diagram: shows the sequence in which.
Slide 12D.88 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach.
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
 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.
1 Object Oriented Analysis System modeling = Functional modeling + Object modeling + Dynamic modeling Functional modeling = Use cases Object modeling =class.
System Sequence Diagrams and Operation Contracts
Standard UML: Communication and Dynamic Behavior
UML Modeling Sequence diagram
Webapp Design with System Sequence Diagrams
Sequence and Collaboration Diagrams
Sequence Diagrams.
Object Oriented Analysis and Design
Sequence Diagrams Lecture 6.
Interaction diagrams.
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
Interaction diagrams Interaction diagrams are models that describe how groups of objects collaborate in some behavior. Typically, an interaction diagram.
Software Design (SE321) Lect6-Collaboration Diagram
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
Presentation transcript:

Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is an Actor, the one who initiated the Use Case Each object has a lifeline some exist before and after the Use Case some are created during the Use Case some are destroyed during the Use Case An active object is indicated by a narrow rectangle (on the activation stack) Time is represented vertically down the diagram. Time moves forward as you go downwards

Figure 15.2 Sequence Diagram

Figure 15.4 Sequence diagram

Figure Focus of control

Figure Showing returns

Figure Message to ‘this’

Figure Destroying an object

Figure Conditional message

Figure Mutually exclusive conditional messages

Figure Iteration

Figure Iteration over a sequence of messages

Figure Iteration over a multiobject

Figure Messages to a class itself, not an object

Sequence Diagram - example Check to see if there is enough quantity on hand If there is, then remove that quantity from inventory and create a delivery item for those goods If there is not enough on hand, then create a back order line item We have 4 objects: an orderLine, product, delivery line item, and a back order line item. The delivery line item and back order line item will be created during the scenario

Sequence Diagram - example :OLine:Product 1:hasStock:=checkQOH() 2:[hasStock]remove() :DelItem 3:[hasStock]new() :BOItem 4:[not hasStock]new() Message numbers are not necessary on SD, and are not shown in the text.

Sequence Diagram - example 2 Check the quantity on hand if there is adequate stock, then check for the need to reorder if we need to reorder then create a reorder line item

Sequence Diagram - example 2 :OLine:Product 1:hasStock:=checkQOH() 2:[hasStock] remove() :RItem 2.1:needToReorder:=checkLevel() 2.3:[needToReorder] new()

Sequence Diagram - example 3 For each line of a purchase order check the quantity on hand if there is enough, remove the quantity from inventory

Sequence Diagram - example 3 :OLine:Product 1.1:hasStock:=checkQOH() 1.2:[hasStock] remove() :PO 1:*[for each line] checkQOH()

Sequence Diagram Example Consider the sequence of events: For each line of a purchase order Check the quantity on hand If there is enough, remove that quantity from inventory create a delivery item for those goods check for the need to reorder if we need to reorder then create a reorder line item If there is not enough on hand, then create a back order line item

As a Sequence Diagram :OLine:Product hasStock:=checkQOH() [hasStock] remove() :PO *[for each line] checkQOH() :DelItem :BOItem [hasStock] new() [not hasStock] new() :RItem needToReorder := checkLevel() [needToReorder] new()

As a Collaboration Diagram :POrder :OLine : DelItem {new} 1*[for all order lines] checkQOH() 1.1: hasStock:=checkQOH() 1.2: [hasStock] remove() 1.2.1: needToReorder := checkLevel() 1.2.2:[needToReorder] new() 1.3a: [hasStock] new() :Product :RItem {new} 1.3b: [not hasStock] new() :BOItem {new}