Copyright W. Howden1 Lecture 4: Sequence Interaction Diagrams.

Slides:



Advertisements
Similar presentations
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Advertisements

Introduction To System Analysis and Design
Copyright W. Howden1 Lecture 7: Functional and OO Design Descriptions.
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.
Lecture 5a: Sequence Interaction Diagrams CSE 111 Copyright W. Howden1.
Copyright W. Howden1 Lecture 3: Elaboration and System Architecture.
Copyright W. Howden1 Lecture 6: Design Evaluation and Intro to OO Design Patterns.
Copyright W. Howden1 Lecture 11: UML Terminology and Additional Models and Notation.
1 © Wolfgang Pelz UML2 UML Part Two. 2 © Wolfgang Pelz UML2 Chapters Four & Twelve Interaction Diagrams.
Copyright W. Howden1 Lecture 5: Collaboration Diagrams.
Lecture 5b: Basic Design Patterns CSE 111. Basic Design Patterns We know our subsystem interface classes and (some of) their methods We need to create.
System Architecture Lecture 3 CSE 111 Spring /22/20151Copyright William E. Howden.
1 Lecture 2: Elaboration Tasks and Domain Modeling.
Software Engineering I Object-Oriented Design
1 Lecture 1: Processes, Requirements, and Use Cases.
Copyright W. Howden1 Lecture 6: Collaboration Diagrams.
© Copyright Eliyahu Brutman Programming Techniques Course.
Copyright W. Howden1 Lecture 2: Elaboration Tasks and Domain Modeling.
Object-Oriented Systems Analysis and Design Using UML
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Lecture a: Additional UML Models: Package, Activity, Deployment Lecture b: Generalization, Aggregation and Additional Domain Model Notation Copyright W.
Lab 6 CPIT 250 System Analysis and Design.
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Chapter 7: The Object-Oriented Approach to Requirements
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.
Interaction diagrams Sequence and collaboration diagrams.
Introduction to Sequence Diagrams
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
Copyright © Hsiao-Lan Wei All Rights Reserved Design Model Interaction diagram.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Interaction and Communication Diagrams Patrick Bailey Keith Vander Linden Calvin College.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Information Systems Engineering Interaction Diagrams: Sequence Diagram Collbortion Diagram.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Sequence Diagrams And Collaboration Diagrams HungNM.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
UNIFIED MODELING LANGUAGE(UML) BY Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 15 The Unified Modeling Language: a Primer.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
1 SEQUENCE DIAGRAM EXAMPLE The domain model, showing the navigability of the associations, and the Reserve video (staff scenario) use-case description.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
 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 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
1 Kyung Hee University Interaction Diagrams Spring 2001.
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.
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.
Object-Oriented Analysis and Design
Object-Oriented Systems Analysis and Design Using UML
Sequence Diagram.
Object Oriented Analysis and Design
Requirements To Design In This Iteration
Unified Modeling Language
Lecture 4: Sequence Interaction Diagrams
Interaction diagrams.
Sequence Diagrams Getting the Message.
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.
UML Interaction diagrams
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Presentation transcript:

Copyright W. Howden1 Lecture 4: Sequence Interaction Diagrams

Copyright W. Howden2 Behavioral vs Static Models Describe interactions between entities Sequence Diagrams Collaboration Diagrams Message Sequence Charts State Charts Describe structure of complex entities Class Diagrams Entity-relationship models

Copyright W. Howden3 Sequence Diagrams - Components Objects –Actors, subsystems, class instances Messages –One object sends a message to another message Each diagram describes a scenario, or what happens during a use of the system System described by a collection of diagrams

Copyright W. Howden4

5 Applicability System/Actor interaction –Requirements elaboration Subsystem interactions –Requirements elaboration and design Subsystem design –Object properties and class visibility

Copyright W. Howden6 System Actor Interaction Investigate the interactions the user has with the system Specify the needed user interface forms –Specify contents/capabilities of GUI before graphical design Following example note: In the actor/system interaction we see self- messages notation

7

Copyright W. Howden8 Subsystems Interaction Show the messages that the subsystems send back and forth Enforce a layers architecture Identify the subsystems interface/proxy In the following example we see the alternatives notation, which allows multiple related flows to be included in

9

Copyright W. Howden10 Additional Examples Get a Date Scenario –Includes conditionals allowing alternative paths in same scenario/ISD Start up Scenario –Shows interactions with system Log On Scenario Exit/Log Off Scenario

11

Copyright W. Howden12

13

Copyright W. Howden14

Copyright W. Howden15 Additional Notation Focus of Control –Indicate when an object’s lifestream is “active” Data return from a sent message Iteration of message

Copyright W. Howden16

Copyright W. Howden17 Systematic Object Identification for Sequence Diagrams Rational Software approach (Rational now part of IBM and source of Rational Unified Process) Four kinds of objects –Actor –Boundary/Form –Entity/Data –Control

Copyright W. Howden18 Boundary Objects Place where the actors interface with the system Referred to as forms by some methods

Copyright W. Howden19 Entity Data type objects Place where information is stored Data Bases

Copyright W. Howden20 Control Coordinates the activities of the use case Often identified with a use case, with one per use case Possible controller objects in O/O –Use Case, Role, System/subsystem, and Business

Copyright W. Howden21

Copyright W. Howden22 Additional Notations – Message Synchronization Synchronous: sender waits until receiver has processed message Procedure call: receiver is ready to receive call, sender waits for return from call. A kind of synchronous Asynchronous: sender sends message and then continues regardless of status of receiver Balking: if receiver is not ready to receive message it is abandoned

Copyright W. Howden23 Application to Distributed Systems Sequence diagrams show collections of interactions between components in system, like subsystem interaction diagrams Can use to develop specifications for components, with individual state diagrams

Copyright W. Howden24 DS Scenarios For Distributed System Scenario 1 –User who is a member logs on and asks for a date. A date is found. Client relies on server to supply first and subsequent records from member Data base. Scenario 2 –User logs on who is not a member. Then a user who is a member logs on. The client eventually asks the server for the next record and nil is returned since there are no more. Client displays a sorry-no-date message.

25

Copyright W. Howden26

Copyright W. Howden27 Developing a State Model Specification for a Component Factor the sequence diagrams, e.g. for the Client, get all the client lifelines Decide where the states are –E.g. For Client, each new GUI Frame? Not always an exact match with the traces –After each message received

Copyright W. Howden28

Copyright W. Howden29