3 1 Tracking Progress Gantt Chart Activities shown

  • Slides: 11
Download presentation
3. 1 Tracking Progress: Gantt Chart • Activities shown in parallel Pfleeger and Atlee,

3. 1 Tracking Progress: Gantt Chart • Activities shown in parallel Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 1

3. 1 Tracking Progress Phases, Steps, and Activities in Building a House Pfleeger and

3. 1 Tracking Progress Phases, Steps, and Activities in Building a House Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 2

3. 3 Effort Estimation Should be Done Repeatedly • Uncertainty affects the accuracy of

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

3. 3 Effort Estimation Watson and Felix Model Productivity Factors Pfleeger and Atlee, Software

3. 3 Effort Estimation Watson and Felix Model Productivity Factors Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 4

Three Stages of COCOMO II Pfleeger and Atlee, Software Engineering: Theory and Practice ©

Three Stages of COCOMO II Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 5

3. 3 Effort Estimation COCOMO II: Estimate Application Points • To compute application points

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 For Screens For Reports Number and source of data tables Number of Total < 4 Total < 8 Total 8+ views (<2 (2 -3 (>3 sections (<2 (2 -3 (>3 contained server, >5 contained server, 3 - server, <3 3 -5 client) <3 5 client) >5 client) <3 simple medium 0 or 1 simple medium 3 -7 simple medium difficult 2 or 3 simple medium difficult 4+ medium 8+ medium difficult client) difficult Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall client) difficult Page 3. 6

3. 3 Effort Estimation Complexity Weights for Application Points Object type Simple Medium Screen

3. 3 Effort Estimation Complexity Weights for Application Points Object type Simple Medium Screen 1 2 3 Report 2 5 8 3 GL component - - 10 Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Difficult Page 3. 7

3. 3 Effort Estimation Productivity Estimate Calculation Pfleeger and Atlee, Software Engineering: Theory and

3. 3 Effort Estimation Productivity Estimate Calculation Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 8

3. 3 Effort Estimation - Evaluating Models • No model captures cost for all

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) Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 9

Risk Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page

Risk Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 10

3. 4 Risk Management Activities (continued) • Example of risk exposure calculation Pfleeger and

3. 4 Risk Management Activities (continued) • Example of risk exposure calculation Pfleeger and Atlee, Software Engineering: Theory and Practice © 2006 Pearson/Prentice Hall Page 3. 11