Jan 15, 200391. 3913 Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale.

Slides:

Advertisements

Similar presentations

Object Design Examples with GRASP

Advertisements

Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.

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 16, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration 1: a simple cash-only success scenario of Process Sale.

Jan Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box Actors.

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

January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.

Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” - may be of.

Fall 2009ACS-3913 Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,

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.

Fall 2009ACS Ron McFadyen1 The context maintains an instance of a concrete state subclass State Pattern Each subclass (concrete state) implements.

Oct Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

NJIT Drawing System Sequence Diagrams Chapter 10 Applying UML and Patterns Craig Larman Presented by Anuradha Dharani.

Object-Oriented Analysis and Design

Object Interaction Modeling

Marcelo Santos – OOAD-CDT309, Spring 2008, IDE-MdH 1 Object-Oriented Analysis and Design - CDT309 Period 4, Spring 2008 More on use cases System sequence.

Slide 1 Chapter 8 Behavioral Modeling. Slide 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports.

Sept Ron McFadyen1 Extend Relationship.

Fall 2009ACS-3913 Ron McFadyen1 From the Merriam-Webster’s online dictionary ( Main Entry: an·thro·po·mor·phism Date: 1753 an interpretation.

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.

SENG 403 SENG 403 – Winter  Brief introduction to SSD  Example (A sales systems (Cashier))  Example (Monopoly game) SENG 403 – Winter 2012.

INFO 620Lecture #51 Information Systems Analysis and Design Sequence and Collaboration Diagrams INFO 620 Glenn Booker.

Chapter 18 Object Design Examples with GRASP. Objectives Design use case realizations –A use-case realization describes how a particular use case is realized.

Object Oriented Analysis and Design System Events & Contracts.

Object Design Examples with GRASP (Ch. 18)

Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.

SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.

Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.

Review ♦ System sequence diagram ♦ Domain model

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.

OOSE Use Case. Requirement Functional: –Features, capabilities, and security Non Functional: –Usability: Human factors, help, and documentation –Reliability:

PRJ566 System Sequence Diagrams.  A system sequence diagram …. Illustrates input and output events related to the system under discussion.  Larman,

Chapter 9 Applying UML and Patterns -Craig Larman

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

COMP-350 Object-Oriented Analysis and Design Drawing System Sequence Diagrams Reference: Larman, Chapter 9.

System sequence diagrams

Software Engineering 1 Object-oriented Analysis and Design Chap 24 Iteration 2 More Patterns.

System Sequence Diagram Chandan Rupakheti & Steve Chenoweth Week 5-3a.

TK2023 Object-Oriented Software Engineering CHAPTER 12 Introduction to Responsibility-Driven Design.

CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.

January Ron McFadyen1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain of interest.

Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.

PRESENTATION ON USE CASE. Use Case Modeling Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is.

OO Methodology Elaboration Phase Iteration 1- Part 3.

Software Engineering 1 Object-oriented Analysis and Design Chap 31 More SSDs and Contracts.

Dr. Awais Majeed Object Oriented Design and UML.

Oct 3, Ron McFadyen1 GRASP Patterns 1.Expert 2.Creator 3.Controller 4.Low Coupling 5.High Cohesion.

SYSTEM-LEVEL SEQUENCE DIAGRAMS Sys466. System-Level Sequence Diagrams  Use cases describe how external actors interact with the software system…  An.

Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,

1 Object Oriented Analysis and Design System Events & Contracts.

Jan Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,

Object Design Examples with GRASP

Elaboration popo.

System Sequence Diagrams and Operation Contracts

BTS430 Systems Analysis and Design using UML

Webapp Design with System Sequence Diagrams

Prepared By Sidra Noureen

Behavioral Modeling.

Sequence Diagrams.

Sequence Diagrams Lecture 6.

Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book

System Sequence Diagrams(SSD)

Object Oriented Analysis

Presentation transcript:

Jan 15, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale beginning a wide-and-shallow design and implementation touches on many major architectural elements begins with a expansion of the Use Case Model with a System Sequence Diagram to clarify the input and output system events

Jan 15, Ron McFadyen2 Simple cash-only Process Sale scenario 1. Customer arrives at a POS checkout with goods and/or services to purchase 2. Cashier starts a new sale 3. Cashier enters item identifier 4. System records sale line item and presents item description, price, and running total Cashier repeats steps 3-4 until indicates done 5. System presents total with taxes calculated 6. Cashier tells customer the total and asks for payment 7. Customer pays and System handles payment...

Jan 15, Ron McFadyen3 System Sequence Diagram a picture showing actors and systems, lifelines, messages, time for a particular scenario for SSDs we will be ignoring an “activation box” that is normally placed on a lifeline :Cashier :System an arbitrary cashier a cashier object the software system to be developed We’ll see it as a black box

Jan 15, Ron McFadyen4 Sequence Diagram object-oriented systems perform tasks by interacting with each other through the passing of messages a sequence diagram is an interaction diagram that emphasizes the messaging sequence A sequence diagram illustrates the dynamic behaviour of a system of objects The arrow we utilize ( ) is for procedural or synchronous messages – where the sender sends a message, transfers control to the receiving object, and waits for a response To indicate a return message and the explicit return of control, we use Ch 15 discusses interaction diagrams more fully

Jan 15, Ron McFadyen5 System Sequence Diagram :Cashier :System Message at Time1 from :Cashier to :System Response at Time2 from :System to :Cashier Earlier events are above later events in the diagram time travels downward Time1 earlier than Time2: Time1 < Time2 message response

Jan 15, Ron McFadyen6 Figure 9.1

Jan 15, Ron McFadyen7 Figure 9.3 There are 4 system events shown here. The cashier will interact with the system in 4 ways. The events are given operation names: makeNewSale, enterItem, endSale, makePayment.