Chapter 3 Case Studies.

Slides:



Advertisements
Similar presentations
Point of Sale (POS) Client & Back Office Server. Operational Concept What is our Objective? What is our Objective? What are our Goals? What are our Goals?
Advertisements

Chapter 11 Designing the User Interface
Chapter 29 State Machine Diagrams Sate Machine Diagrams Represent state of an object Behavior as reaction to events.
Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.
Object-Oriented Analysis and Design
Object-Oriented Analysis and Design CHAPTERS 12-14: INTRODUCTION TO DESIGN 1.
Design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must.
COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.
NJIT More GRASP Patterns Chapter 22 Applying UML and Patterns Craig Larman Prepared By: Krishnendu Banerjee.
Case Study The NextGen POS System
NJIT 1 Iteration 2 Requirements and More GRASP Chapter 24.
Jan 8, Ron McFadyen1 Waterfall Spiral UP Case study UML Use Cases.
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.
March R McFadyen1 Figure 30.2 Layers in NextGen They only have three layers in this architecture Each layer is shown as a UML Package No separate.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Designing with Interaction and Design Class Diagrams Chapters 15 & 16 Applying UML and Patterns Craig Larman With some ideas from students in George Blank’s.
TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.
Objectives Design Class Diagrams Issues in system design Generalization Review UML papers.
Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”
Chapter 13 Starting Design: Logical Architecture and UML Package Diagrams.
Computer System Overview Chapter 1. Operating System Exploits the hardware resources of one or more processors Provides a set of services to system users.
GRASP Principles. How to Design Objects The hard step: moving from analysis to design How to do it? –Design principles (Larman: “patterns”) – an attempt.
Chapter 18 Object Design Examples with GRASP. Objectives Design use case realizations –A use-case realization describes how a particular use case is realized.
Week 10 Iteration 3 What is here Iteration 3 works like iteration 2 More OO design This week more UML.
Chapter 17. GRASP General Responsibility Assignment Software Patterns (Principles) OOD: after identifying requirements, create domain model, define responsiblities.
Chapter 7: Object Design Examples with GRASP. Objective Design use case realizations. Apply GRASP to assign responsibilities to classes. Apply UML to.
1 ITEC 3010 “Systems Analysis and Design, I” LECTURE 10: Use Case Realizations [Prof. Peter Khaiter]
Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.
GRASP: Designing Objects With Responsibilities
Software Architecture in Practice Architectural description (The reduced version)
SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler
TK2023 Object-Oriented Software Engineering CHAPTER 3 CASE STUDY: POS SYSTEM.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Chapter 17 GRASP: Designing Objects with Responsibilities. 1CS6359 Fall 2011 John Cole.
Black Box Testing Focuses in the functional requirements of the program It is not an alternative to white-box techniques It is a complementary approach.
Chapter 13 Logical Architecture and UML Package Diagrams 1CS6359 Fall 2012 John Cole.
Domain Model Refinement Larman, chapter 31 CSE 432: Object-Oriented Software Engineering Glenn D. Blank, Lehigh University.
Chapter 9 Applying UML and Patterns -Craig Larman
Sept Ron McFadyen1 Today Sept 16: Chapters 1, 2, 3 Introductory material Next Tuesday Sept 21: Rational Rose and Use Cases Chapter 6 - Use.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
What to remember from Chap 13 (Logical architecture)
Software Engineering 1 Object-oriented Analysis and Design Chap 24 Iteration 2 More Patterns.
Chapter 4 Accounting for Merchandising Businesses.
Chapters 10, 11 SSD (Revision) SD DCD Exam Object-Oriented Design.
Understanding Requirements
Elaboration Iteration 3 – Part 3 - Persistence Framework -
Larman chapter 101 Domain Model: Visualizing concepts Larman chapter 10.
Copyright © Craig Larman All Rights Reserved COMP-350 Object-Oriented Analysis and Design GRASP: Designing Objects with Responsibilities Reference:
Summary from previous lectures
Chapter 3: Case Studies What is and is not Covered in the Case Study?  Traditional business software applications include UI elements, core application.
(Further analysis and Refactoring) Larman, chapters 23 and 24 Glenn D. Blank, CSE432.
SYSTEM-LEVEL SEQUENCE DIAGRAMS Sys466. System-Level Sequence Diagrams  Use cases describe how external actors interact with the software system…  An.
OO Methodology Elaboration Iteration 3 – Part 3 - More Design Patterns -
Chapter 4 Accounting for Merchandising Businesses.
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
Elaboration popo.
BTS530: Major Project Planning and Design
GRASP : Designing Objects with Responsibilities
Tiers vs. Layers.
Chapter 23 Iteration 2.
Week 10 Iteration 3.
State Machine Diagrams
Week 5.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Week 5.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Other System Requirements
Presentation transcript:

Chapter 3 Case Studies

Example 1: Point of Sale (POS) Focus on core logic, not GUI. other layers are technology dependent core is similar across technologies skills learned are applicable everywhere design patterns of other layers not constant

Fig. 3.1

Iteration as a tool and environment Author notes that in Iteration 1 only certain techniques used so only these are introduced at this time In Iteration 2, we look at more UML tools, etc

Fig. 3.2

NextGen POS records sales and handles payments, returns, etc input devices: computers, barcode reader, fancy client terminals (Home Depot), PDA? external interfaces: tax calculator susceptible to communication failure like not access to credit card database individualized client logic (if you want to sell to many businesses)

Monopoly domain modeling, object design and patterns run as a simulation; very little “player” interaction