NJIT 1 Iteration 2 Requirements and More GRASP Chapter 24.

Slides:



Advertisements
Similar presentations
Object-Oriented Analysis and Design CHAPTERS 8, 9: BASICS, INTRO TO DOMAIN MODELS 1.
Advertisements

Object Design Examples with GRASP
Chapter 4: Inception is Not the Requirements Phase
Chapter 9 Domain Models The classic OOAD model. Fig. 9.1.
Object-Oriented Analysis and Design
Chapter 1 Object Oriented Analysis and Design. UML, Patterns, and Object-Oriented Analysis and Design  The essential skills for the creation of well-designed,
Object-Oriented Analysis and Design CHAPTERS 12-14: INTRODUCTION TO DESIGN 1.
1 The Business Modeling Discipline. 2 Purpose of Business Modeling  To understand the structure and dynamics of the organization in which a system is.
COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.
Drawing System Sequence Diagrams
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
Object Oriented Analysis and Design
NJIT Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman Presented By :Satish Khanna.
Understanding Requirements
Case Study The NextGen POS System
Domain model: visualizing concepts
NJIT 1 Domain Model Visualizing Concepts Chapter 9 Applying UML and Patterns Craig Larman.
NJIT Drawing System Sequence Diagrams Chapter 10 Applying UML and Patterns Craig Larman Presented by Anuradha Dharani.
Iterative development and The Unified process
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
Chapter 3 Case Studies.
COMP 350: Object Oriented Analysis and Design Lecture 2
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
NJIT Inception is not the Requirements Phase Chapter 4 Applying UML and Patterns Craig Larman.
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.
Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
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.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Chapter 7 Applying UML and Patterns Craig Larman
Jan 7, A UP project organizes the work and iterations across four major phases: – Inception -- approximate vision, business case, scope, vague estimates.
Chapter 9 Applying UML and Patterns -Craig Larman
SYS466: Analysis and Design Using OO Models Domain Class Diagram.
Chap 28 UML Activity Diagrams and Modeling
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
Larman ch. 131 Use-Case Model : Adding Detail with operation contracts Larman ch. 13.
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
Object-Oriented Analysis and Design CHAPTER 10: SYSTEM SEQUENCE DIAGRAMS 1.
COMP-350 Object-Oriented Analysis and Design Drawing System Sequence Diagrams Reference: Larman, Chapter 9.
DOMAIN MODEL: ADDING ATTRIBUTES Identify attributes in a domain model. Distinguish between correct and incorrect attributes.
The Rational Unified Process 1 EECS810: Software Engineering.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Chapter 4. Inception is NOT Requirements: Inception is a short, initial stage. Its purpose is a common vision and scope measurement. needed to do: –analyze.
Software Engineering 1 Object-oriented Analysis and Design Chap 24 Iteration 2 More Patterns.
Object-Oriented Analysis and Design CHAPTERS 9, 31: DOMAIN MODELS 1.
OO Methodology Elaboration Iteration 2 - Design Patterns -
TK2023 Object-Oriented Software Engineering CHAPTER 12 Introduction to Responsibility-Driven Design.
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN Objectives Describe the book goals and scope Define OOA/D (Object-Oriented Analysis and Design) Illustrate.
Software Design. A well-known phenomenon You will learn…. –Thinking "object oriented“ –Define requirements and analyze the problem domain. –Design of.
Week 2. Topics Inception phase Evolutionary requirements Use cases.
Inception is not Requirement phasee Chapter 3 and 4 Applying UML and Patterns -Craig Larman.
OO Methodology Elaboration Phase Iteration 1- Part 3.
Chapter 8: Iteration 1 - Basics.  We review here the requirements for first iteration of our case studies. They are a subset of the requirements as described.
(Further analysis and Refactoring) Larman, chapters 23 and 24 Glenn D. Blank, CSE432.
Chapter 8. Iteration 1, Elaboration: book view differs from reality for pedagogical reasons not doing “risk-driven” up front uses many OOA/D skills should.
PART II INCEPTION Chapter 4 Inception is Not The Requirements Phase.
Elaboration: Iteration 2. Elaboration: Iteration 2 Basics Iteration 1 ends with : All the software has been tested: The idea in the UP is to do early,
Elaboration popo.
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN
UNIFIED PROCESS.
Unified Process (UP).
Week 2.
OBJECT ORIENTED ANALYSIS AND DESIGN
Presentation transcript:

NJIT 1 Iteration 2 Requirements and More GRASP Chapter 24

2 Previous Key Concepts Covered The goal of the Inception phase is to do enough investigation to form a rational, justifiable opinion of the overall purpose and feasibility of a system. The goal of the Elaboration Iteration 1 phase was on the concepts of how to think in objects.

3 Elaboration Iteration 2 emphasis Essential object design The use of patterns to create a solid design Application of UML to visualize the models

4 Iteration 2 of the NextGen POS Systems Covers Support for variation is third-party services. E.g Tax Calculator for the POS Complex pricing rules Refresh GUI window when sale total changes

5 Focus on the RUP Goal Remembering the critical idea of RUP points to the fundamental concept of “Iterative Development”. This explains why Iteration 2 requirements are not newly discovered. They are simply an elaboration of the requirements identified during the inception stage.

6 Refinement of Analysis- oriented Artifacts Use-cases are revisited, investigated, and written in detail based on insights gain from Iteration 1. Use-case models (SSDs) are revisited and extended to support third-party systems (e.g in the case of the POS – a tax calculator) While it is reasonable skipping refining the domain model; this iteration gives the modeler insights as to what requirements have major or minor impact on the domain model parameters (i.e. attributes, associations ….)