Slide 1 Copyright QSM Associates, Inc. All Rights Reserved “Deadline Driven Estimation” “How much functionality can be built, within a deadline of X, with.

Slides:



Advertisements
Similar presentations
Project Estimation: Metrics and Measurement
Advertisements

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Slide 1 Copyright QSMAssociates, Inc. All Rights Reserved “Index Based Productivity Benchmarking” “How Productive Were Our Teams on Our Most Recent Projects?”
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
T. E. Potok - University of Tennessee CS 594 Software Engineering Lecture 2 Dr. Thomas E. Potok
© 2010 Pearson Education, Inc. All rights reserved.
© 2010 Pearson Education, Inc. All rights reserved.
© 2010 Pearson Education, Inc. All rights reserved.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
© 2010 Pearson Education, Inc. All rights reserved.
Some Visualization Principles from Edward Tufte. Edward Tufte, Beautiful Evidence See also
Information Processing The History Assignment. Assignment Brief Write a 1000-word report on one aspect of ‘The History of Computing’ This will be worth.
Copyright © 2006 Pearson Education, Inc. Publishing as Pearson Addison-Wesley.
Copyright QSM Associates, Inc. 1 Michael C. Mah Managing Partner QSM Associates, Inc. 75 South Church Street Pittsfield, MA Fax
© 2010 Pearson Education, Inc. All rights reserved.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
April 17, 2006Graphical Presentation of Information Graphical Presentation of Information IBM Mid-Peninsula PC Club Pat McMahon April 17, 2006.
CEN 4935 Senior Software Engineering Project Joe Voelmle.
9-0 Net Present Value and Other Investment Criteria Chapter 9 Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
University of Toronto Department of Computer Science © 2001, Steve Easterbrook CSC444 Lec22 1 Lecture 22: Software Measurement Basics of software measurement.
Copyright QSM Associates, Inc. All Rights Reserved 1 Michael C. Mah Managing Partner QSM Associates, Inc. 75 South Church Street Pittsfield, MA
Chapter 8 : Software Quality Assurance Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
COCOMO Models Ognian Kabranov SEG3300 A&B W2004 R.L. Probert.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Cost13 1 Cost Estimation Estimates based on LOC. cost13 2 Boehm's COCOMO u Software Engineering Economics u Prentice-Hall c1981 u type COCOMO in a search.
Chapter 1. Introduction.
Slide 6-1 Copyright © 2004 Pearson Education, Inc.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
SEG3300 A&B W2004R.L. Probert1 COCOMO Models Ognian Kabranov.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #2 Software Engineering.
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M16 - Version 8.01 SMU CSE 7315 Planning and Managing a Software Project.
Cost9a 1 Software Estimating Technology: A Survey Richard Stutzke Crosstalk, May96 text pp
1 Principles of Information Technology Introduction to Software and Information Systems Copyright © Texas Education Agency, All rights reserved.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
QSM Associates, Inc. 1 Michael C. Mah Managing Partner QSM Associates, Inc. 75 South Church Street Pittsfield, MA Fax
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M13 8/20/2001Slide 1 SMU CSE 8314 /
Copyright , Dennis J. Frailey CSE Software Measurement and Quality Engineering CSE8314 M00 - Version 7.09 SMU CSE 8314 Software Measurement.
Fundamentals of Visual Modeling with UML Module 1: Introduction to Object Technology.
Software Cost Estimation By Deepika Chaudhary. In project planning process a project is split into a number of activities which are performed in parallel.
Section 8.2 The Inverse Trigonometric Functions (Continued) Copyright © 2013 Pearson Education, Inc. All rights reserved.
Waves Copyright© 2015 EducAide Software Inc. All rights reserved.
1 Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5 LiGuo Huang Computer Science and Engineering Southern Methodist University.
Slide 1 Project Management Chapter 4. PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons,
Copyright © 2008 Vista Higher Learning. All rights reserved. 9.
Section 1.5 Circles Copyright © 2013 Pearson Education, Inc. All rights reserved.
Types of Hypotheses Research Hypothesis Statistical Hypotheses
Software Estimating Technology: A Survey
Software Metrics 1.
Software Quality Assurance (SQA)
Principles of Information Technology
Software Lifecycle Management Lecture
Software Project Sizing and Cost Estimation
Three-dimensional Mapping of the Initiation of Nonsustained Ventricular Tachycardia in the Human Heart by Mina K. Chung, Steven M. Pogwizd, Dave P. Miller,
"From Nuclear Submarines to Widgets: What QA and Test Defect Rates Are Saying." Michael Mah Managing Partner QSM Associates, Inc.
COCOMO Model Basic.
Familiar Metrics Management
Why Do We Measure? assess the status of an ongoing project
COCOMO Models.
Quadratic Equations, Inequalities, and Functions
Nonlinear Functions, Conic Sections, and Nonlinear Systems
Why Do We Measure? assess the status of an ongoing project
Genetics Practice Mr Kaneshiro
Number and Quantity Quick Check
Copyright © 2014, 2000, 1992 Elsevier Inc. All rights reserved.
Grade 3 Math Review Ms Nelson
Section 10.5 The Dot Product
FISSION &FUSION New User
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
COCOMO MODEL.
Presentation transcript:

