Inception is not Requirement phasee Chapter 3 and 4 Applying UML and Patterns -Craig Larman.

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Chapter 4: Inception is Not the Requirements Phase
Object-Oriented Analysis and Design
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Rational Unified Process
COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
NJIT 1 Iteration 2 Requirements and More GRASP Chapter 24.
Slide 9.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
Dr. Kivanc DincerCS319 Week 1 - Sept.12,20051 Chapter 4 INCEPTION IS NOT THE REQUIREMENTS PHASE Objectives Define the inception step. Motivate the following.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Iterative development and The Unified process
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
COMP 350: Object Oriented Analysis and Design Lecture 2
NJIT Inception is not the Requirements Phase Chapter 4 Applying UML and Patterns Craig Larman.
The web application development process Basharat Mahmood, COMSATS Institute of Information Technology, Islamabad, Pakistan. 1.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
IS0514 Lecture - Week 2 Best Practice Development Methodology.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
The Rational Unified Process
Rational Unified Process (Part 1) CS3300 Fall 2015.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Chapter 1 , 2 , 3 and 4 Applying UML and Patterns -Craig Larman
Software Engineering Management Lecture 1 The Software Process.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
Chapter 7 Applying UML and Patterns -Craig Larman
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.
IMAT1906 Systems Development Lecture week 6: systems analysis (1) : feasibility.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
Miguel Garzón, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5 Leffingwell.
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,
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
CS 5150 Software Engineering Lecture 7 Requirements 1.
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.
Week 2. Topics Inception phase Evolutionary requirements Use cases.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Rational Unified Process (RUP)
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach
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.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
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.
Larman chapter 41 Inception Larman chapter 4 and 7.
The Unified Process and the Inception Phase James W. Benham CMPT 371 Fall 2004.
The B uff. The Buffs Outline 1. Summary of last presentation 2. Current iteration and Progress 3. Plan for next iteration.
PART II INCEPTION Chapter 4 Inception is Not The Requirements Phase.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
TK2023 Object-Oriented Software Engineering
C. What is a Feasibility report
Applying UML and Patterns
The Web Application Development Process Models
UNIFIED PROCESS.
Unified Process (UP).
COMP 350: Object Oriented Analysis and Design Lecture 2
Object Oriented Analysis and Design
Week 2.
Chapter 2 – Software Processes
Chapter 4 Inception CS John Cole.
Feasibility Report.
Presentation transcript:

Inception is not Requirement phasee Chapter 3 and 4 Applying UML and Patterns -Craig Larman

Management Environment Business Modeling Implementation Test Analysis & Design Preliminary Iteration(s) Iter. #1 Phases Process Workflows Do you remember this ? Supporting Workflows Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Deployment Configuration Mgmt Requirements ElaborationTransitionInceptionConstruction time

What needs to be done? Describe the initial common vision and business case for this project. Exhibiting at least one candidate architecture based on experience gained from similar systems or in similar problem domains Determine if the project is feasible Determine if the organization should build or buy the necessary system Make a rough estimate of the cost and time. Determine if we should go ahead with the project or stop Inception : Initial short step in the process

Example Questions in Inception Ask questions such as: What is the vision and business case for this project? Feasible? Buy and/or build? Buy components and glue them together or from scratch? Estimate potential risks Rough estimate of cost: Is it $10K-100K or in the millions? Should we proceed or stop? If the answer isYES …..

Feasible ? Legal feasibility No conflicts with legal requirements, e.g. a data processing system must comply with the local Data Protection Acts.. Schedule feasibility Schedule feasibility is a measure of how reasonable the project timetable is. Given our technical expertise, are the project deadlines reasonable? Cultural feasibility Impact on the local and general culture Resource feasibility

So what is the purpose of Inception ? Do just enough investigation to be able to present a rational business case to show purpose, feasibility and need for the proposed software. Plans and estimates created during the inception phase are not to be considered as reliable Decide whether it is worth to make serious investigation (during elaboration ) further or stop right now?

7 How Long Should the Inception Phase be? Short. It may even be shorter (less than a week) if the project is commissioned by a client: “ I want this game based on this film that will come out in 2 years time; here is the film storyboard, costumes design, target market analysis... and it must have the same puzzles as the latest Harry Potter game ”. Sometimes business negotiations will take much longer however …

How Long Should the Inception Phase be?

9 What Artifacts (documents or model) may start in Inception? Vision and Business Case: describes the high-level goals and constraints, provides an executive summary; Use Case Model ( next chap ): describes the fundamental requirements: during inception identify the names of the use cases and analyse perhaps 10% of the them; Supplementary specification: describe non- functional requirements, look-and-feel, atmosphere etc.

What artifacts (documents or model) may start in Inception? Glossary: keeping track to key terms; Risk list and risk management plan: describe the risks (business, technical, resource, schedule) and ideas for their mitigation; Prototypes and proof-of-concepts: to clarify the vision, and validate technical ideas; Iteration Plan: Describes what to do in the first elaboration iteration, and overall goals of the elaboration phase; IMPORTANT : Artifacts will be partial at this stage. Will be refined in later iterations.

11 You Know you did not Understand Inception when: It is more than a few weeks long; There is an attempt to define most of the requirements; Plans and estimates are expected to be reliable; There is no business case or vision artefact; All the use case were written in detail.

Remember The inception phase is not very technical, it is really about deciding if it is worthwhile to invest in deeper exploration (the purpose of the elaboration phase); Not going any further is not a negative outcome (droping the project during elaboration is not a mistake of inception)

Questions ?