Presentation is loading. Please wait.

Presentation is loading. Please wait.

Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.1 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress : Gantt Chart Activities shown.

Published byJoella Quinn Modified over 9 years ago

Similar presentations

Presentation on theme: "Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.1 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress : Gantt Chart Activities shown."— Presentation transcript:

1 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.1 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress : Gantt Chart Activities shown in parallel

2 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.2 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress Phases, Steps, and Activities in Building a House

3 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.3 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Estimation Should be Done Repeatedly Uncertainty affects the accuracy of cost and size estimations

4 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.4 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Watson and Felix Model Productivity Factors

5 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.5 © 2006 Pearson/Prentice Hall Three Stages of COCOMO II

6 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.6 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation COCOMO II: Estimate Application Points To compute application points count the number of screens, reports, and programming language used, and determine the complexity level 8 +mediumdifficult 4 +mediumdifficult

7 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.7 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Complexity Weights for Application Points Object typeSimpleMediumDifficult Screen 123 Report 258 3GL component -- 10

8 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.8 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation Productivity Estimate Calculation

9 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.9 © 2006 Pearson/Prentice Hall 3.3 Effort Estimation - Evaluating Models No model captures cost for all types of development PRED(25%) within 25% of actual cost MMRE - mean magnitude of relative error (small is good)

10 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.10 © 2006 Pearson/Prentice Hall Risk

11 Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.11 © 2006 Pearson/Prentice Hall 3.4 Risk Management Risk Management Activities (continued) Example of risk exposure calculation

Download ppt "Pfleeger and Atlee, Software Engineering: Theory and PracticePage 3.1 © 2006 Pearson/Prentice Hall 3.1 Tracking Progress : Gantt Chart Activities shown."

Similar presentations

ISBN 0-13-146913-4 Prentice-Hall, 2006 Chapter 2 Modeling the Process and Life Cycle Copyright 2006 Pearson/Prentice Hall. All rights reserved.

ISBN Prentice-Hall, 2006 Chapter 2 Modeling the Process and Life Cycle Copyright 2006 Pearson/Prentice Hall. All rights reserved.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.

CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Estimation using COCOMO More Science, Less Art. COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s 1981 - COCOMO81 1996.

Estimation using COCOMO More Science, Less Art. COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s COCOMO
ISBN 0-13-146913-4 Prentice-Hall, 2006 Chapter 3 Planning and Managing the Project Copyright 2006 Pearson/Prentice Hall. All rights reserved.

ISBN Prentice-Hall, 2006 Chapter 3 Planning and Managing the Project Copyright 2006 Pearson/Prentice Hall. All rights reserved.
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.

Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.

Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.
1 Calibrating Function Points Using Neuro-Fuzzy Technique Vivian Xia NFA Estimation Inc. London, Ontario, Canada Danny Ho IT Department.

1 Calibrating Function Points Using Neuro-Fuzzy Technique Vivian Xia NFA Estimation Inc. London, Ontario, Canada Danny Ho IT Department.
Lecturer: Dr. AJ Bieszczad Chapter 33-1 Planning and managing the project Tracking project progress Project personnel and organization Effort and schedule.

Lecturer: Dr. AJ Bieszczad Chapter 33-1 Planning and managing the project Tracking project progress Project personnel and organization Effort and schedule.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.

SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
Chapter 3 Planning and Managing the Project Shari L. Pfleeger Joanne M. Atlee 4th Edition.

Chapter 3 Planning and Managing the Project Shari L. Pfleeger Joanne M. Atlee 4th Edition.
Computer Engineering 203 R Smith Project Scheduling 12/2007 1 Scheduling Now we know how much work there is to do, when can it be done? What kind of schedule.

Computer Engineering 203 R Smith Project Scheduling 12/ Scheduling Now we know how much work there is to do, when can it be done? What kind of schedule.
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.

Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Project Management Software Tools Cheryl A. Wilhelmsen Lee Ostrom.

Project Management Software Tools Cheryl A. Wilhelmsen Lee Ostrom.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.

Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
University of Toronto Department of Computer Science © 2001, Steve Easterbrook CSC444 Lec22 1 Lecture 22: Software Measurement Basics of software measurement.

University of Toronto Department of Computer Science © 2001, Steve Easterbrook CSC444 Lec22 1 Lecture 22: Software Measurement Basics of software measurement.
© The McGraw-Hill Companies, 2005 1 Software Project Management 4th Edition Software effort estimation Chapter 5.

© The McGraw-Hill Companies, Software Project Management 4th Edition Software effort estimation Chapter 5.
Chapter 3 Planning and Managing the Project. Pfleeger and Atlee, Software Engineering: Theory and PracticeChapter 3.2 Important Dates 09/09/2010 HW: Page.

Chapter 3 Planning and Managing the Project. Pfleeger and Atlee, Software Engineering: Theory and PracticeChapter 3.2 Important Dates 09/09/2010 HW: Page.
ISBN 0-13-146913-4 Prentice-Hall, 2006 Chapter 10 Delivering the System Copyright 2006 Pearson/Prentice Hall. All rights reserved.

ISBN Prentice-Hall, 2006 Chapter 10 Delivering the System Copyright 2006 Pearson/Prentice Hall. All rights reserved.
Four P’s People – software engineers People – software engineers Product – software to be produced Product – software to be produced Process – framework.

Four P’s People – software engineers People – software engineers Product – software to be produced Product – software to be produced Process – framework.
Schedule & effort.

Schedule & effort.

Similar presentations

Ads by Google