Chapter 4 Inception CS6359 -- John Cole.

Slides:



Advertisements
Similar presentations
FROM INCEPTION TO ELABORATION Use Cases, Domain Models & SSDs Oh My!
Advertisements

CS 221 Chapter 2 Excel. In Excel: A1 = 95 A2 = 95 A3 = 80 A4 = 0 =IF(A1
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Object-Oriented Analysis and Design LECTURE 2: INCEPTION PHASE.
Chapter 4: Inception is Not the Requirements Phase
Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.
COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
Systems Analysis and Design in a Changing World, Tuesday, Jan 30.
Dr. Kivanc DincerCS319 Week 1 - Sept.12,20051 Chapter 4 INCEPTION IS NOT THE REQUIREMENTS PHASE Objectives Define the inception step. Motivate the following.
171 Use Case Descriptions Chapter 4 – Facade Iteration Initial Requirements (Inception Phase)
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
NJIT Inception is not the Requirements Phase Chapter 4 Applying UML and Patterns Craig Larman.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
E-Store System for MEHE Final status report Team #2 Sandeep, Vijay, Jennifer, Ali, Meghna April 6 th, 2007.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
Inception Is there a project in there? What’s the vision, scope & business case?
Systems Analysis Lecture 2 Analysing the Business Case Feasibility Scope 1 BTEC HNC Systems Support Castle College 2007/8.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
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 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 3 Feasibility Studies.
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
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.
Inception is not Requirement phasee Chapter 3 and 4 Applying UML and Patterns -Craig Larman.
Rational Unified Process (RUP)
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.
1 Systems Analysis & Design 7 th Edition Chapter 2.
Overview of the Web Development Process.  Website Strategic Plan (Planning)  Content and Site Architecture (Planning)  Website Strawman (Planning)
Larman chapter 41 Inception Larman chapter 4 and 7.
The Unified Process and the Inception Phase James W. Benham CMPT 371 Fall 2004.
PART II INCEPTION Chapter 4 Inception is Not The Requirements Phase.
Quiz 1 Q1) Discuss briefly the main phases of the requirement process. Q2)Discuss briefly the main outcome of the Trawling for Requirements phase.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
TK2023 Object-Oriented Software Engineering
Chapter 33 Estimation for Software Projects
Chapter Five Project Planning.
SE503 Advanced Project Management
SA Capstone Requirements and Design Week 2 SYST36367 Winter 2017
Applying UML and Patterns
CHAPTER ‘3’ Project Blastoff
Chapter 2: The Project Management and Information Technology Context
Unified Process(UP) popo.
Unified Process (UP).
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Requirements and the Software Lifecycle
COMP 350: Object Oriented Analysis and Design Lecture 2
Week 2.
Requirements Analysis
Chapter 2 Managing Spending
Requirements Engineering Bsc Applied Computing Year 2
Evolutionary Requirements
OO Design and Development
SA Capstone Requirements and Design Week 2 SYST36367 Winter 2018
Chapter 33 Estimation for Software Projects
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
AD642 Project Communication: Intro
Chapter 26 Estimation for Software Projects.
CPDM.IISc TeamName TeamMember1, TeamMember2, TeamMember3, Domain Expert*
Other System Requirements
Presentation transcript:

Chapter 4 Inception CS6359 -- John Cole

Purpose of Inception Establish a common vision and basic scope of the project Creation of a business case Creation of a development environment CS6359 -- John Cole

Questions Is it feasible? Buy or build? Rough range of cost CS6359 -- John Cole

What it isn’t Defining precise requirements Getting good estimates CS6359 -- John Cole

In one sentence… Envision the project scope, vision, and business case Do the stakeholders have basic agreement on the project and is it worth further investigation? CS6359 -- John Cole

How long does it take? Can be as short as a day or two, as long as a few weeks CS6359 -- John Cole

What gets defined? Business case Some of the use cases Other (usually non-functional) requirements Key domain terminology List of risks (business, resource, technical, schedule) and risk management plan Prototypes Iteration plan Phase plan Development case CS6359 -- John Cole

You didn’t get it when… It takes more than a few weeks You attempt to define most of the requirements Estimates are expected to be reliable You define the architecture There is no business case or vision All of the use cases were written No use cases were written CS6359 -- John Cole