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.

Slides:



Advertisements
Similar presentations
Object Design Examples with GRASP
Advertisements

System Sequence Diagrams
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
Jan 15, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale.
January Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box.
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.
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.
Drawing System Sequence Diagrams
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Chapter 10 System Sequence Diagrams. What is a System Sequence Diagram? A way of modeling input and output events related to systems It is a picture that.
Activity, Collaboration, and Component Diagrams Philip Liew
1 © Wolfgang Pelz UML2 UML Part Two. 2 © Wolfgang Pelz UML2 Chapters Four & Twelve Interaction Diagrams.
Use Cases & Requirements Analysis By: Mostafa Elbarbary.
Dynamic modeling using UML
NJIT Drawing System Sequence Diagrams Chapter 10 Applying UML and Patterns Craig Larman Presented by Anuradha Dharani.
Object-Oriented Analysis and Design
Sept Ron McFadyen1 Extend Relationship.
חוזים – Contracts 1. Larman – Chapter 10 – SSDs 10.2 What are System Sequence Diagrams? (introduction) Use cases describe how external actors interact.
9/18/011 Software Requirements Analysis and Design (Continued)
Object-Oriented Analysis and Design
LECTURE 5 SEQUENCE DIAGRAM 1. INTRODUCTION – SYSTEM SEQUENCE DIAGRAM A system sequence diagram is a fast and easily created artifact that illustrates.
TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.
Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative Development Part III Elaboration Iteration I – Basic1.
Sequence diagrams Chapter 5 Sommerville. Sequence diagrams Sequence diagrams are part of the UML and are used to model the interactions between the actors.
Class, Sequence and UML Model.  Has actors and use cases.
Object Oriented Analysis and Design System Events & Contracts.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
PRJ566 System Sequence Diagrams.  A system sequence diagram …. Illustrates input and output events related to the system under discussion.  Larman,
♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.
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.
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
Object-Oriented Analysis and Design CHAPTER 10: SYSTEM SEQUENCE DIAGRAMS 1.
Drawing System Sequence Diagrams
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
COMP-350 Object-Oriented Analysis and Design Drawing System Sequence Diagrams Reference: Larman, Chapter 9.
System sequence diagram M Taimoor Khan
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
CSCI-383 Object-Oriented Programming & Design Lecture 12.
System Sequence Diagram Chandan Rupakheti & Steve Chenoweth Week 5-3a.
Object-Oriented Analysis and Design Feb 2, 2009.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
Dynamic Models Sequence Diagrams Collaboration Diagrams Activity Diagrams.
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.
Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.
Summary from previous lectures
 System Sequence Diagrams Sheridan SYST Engineering Quality Systems 11.
SYSTEM-LEVEL SEQUENCE DIAGRAMS Sys466. System-Level Sequence Diagrams  Use cases describe how external actors interact with the software system…  An.
1 Object Oriented Analysis and Design System Events & Contracts.
Logical Architecture and UML Package Diagrams. The logical architecture is the large-scale organization of the software classes into packages, subsystems,
 Sequence Diagrams Introduction.  Sequence Diagrams  Review Schedule Sheridan.
Systems Analysis and Design in a Changing World, Fourth Edition
System Sequence Diagrams and Operation Contracts
UML Modeling Sequence diagram
BTS430 Systems Analysis and Design using UML
Webapp Design with System Sequence Diagrams
Sequence Diagrams.
Princess Nourah bint Abdulrahman University
How do we convince people that in programming simplicity and clarity —in short: what mathematicians call "elegance"— are not a dispensable luxury, but.
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
System Sequence Diagrams(SSD)
Use cases Dr. X.
Presentation transcript:

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 of SD? diagrams exploration diagrams exploration Group members: Edgaras, Ronaldas, Julius and Andrius

What is Sequence diagrams? A sequence diagram (SD) is a picture that shows, for one particular scenario of a use case, the events that external actors generate their order, and inter- system events. A sequence diagram (SD) is a picture that shows, for one particular scenario of a use case, the events that external actors generate their order, and inter- system events. Also SD is an interaction diagram that details how operations are carried out, what messages are sent. Also SD is an interaction diagram that details how operations are carried out, what messages are sent.

What is Sequence diagrams? SD are organized according to time. SD are organized according to time. The time progresses as you go down the page. The time progresses as you go down the page. The objects involved in the operation are listed from left to right according to when they take part in the message sequence. The objects involved in the operation are listed from left to right according to when they take part in the message sequence.

Why do we use SD? Because we have to design the software to handle these events (from the mouse, keyboard, another system, …) and execute a response. Basically a software system reacts the three things: Because we have to design the software to handle these events (from the mouse, keyboard, another system, …) and execute a response. Basically a software system reacts the three things: 1) External events from actors (humans or computers). 1) External events from actors (humans or computers). For example, when a cashier enters an item’s Id, the cashier is requesting the POS system to record that item’s sale (The enterItem event). That event initiates an operation upon the system. The use case text implies the enterItem event, and the SSD makes it concrete and explicit. For example, when a cashier enters an item’s Id, the cashier is requesting the POS system to record that item’s sale (The enterItem event). That event initiates an operation upon the system. The use case text implies the enterItem event, and the SSD makes it concrete and explicit. 2) Timer events. 2) Timer events. 3) Faults or exceptions (which are often from external sources). 3) Faults or exceptions (which are often from external sources).

What is the basic notation of sequence diagrams? A sequence diagram depicts the sequence of actions that accrue in a system. The invocation methods in each object, and the order in which the invocation accurse is captured in a SD. This makes the SD a very useful tool to easily represent the dynamic behavior of the system. A sequence diagram depicts the sequence of actions that accrue in a system. The invocation methods in each object, and the order in which the invocation accurse is captured in a SD. This makes the SD a very useful tool to easily represent the dynamic behavior of the system. A SD is two – dimensional in nature. An the horizontal axis, it show life of the object that it represents while on the vertical axis it shows the System of the creation or invocation of these objects. A SD is two – dimensional in nature. An the horizontal axis, it show life of the object that it represents while on the vertical axis it shows the System of the creation or invocation of these objects. Because it uses class name and object reference the SD is very useful in elaboration and detailing the dynamic design and the sequence and origin of invocation of objects. The SD is one of most widely used dynamic diagrams. Because it uses class name and object reference the SD is very useful in elaboration and detailing the dynamic design and the sequence and origin of invocation of objects. The SD is one of most widely used dynamic diagrams.

15.7 diagram Life line boxes and life lines and messages. Situation : Register and sale. Diagram shows how register and sale classes change they information

Diagram 15.8 Diagram shows 2 ways a return result from a message. Diagram shows 2 ways a return result from a message.

Diagram 15.9 This diagram shows message being sent from an object to itself by using a nested activation bar This diagram shows message being sent from an object to itself by using a nested activation bar