Sequence diagrams Practice 7. Task 1  The “Author” sends his paper to the “Editor” by the message “manuscript” and waits the confirmation.

Slides:



Advertisements
Similar presentations
Case Studies Elevator control system Elevator control system Comet case studies From task structuring to target system configuration.
Advertisements

Object-Oriented Analysis and Design CHAPTERS 15: UML INTERACTION DIAGRAMS 1.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
Interaction Diagrams Activity Diagram State Machine Diagram
Copyright W. Howden1 Lecture 7: Functional and OO Design Descriptions.
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.
Copyright W. Howden1 Lecture 4: Sequence Interaction Diagrams.
Project Doors Group Doors 3 Presenters: Becky Smith, Tim Hollosy Demo Given by: Tim Hollosy.
Collaboration Diagrams. Example Building Collaboration Diagrams.
Sequence Diagram. What is Sequence Diagram?  Sequence Diagram is a dynamic model of a use case, showing the interaction among classes during a specified.
7M822 UML Interaction Diagrams 25 November 2010.
7M822 UML Sequence Diagrams 5 October 2009.
Blaha and Rumbaugh Sections 7.2 and 8.2
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
Object Oriented Software Development
1 Object Oriented Analysis and Design. 2 Object-Oriented Analysis  Statement of what our client wants Object-Oriented Design  How to provide it using.
Interaction diagrams Sequence and collaboration diagrams.
Welcome to CIS 083 ! Events CIS 068.
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.
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.
 2000 Deitel & Associates, Inc. All rights reserved. Optional Case Study - Chapter 5 Outline 5.1 Introduction 5.2 Collaborations 5.3 Creating Collaborations.
 2000 Deitel & Associates, Inc. All rights reserved. Optional Case Study - Chapter 4 Outline 4.1 Introduction 4.2 Class Operations 4.3 Creating Class.
 2000 Deitel & Associates, Inc. All rights reserved. Optional Case Study - Chapter 3 Outline 3.1 Introduction 3.2 Class Attributes 3.3 Statechart Diagrams.
1 Modeling interactions and behavior Lecturer Dr. Mai Fadel.
Starting Object Design
Collaboration Diagrams CSIS3600. What is a Collaboration Diagram Collaboration diagrams illustrate interactions between objects The collaboration diagram.
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.
Information Systems Engineering Interaction Diagrams: Sequence Diagram Collbortion Diagram.
2Object-Oriented Program Development Using C++ 3 Basic Loop Structures Loops repeat execution of an instruction set Three repetition structures: while,
Coming up: Interaction Diagrams Sequence Diagrams Dan Fleck.
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 And Collaboration Diagrams HungNM.
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”
Essentials of Counter-Controlled Repetition Counter-controlled repetition requires: Control variable (loop counter) Initial value of the control variable.
Alice in Action with Java Chapter 4 Flow Control.
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.
1 Kyung Hee University Interaction Diagrams Spring 2001.
 2000 Deitel & Associates, Inc. All rights reserved. Optional Case Study - Chapter 6 Outline 6.1 Introduction 6.2 Implementation: Visibility 6.3 Implementation:
Activity diagrams Practice 7. Task 1  The first action in the activity is the adding the item to the order. If the order if formed (“ready”), then it.
Sequence diagrams Lecture 5. Main terms  Interaction  Life line  Activation  Executable behavior and derived behavior  Messages  Trajectory  Frame.
UNIT-IV Designing Classes – Access Layer ‐ Object Storage ‐ Object Interoperability.
Collaboration Diagrams
Overheads for Computers as Components
Sequence Diagram.
Communication DIAGRAM
Optional Case Study - Chapter 4
Sequence Diagram.
BBC Microbit.
Interactions.
Object Oriented Analysis and Design
תכן UML in Design מקורות: S. R. Schach: Chapter 12
Princess Nourah bint Abdulrahman University
IMAT5205 Systems Analysis and Design
Lecture 4: Sequence Interaction Diagrams
Interaction diagrams.
Sequence Diagrams Getting the Message.
Interaction diagrams Interaction diagrams are models that describe how groups of objects collaborate in some behavior. Typically, an interaction diagram.
UML Interaction diagrams
Use Cases Based on the paper
Communication DIAGRAM
Computer Science Core Concepts
Software Design (SE321) Lect6-Collaboration Diagram
UML Interaction Diagrams
Chapter 4 Sequence Diagrams
Presentation transcript:

Sequence diagrams Practice 7

Task 1  The “Author” sends his paper to the “Editor” by the message “manuscript” and waits the confirmation of receipt. The editor sends the paper to the reviewer (“Peer”) by the message “evaluate”. The reviewer sends the editor a message with an assessment of the paper “review”. The editor sends the author a message with results “resolution” and sends the reviewer his gratitude “thanks”.  Build the structural model of the interaction in the form of collaboration “ReviewManuscript”, specify the multiplicity of the role of reviewer so as the paper is send for review to one of five reviewers.  Specify, using the fragments, that the paper is sent for review to any three of five reviewers.  Using fragments, show, that the order of sending the results of the paper reviewing to the author and sending the gratitude to the reviewers doesn’t matter.

Task 2  The passenger (“Person”) comes into the elevator and presses the button (“pressButton”) with the number of the floor (“floor”). The lift closes doors and starts moving with the synchronous calling the operation “startMoving”. After that it shows the passenger the numbers of the moved floors by the message “floorReached”. Then lift calls the operation “stopMoving” and stops. The passengers presses the button (“pressDoors”) for making the doors opened.  How can you clarify the mode, if it is known that a lift works from the first to the fifth floors?  Specify that before pressing the button with a number of floor the person must close the doors (“pressDoors”).  Using fragments, show that a passenger can’t press buttons for opening and closing of the door while moving.  Specify that a lift moves one floor for 3 sec.

Task 3  The sequence diagram “SelectFloor” contains the lifeline of the cage, represented by the instance of the active class “Cabin”, the lifeline “floor” of the instance of the class “FloorButton” with selector “1” and the lifeline of the class “Algorithm”. The interaction starts from the synchronous calling of the operation for button “isPressed” at the lifeline “floor” from the cage. This operation returns the boolean value “true” if the button is pressed. Then the instance of the class “Cabin” calls the operation “selectFloor” at the algorithm.  Using the operator of a cycle (loop) show that there is a check of all buttons if they are pressed. The variable of the cycle with a number of the floor must be declared as an attribute of the interaction.  Add calls of the operations of specifying numbers of floors which buttons are pressed.  Give the example of the allowed and forbidden paths at this interaction.