Sequence diagram example T120B029P7 2012 pavasaris.

Slides:



Advertisements
Similar presentations
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Advertisements

Object-Oriented Analysis and Design CHAPTERS 15: UML INTERACTION DIAGRAMS 1.
Interaction Diagram Notation From Chapter 15 of Craig Larman, Applying UML and Patterns John Dalesandro.
Ana M. Fernández  A UML diagram that depicts: ◦ interactions between objects. ◦ how the business currently works by showing how various.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,
Lecture 5a: Sequence Interaction Diagrams CSE 111 Copyright W. Howden1.
THE OBJECT-ORIENTED DESIGN WORKFLOW UML2 Sequence Diagrams.
1 © Wolfgang Pelz UML2 UML Part Two. 2 © Wolfgang Pelz UML2 Chapters Four & Twelve Interaction Diagrams.
Chapter 15 Interaction Diagrams. Most Common Sequence Diagram Communication Diagram Sequence Diagrams illustrate interactions between classes of a program.
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.
Use Case Diagrams. Use Case Use case A view to system seen from outside(user) User’s requirements on system A set of scenario for an actor to achieve.
Use Case Modeling.
7M822 UML Interaction Diagrams 25 November 2010.
SE-565 Software System Requirements More UML Diagrams.
Coming up: Interaction Diagrams
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
Sequence Diagram Tutorial
מידול התנהגותי 1. Today’s Session Sequence Diagrams State Machines 2.
Use Case Diagrams. Use cases modeling Overview Motivation Communication between developers and users Users don’t know system, developers don’t know users’
UML / UML 2.0 Diagrams (Part III) 1. Sequence diagram is the most common kind of interaction diagram. It focuses on the message interchange between a.
1 SAD2 - UML 2 nd Lecture Sequence Diagram and other dynamic views Lecturer: Dr Dimitrios Makris
Interaction Modeling. Introduction (1) Third leg of the modeling tripod. It describes interaction within a system. The class model describes the objects.
Introduction to Interaction Diagrams Used to illustrate the dynamic behaviour of a community of objects that collaborate by passing messages in order to.
1 On to Object Design Chapter 14 Applying UML and Patterns.
Systems Analysis and Design in a Changing World, 6th Edition
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.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML Sequence Diagrams.
1 Modeling interactions and behavior Lecturer Dr. Mai Fadel.
Starting Object Design
Chapter 4: UML Interaction Diagrams. Objective Provide a reference for frequently used UML interaction diagram notation- sequence and communication diagrams.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
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.
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.
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.
Object Oriented Analysis and Design Sequence Diagrams.
1 On To Object Design Chapter 14 Applying UML and Patterns -Craig Larman.
CSCI-383 Object-Oriented Programming & Design Lecture 12.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
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 10: Statecharts.
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.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
Dr. Kivanc DincerCS319 Week 6 - Oct.17,20051 Chapter 14 Onto Object Design Objectives Understand dynamic and static object design modeling. Try agile modeling,
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.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 8 Advanced Interaction Modeling
UML Interaction Diagrams
Sequence Diagram.
Prepared By Sidra Noureen
Business System Development
UML Sequence Diagrams.
Object Oriented Analysis and Design
Princess Nourah bint Abdulrahman University
System Sequence Diagrams
Systems Analysis and Design in a Changing World, 6th Edition
Superior University, Lahore
Interaction Diagrams A Lot of UML!
UML Interaction diagrams
Appendix 3 Object-Oriented Analysis and Design
Presentation transcript:

Sequence diagram example T120B029P pavasaris

What is the purpose of sequence diagram ? The sequence diagram is used primarily to show the interactions between objects in the sequential order that those interactions occur. Developers think sequence diagrams were meant exclusively for them :-) Business staff can find sequence diagrams useful to communicate how the business currently works by showing how various business objects interact. A business-level sequence diagram can be used as a requirements document. During the requirements phase use cases are often refined into one or more sequence diagrams.

Sequence vs. Activity? Little bit later…

Notation 1/ An empty frame Lifeline

Notation 2 Sending a message/methos to another object The name is placed above the arrowed line And represents an operation/method that the receiving object's class implements.

Notation 3 Return messages – optional The use of return messages depends on the level of detail/abstraction Return value is placed above dotted line

Notation 4 Sending a message to itself the model draws attention to the fact that this processing takes place in the system object.

Notation 5 Asynchronous message

Notation 6 Who will guard the guardians themselves? Who will guard the guardians themselves

Combined fragments (alternatives, options, and loops) A combined fragment is used to group sets of messages together to show conditional flow in a sequence diagram. Alternatives - classic "if then else" logic Options - a simple "if then" without “else” Loops – a repetitive sequence

Alternatives mutually exclusive choice between messages

Option used to model a sequence that, given a certain condition, will occur; otherwise, the sequence does not occur.

Loops does not require guard condition be placed on it a guard can have two special conditions Minint = 1, Maxint = 5

Breaks most commonly used to model exception handling cause the exiting of an enclosing interaction's sequence. In cases where a break is part of combined fragment, then only that fragment is exited.

Nested diagrams Referencing another sequence diagram

Sequence(SD) vs. activity (AD)? AD mainly represent process flows. SD mainly represent step by step ordered in time interaction between different objects. AD also repersents an object role in workflow but level of repersenation is not dynamic like SD. Example: Object lifeline and detailed sequence of interaction

Online bookshop example

Facebook user authentication in a Web application

Submit comments (AJAX)