Chapter 18.

Slides:



Advertisements
Similar presentations
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Advertisements

Chapter 29 State Machine Diagrams Sate Machine Diagrams Represent state of an object Behavior as reaction to events.
Object Design Examples with GRASP
System Sequence Diagrams
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.
Object-Oriented Analysis and Design
Drawing System Sequence Diagrams
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
NJIT Object Design Examples with GRASP Chapter 18 Applying UML and Patterns Craig Larman Presented By : Ajay Alegonda.
NJIT Drawing System Sequence Diagrams Chapter 10 Applying UML and Patterns Craig Larman Presented by Anuradha Dharani.
Object-Oriented Analysis and Design
Figure 1.1 The observer in the truck sees the ball move in a vertical path when thrown upward. (b) The Earth observer views the path of the ball as a parabola.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Chapter 28 Activity Diagrams Model processes: –Business processes –Workflow –Data flow –Complex algorithms.
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.
CSSE 374: More GRASP’ing and Use Case Realization Steve Chenoweth Office: Moench Room F220 Phone: (812) These.
SENG 403 SENG 403 – Winter  Brief introduction to SSD  Example (A sales systems (Cashier))  Example (Monopoly game) SENG 403 – Winter 2012.
GRASP Pattern Zhen Jiang West Chester University
Chapter 18 Object Design Examples with GRASP. Objectives Design use case realizations –A use-case realization describes how a particular use case is realized.
1 Ch 18. Object Design Examples With Grasp Objectives Design use case realizations. Apply GRASP to assign responsibilities to classes. Apply UML to illustrate.
Chapter 7: Object Design Examples with GRASP. Objective Design use case realizations. Apply GRASP to assign responsibilities to classes. Apply UML to.
Chapter 26 GoF Design Patterns. The Adapter Design Pattern.
GRASP: Designing Objects With Responsibilities Chapter 17 Applying UML and Patterns -Craig Larman.
Object Design Examples with GRASP (Ch. 18)
17. GRASP—Designing Objects with Responsibilities III CSE5324 Lecture Quiz 17 due at 5 PM Thursday, 8 October 2015.
Review ♦ System sequence diagram ♦ Domain model
1 Lecture 6: Operation Contracts. 2 Overview  What is contract ?  The guidelines for writing contracts for the system operations.  Use Case realizations.
Operation Contracts: Getting ready to open the “System” black box All material from Applying UML and Patterns, 3 rd Edition, Craig Larman, chapter 11.
♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.
Larman ch. 131 Use-Case Model : Adding Detail with operation contracts Larman ch. 13.
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
Chapter 11 Operation Contracts. What They Are An operation is a specification of a transformation or query that an object may be called on to execute.
Operation Contracts. Primary way to describe system behavior is with use cases Operation contracts provide more details in terms of state changes to objects.
Week 4 Operational Contracts Requirements to Design Logical Architecture.
OO Methodology Elaboration Iteration 2 - Design Patterns -
TK2023 Object-Oriented Software Engineering CHAPTER 12 Introduction to Responsibility-Driven Design.
Object-Oriented Analysis and Design Week 11, 2009.
GRASP: Designing Objects With Responsibilities
OO Methodology Elaboration Phase Iteration 1- Part 3.
Chapter 8 Work Reengineering and Conceptual Design.
Summary from previous lectures
1 Chapter 9: Operation Contracts Chapter 13 in Applying UML and Patterns Book.
Software Engineering 1 Object-oriented Analysis and Design Chap 31 More SSDs and Contracts.
CSCI 6461 Final Review Spring Chapters/Topics Covered Ch 7 From Modules to Objects Ch 10 Requirements Workflow Ch 11 Analysis Workflow Ch 12 Design.
1 Design Model Use-Case realizations with GRASP Larman chapter 17.
OO Methodology Elaboration Phase Iteration 1- Part 2.
Logical Architecture and UML Package Diagrams. The logical architecture is the large-scale organization of the software classes into packages, subsystems,
Object Design Examples with GRASP
Systems Analysis and Design in a Changing World, 6th Edition
System Sequence Diagrams and Operation Contracts
System sequence diagrams
DESIGN MODEL: USE-CASE REALIZATIONS WITH GRASP PATTERNS
GRASP : Designing Objects with Responsibilities
Sequence Diagrams.
Sequence Diagrams Lecture 6.
Systems Analysis and Design in a Changing World, 6th Edition
Interaction Diagrams A Lot of UML!
Chapter 23 Iteration 2.
Chapter 11: Class Diagram
State Machine Diagrams
System Sequence Diagrams(SSD)
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Operation Contracts Ch. 11.
Design Model: Creating Design Class Diagrams
Presentation transcript:

Chapter 18

Use Case Realization Implement a Use Case Implement one or more scenarios (Use case is sum of all scenarios)

Fig. 18.1 Use Case Realization

Realization Use case SSD – contain: Systems operations Build communications diagrams or sequence diagrams

Fig. 18.2 Sys Ops in Communication diagrams

Fig. 18.3 Sys Ops in Interaction diagrams

Operational Contracts Fill in details in an interaction diagram Look at enterItem Contract Post condition : sli is created

Fig. 18.4 Apply post condition

Fig. 18.5 Design makeNewSale

Example NextGen Now walk through the design

Fig. 18.6 Create new sale

Fig. 18.7 enterItem Interaction Diagram

Fig. 18.8 Data Class Diagram

Fig. 18.9 How to complete a sale

Fig. 18.10 getTotal

Fig. 18.11 & 18.12

Fig. 18.13 Payment

Fig. 18.14 Alt choice

Fig. 18.15 Log complete sale

Fig. 18.16 get balence

Fig. 18.17 Final DCD

Connect the UI

Fig. 18.18 enterItem

Fig. 18.19 Add getTotal

Fig. 18.20 Sys Start

Fig. 18.28