Sept 200491.3913 Ron McFadyen1 Today Sept 16: Chapters 1, 2, 3 Introductory material Next Tuesday Sept 21: Rational Rose and Use Cases Chapter 6 - Use.

Slides:



Advertisements
Similar presentations
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Advertisements

Ch 3: Unified Process CSCI 4320: Software Engineering.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Chapter 2 Approaches to System Development
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,
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Waterfall Development Process
Design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must.
September Ron McFadyen1 design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before.
Design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must.
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
Object Oriented Analysis and Design
NJIT Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman Presented By :Satish Khanna.
03/12/2001 © Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Object Oriented Analysis and Design Chapter 1 Applying UML and Patterns -Craig Larman.
03/12/2001 © Bennett, McRobb and Farmer Development Process Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
Jan 8, Ron McFadyen1 Waterfall Spiral UP Case study UML Use Cases.
Chapter 3 Case Studies.
Systems Analysis and Design in a Changing World, Fifth Edition
COMP 350: Object Oriented Analysis and Design Lecture 2
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
CIS 321—IS Analysis & Design
Chapter 2: Approaches to System Development
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
A Development Process Lecture Oo13 Objectory based method.
Chapter 18 Object Design Examples with GRASP. Objectives Design use case realizations –A use-case realization describes how a particular use case is realized.
Topic 1: Approaches to System Development
Sept Ron McFadyen1 UML & Design Patterns Course outlineoutline /3 Advanced Systems Design.
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Chapter 17 GRASP: Designing Objects with Responsibilities. 1CS6359 Fall 2011 John Cole.
Jan 7, A UP project organizes the work and iterations across four major phases: – Inception -- approximate vision, business case, scope, vague estimates.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
CSE 436—Software Development Models Ron K. Cytron 10 October 2005.
Object Oriented Analysis and Design Chapter 1 Applying UML and Patterns -Craig Larman.
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN Objectives Describe the book goals and scope Define OOA/D (Object-Oriented Analysis and Design) Illustrate.
The principles of an object oriented software development process Week 04 1.
The Systems Development Environment Systems Analysis and Design II.
© Bennett, McRobb and Farmer 2005
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN 1. WHAT IS AN INFORMATION SYSTEM? An information system is a collection of interrelated components that collect,
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
2 Systems Analysis – ITEC 3155 Systems Analysis Tasks.
Object Oriented Analysis & Design By Rashid Mahmood.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Introduction To System Analysis and Design
Software Development.
Object Design Examples with GRASP
Elaboration popo.
UNIT 1.
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Chapter 5: Object Oriented Analysis and Design
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN
System Development Process
COMP 350: Object Oriented Analysis and Design Lecture 2
Object Oriented Analysis and Design
Introduction To System Analysis and Design PART 2
Object Oriented Analysis and Design
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
CSCI 360: Software Architecture & Design
Presentation transcript:

Sept Ron McFadyen1 Today Sept 16: Chapters 1, 2, 3 Introductory material Next Tuesday Sept 21: Rational Rose and Use Cases Chapter 6 - Use Cases Followed by Chapters 9 and 25

Sept Ron McFadyen2 UML and patterns UML is a collection of techniques, a notation One case study throughout text NextGenPOS Text makes reference to the UP in order to set UML and the applications of patterns into a context UP is an iterative development methodology Iterative is very different from Waterfall Ch 1 OOA/D

Sept Ron McFadyen3 Ch 1 OOA/D OO analysis Emphasizes finding and describing the objects in the problem domain Example: playing a dice game One artifact is the Domain Model Player Die DiceGame plays rolls includes name faceValue

Sept Ron McFadyen4 Ch 1 OOA/D OO design Emphasizes defining software objects and how they collaborate to fulfill requirements To investigate and document the nature of how objects behave, we use interaction diagrams (and other techniques) die1:Die:DiceGamedie2:Die play() roll() getFaceValue()

Sept Ron McFadyen5 Ch 1 OOA/D OO design As we design, we assign responsibilities to classes and our domain model evolves to a design class diagram Player Die DiceGame plays rolls includes name faceValue play() roll() getFaceValue()

Sept Ron McFadyen6 Ch 1 OOA/D Unified Modeling Language (UML) Standard language for documenting OO systems Emerged due to efforts of Booch, Rumbaugh and Jacobson – the 3 amigos

Sept Ron McFadyen7 Ch 2 Iterative Development and the Unified Process (UP) Presented as an example process/methodology to give some structure/context to the presentation of the case study, UML, and patterns. Up is a from the Rational Corporation An iterative development process each iteration yields a working system iterations last anywhere from 2 weeks to 6 months many iterations make a project risk-driven early iterations prove out the major risks or show- stoppers

Sept Ron McFadyen8 Unified Process several activities deliverables are referred to as artifacts - works produced (use cases, code, database designs, …) Each iteration involves choosing some requirements and quickly designing, implementing and testing Relies on feedback. System converges towards the appropriate design 4 phases inception, elaboration, construction, transition Inception Use case model is started

Sept Ron McFadyen9 Figure 2.4 Illustrates the activities in UP used to develop a system Iterative development is central to the UP

Sept Ron McFadyen10 Figure 2.3 illustrates the 4 phases comprising the UP More requirements gatheringMore programming

Sept Ron McFadyen11 design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must revise earlier decisions based on experience in project - I.e. there is feedback Section 2.7

Sept Ron McFadyen12 design analysis implementation testing maintenance Waterfall Development Process Not iterative errors in earlier phases are really expensive to fix doesn’t allow for prototyping which is a strong aid for confirming requirements Section 2.7

Sept Ron McFadyen13 Ch 3 Case Study: the NextGen POS System Record sales Handle payments Retail store Interfaces to service applications Tax calc Inventory control Client – web browser Commercial application – sell to different clients

Sept Ron McFadyen14 NextGen POS Layered architecture

Sept Ron McFadyen15 Elaboratio n Iteration 1 Ch 9-20 Elaboratio n Iteration 1 Ch 9-20 Elaboratio n Iteration 2 Ch Elaboratio n Iteration 2 Ch Iteration 3 Elaboratio n Ch Iteration 3 Elaboratio n Ch Inception Ch 4-8 Inception Ch 4-8 The inception phase An initial step to investigate the prospective system, develop a vision, and make a decision to proceed or not We focus on the Use Case Model that is started in the Inception phase The elaboration phase Text uses 3 iterations to develop NextGenPOS Note that Java code is presented in Ch 20

Sept Ron McFadyen16 3C13 Lab can be used to work with Rational Rose Other tools you might use: Argo/UML, Poseidon, Visio, … Userid/password will be available Next week