Iterative Process Planning

Slides:



Advertisements
Similar presentations
Chapter 7: Software production process Refers to the activities that are used for building, delivering, deploying, and evolving a software product, from.
Advertisements

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Arlow and Neustadt ch.21 What is the unified process? People are more important than any process. Good people with a good process will outperform good.
Last Class Meeting Final Examination.
Learning software process with UPEDU Slide 9-1  2000 École Polytechnique de Montréal & Rational Software Project Management - Outline  Defining the Project.
INTRODUCTION Successful software projects require Careful planning
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
SYSC System Analysis and Design
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Chapter 5: Project Scope Management
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Iterative development and The Unified process
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
The project structure (WBS) 24-March Recap Software Development Planning 2.
Chapter 6 View Alignment Techniques and Method Customization (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis.
Chapter 6– Artifacts of the process
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Sixteenth Meeting 6:30 – 9:20 pm, Thursday, September 20, 2001 Review - Looking Forward (from Part IV, Chapter 15 of Royce’ book) Final Examination.
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
RUP Fundamentals - Instructor Notes
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
Fifteenth Lecture Hour 10:30 – 11:20 am, Sunday, September 16 Tailoring the Process (from Chapter 14 of Royce’ book)
HANDLED BY Ms.k.CHITHARTHANI L/IT. Aim: To present the concept regarding how the sotware projects are planned, monitored and controlled. Objective: 
CLEANROOM SOFTWARE ENGINEERING.
Twelfth Lecture Hour 10:30 – 11:20 am, Saturday, September 15 Software Management Disciplines Project Organization and Responsibilities (from Part III,
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Relating Testing to Quality –Timeliness of Testing –Quality Attributes Gauge by Testing –Roles Defining Test Discipline Activities Elaborating the Test.
Fourteenth Lecture Hour 9:30 – 10:20 am, Sunday, September 16 Software Management Disciplines Project Control and Process Automation (from Part III, Chapter.
Information Technology Project Management
Work Breakdown Structure (WBS) The WBS represents a logical decomposition of the work to be performed and focuses on how the product, service, or result.
Chapter – 9 Checkpoints of the process
Iterative process planning. Overview Introductory Remarks 10.1 Work breakdown structure 10.2 Planning Guidelines 10.3 The cost & Schedule estimating process.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Estimating Project Times and Costs Chapter 5.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Chapter 4 프로세스 모델 Process Models
Effort Estimation ( 估计 ) And Scheduling ( 时序安排 ) Presented by Basker George.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Chapter 8 Workflows of the Process Taken from Walker Royce’s textbook – Software Project Management plus a number of Personal Comments.
The Rational Unified Process 1 EECS810: Software Engineering.
Estimating Project Times and Costs CHAPTER FIVE Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Project Task Planning 1 Concepts and Definitions Work Breakdown Structures.
Project Scope Management 1. 2 Learning Objectives Understand the elements that make good project scope management important. Explain the scope planning.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
ITERATIVE PROCESS PLANNING Summary Projects can under plan and they can over plan. Once again, balance is paramount in the level of planning detail and.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Architecture Architecture represents different things from use cases –Use cases deal primarily with functional properties –Architecture deals.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
TK2023 Object-Oriented Software Engineering
Work Breakdown Structure (WBS)
Work Breakdown Structure (WBS)
UNIFIED PROCESS.
UML: Unified modeling language
Presentation transcript:

Iterative Process Planning Software Management (from Part III, Chapter 10 of Royce’ book)

Topic for Today Iterative Process Planning Work Breakdown Structures (WBS) Planning Guidelines The Cost and Schedule Estimating Process The Iterative Planning Process

Conventional breakdown structures Conventional work breakdown structures are project-specific, and cross-project comparisons are usually difficult or impossible. Most organizations allow individual projects to define their own project-specific structure tailored to the project manager’s style, the customer’s demands, or other project-specific preferences. With no standard WBS structure, it is extremely difficult to compare plans, financial data, schedule data, organizational efficiencies, cost trends, productivity trends, or quality trends across multiple projects. Each project organizes the work differently and uses differ- ent units of measure

Recommended WBS First Level Second Level Third Level Workflows for WBS elements. Can be allocated to single teams. Second Level Defined for each phase of the life cycle. Third Level Focus on the activities that produce the artifacts of each phase.

Work Breakdown Structure

WBS (cont’d)

WBS Budgeting

Effort and Schedule By Phase

Iterations Inception stage Elaboration stage Construction stage Prototypes, critical use cases, existing components, custom component prototypes. Elaboration stage Architecture, initialization, scenarios, peak load conditions, worst case control flow, fault tolerance. Construction stage Alpha and beta releases, execution of all critical cases, 95% of capabilities demonstrated. Transition stage Resolve all defects, incorporate beta feedback, incorporate performance improvements.

Evolution of Planning

Cost and Schedule Estimating Steps – Top Down 1. Software project manager characterizes overall size, process, environment, people and quality. 2. Software manager makes a macro-level estimate of effort and schedule using software cost estimation model. 3. Software manager partitions the effort in top-level WBS. 4. Subproject managers decompose each WBS element into lower levels.

Cost and Schedule Estimating Steps – Bottom Up Lower level WBS elements are elaborating into detailed tasks by responsible WBS element managers. Estimates are combined and integrated into higher level WBS elements. Comparisons are made with the top down budgets and schedule milestones. Large differences are reconciled to converge on agreements.

Planning Balance Across Life Cycle

Assignment for Next Class Meeting Read Chapter 10 of Royce’ book, on iterative process planning. Learn and discuss the similarities and the differences of top-level organization of a conventional WBS and the top-level organization of a modern WBS. Learn and discuss the similarities and the differences between the four steps for a top-down cost and schedule estimate and the three steps for a bottom-up cost and schedule estimate. Learn and discuss the similarities and the differences of the contents of the iterations in each of the four development phases.