Slide 1 Copyright QSM Associates, Inc. All Rights Reserved “Deadline Driven Estimation” “How much functionality can be built, within a deadline of X, with Y people, given proficiency Z?”

Slide 2 Copyright QSM Associates, Inc. All Rights Reserved Software Production Equation Conceptual Form = xx TIMEEFFORT PROCESS PRODUCTIVITY PRODUCT SIZE ESLOC Function Points Objects

Slide 3 Copyright QSM Associates, Inc. All Rights Reserved Step 1 - Identify Time and Budgeted Effort Time to June Deadline = 6 Months Budgeted Effort = 24 Person- Months

Slide 4 Copyright QSM Associates, Inc. All Rights Reserved Step 2 - Select Application Class and Productivity Index CategoryPI STD Dev v Business /- 4.1 v System Software /- 4.9 v Telecom /- 4.0 v Scientific /- 3.5 v Process Control /- 3.4 v Command & Ctrl /- 4.3 v Avionic 8.2 +/- 4.8 v Real-time 7.8 +/- 3.8 v Microcode 6.3 +/- 2.8

Slide 5 Copyright QSM Associates, Inc. All Rights Reserved PI PP Step 3 - Map PI Value to a Productivity Parameter PI PP

Slide 6 Copyright QSM Associates, Inc. All Rights Reserved Size B Very Low.16 Low.18 Med Low.28 Med High.34 High.37 Very High.39 Step 4 - Select “ B” (Integration Factor) Progressively Higher Values of B allow for Various Degrees of Software Integration Testing

Slide 7 Copyright QSM Associates, Inc. All Rights Reserved Step 5 - Calculate Size Selected PI = 17, Mapping to a Productivity Parameter = Effort = 24 Person-Months Time = 6 Months

Slide 8 Copyright QSM Associates, Inc. All Rights Reserved Step 5 - Calculate Size (con’t) SLOC = (35422) x (6 mos/12) 1.33 x ((24 pm/12)/.28).33 = (35422) x (.5) 1.33 x (7.14).33 = 27,074

Slide 9 Copyright QSM Associates, Inc. All Rights Reserved Step 6 - Map to Functional Size Units v Based on resultant size, translate that down to additional size units, such as number of programs, modules, function points, objects, etc. v For example, if size profiles of your projects reveal typical proportions of 200 source lines of C++ code per object, then loc would translate to about 135 objects. v Try (really hard now) NOT to promise more than 135 objects in the 6 month time frame!!

Slide 10 Copyright QSM Associates, Inc. All Rights Reserved Recommended Reading v Mah, Michael C., “High-Definition Software Measurement” © May 1999 Software Magazine  Mah, Michael C., and Putnam, Lawrence H., “Software by the Numbers: An Aerial View of the Software Metrics Landscape” © 1997 American Programmer.  Putnam, Lawrence H., and Myers, Ware, “Industrial Strength Software” © 1997 IEEE Computer Society.  Tufte, Edward, “Visual Explanations, Images and Quantities, Evidence and Narrative” © 1997 Graphics Press.