Software Estimating Technology: A Survey

Slides:



Advertisements
Similar presentations
A SEMINAR ON COCOMO Presentation by, Kongkon Mahanta MCA 4 th sem Roll no- 8.
Advertisements

Estimation using COCOMO More Science, Less Art. COCOMO History COCOMO History Constructive Cost Model Dr. Barry Boehm TRW in 1970s COCOMO
Early Effort Estimation of Business Data-processing Enhancements CS 689 November 30, 2000 By Kurt Detamore.
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
Software Cost Estimation Main issues:  What factors determine cost/effort?  How to relate effort to development time?
Project Risks and Feasibility Assessment Advanced Systems Analysis and Design.
Ch8: Management of Software Engineering. 1 Management of software engineering  Traditional engineering practice is to define a project around the product.
1 COST ESTIMATION Basics, COCOMO, FP. 2 What is estimated? TIME MONEY TIME: –duration, chronological weeks, months, years –effort, person-month (man-month)
CSC 395 – Software Engineering
Software Project Planning Infsy 570 Dr. R. Ocker.
Information System Economics Software Project Cost Estimation.
University of Toronto Department of Computer Science © 2001, Steve Easterbrook CSC444 Lec22 1 Lecture 22: Software Measurement Basics of software measurement.
Cost22 1 Question of the day u If you were the boss, what would you do for cost estimation?
ECE 355: Software Engineering
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Lecture 22 Instructor Paulo Alencar.
COCOMO Models Ognian Kabranov SEG3300 A&B W2004 R.L. Probert.
After Lesson 6 next is Lesson 13 to fit topic on Software Development SOFTWARE PROJECT MANAGEMENT.
Estimation Why estimate? What to estimate? When to estimate?
Dr. M. Shamim HossainSWE 211 Effort, Duration and Cost Lec 3 1.
Project Management Estimation. LOC and FP Estimation –Lines of code and function points were described as basic data from which productivity metrics can.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 23Slide 1 Chapter 23 Software Cost Estimation.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Effort estimation.
By K Gopal Reddy.  Metrics in software are of two types.direct and indirect.  Function points as indirect metrics.  Function points are used to measure.
A Brief Introduction to COCOMO Hossein Saiedian EECS810: Software Engineering.
1 Software Cost Estimation. Outline  Introduction  Inputs and Outputs  Methods of Estimation  COCOMO  Conclusion 2.
Group Members: Ayush Newatia, Barry Foye, Billy Felton, Kevin Anderson, Shahnaz Begum and Adam Jasinski Constructive Cost Model is a technique used to.
Quality Assurance vs. Quality Control Quality Assurance An overall management plan to guarantee the integrity of data (The “system”) Quality Control A.
Software cost estimation Predicting the resources required for a software development process 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.
T. E. Potok - University of Tennessee CS 594 Software Engineering Lecture 3 Dr. Thomas E. Potok
Cost Estimation. Problem Our ability to realistically plan and schedule projects depends on our ability to estimate project costs and development efforts.
Cost Estimation What is estimated? –resources (humans, components, tools) –cost (person-months) –schedule (months) Why? –Personnel allocation –Contract.
Project Estimation Model By Deepika Chaudhary. Factors for estimation Initial estimates may have to be made on the basis of a high level user requirements.
Software Project Planning Part II. Troutman's Postulates Profanity is the one language understood by all programmers. Not until a program has been in.
1 540f07cost10 Question of the Day u How important is it to be able to estimate the cost of a software project?
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.
SFWR ENG 3KO4 Slide 1 Management of Software Engineering Chapter 8: Fundamentals of Software Engineering C. Ghezzi, M. Jazayeri, D. Mandrioli.
Software Project Estimation IMRAN ASHRAF
Cost9a 1 Software Estimating Technology: A Survey Richard Stutzke Crosstalk, May96 text pp
Effort Estimation Has been an “art” for a long time because
©Ian Sommerville, adapted by Werner Wild 2004Project Management Slide 1 Software cost estimation u Predicting the resources required for a software development.
Estimation using COCOMO
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
Rating Very Very Extra Cost Drivers Low Low Nominal High High High Product Attributes Required software reliability Database size.
Cost12 1 Question of the Day u How important is it to be able to estimate the cost of a software project?
INFSY 570 DR. R. OCKER Software Project Planning.
بشرا رجائی برآورد هزینه نرم افزار.
Estimation Questions How do you estimate? What are you going to estimate? Where do you start?
Project Cost Management
כ"ז/שבט/תשע"ח An Overview of Software Development Effort and Cost Estimation Techniques Professor Ron Kenett Tel Aviv University School of Engineering.
Software Engineering.
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
Software Cost Estimation
Software Planning
Constructive Cost Model
Software Development & Project Management
Software Engineering.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION
COCOMO Model Basic.
Chapter 5: Software effort estimation- part 2
Activities During SPP Size Estimation
More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.
COCOMO Models.
COCOMO 2 COCOMO 81 was developed with the assumption that a waterfall process would be used and that all software would be developed from scratch. Since.
Software Cost Estimation
COnstructive COst MOdel
COCOMO MODEL.
Presentation transcript:

Software Estimating Technology: A Survey Richard Stutzke Crosstalk, May96 text pp204-215

Cost Estimation An estimate of the effort and duration, associated costs of equipment, travel and training and the rationale for the calculations

Problem “The estimator must estimate the effort (person-hours) and duration (calendar-day) for the project to enable managers to determine improtant business measures such as product costs, return on investment, and time to market.”

Recommendation If you are involved with cost estimation, I recommend the following book Tom DeMarco, Controlling Software Projects, Yourdon Press, NY c1982

Definition of Estimate (DeMarco) Default: "An estimate is the most optimistic prediction that has a non-zero probability of coming true" Proposed: "An estimate is a prediction that is equally likely to be above or below the actual result"

Estimates should not become goals DeMarco argues that the estimation and the management decision about pricing or goals should be separate.

Estimate

Parametric Cost Estimation LOC models Boehm's COCOMO Putnam's Model (SLIM) non-LOC models Function Points combination COCOMO2

Prediction Formulas b>1 E=aXb b<1

Boehm's COCOMO Software Engineering Economics – article (1983) pp216-233 in text Software Engineering Economics – (book) Prentice-Hall c1981 type COCOMO in a search engine - many www sites

COnstructive COst MOdel Basic macro - overview of whole project with one metric of KSLOC Intermediate multiplicative adjustment factors Detailed applying model to each phase

Modes of Software Development Organic detached, often batch Semidetached e.g. transaction processing Embedded e.g. os kernel

Programmer Effort Application Programs Utility Programs PM = 2.4 * (KDSI)1.05 Utility Programs PM = 3.0 * (KDSI)1.12 Systems Programs PM = 3.6 * (KDSI)1.20 Note A’s in text are different from later versions of COCOMO

Example for effort Size Appl Util Sys 5K 13.0 18.2 24.8

Development Time (Months) Application Programs TDEV = 2.5 * (PM) 0.38 Utility Programs TDEV = 2.5 * (PM) 0.35 Systems Programs TDEV = 2.5 * (PM) 0.32

Example for development time size appl util sys 5K 6.63 6.90 6.99 10K 8.74 9.06 9.12 15K 10.27 10.62 10.66 20K 11.52 11.88 11.90 25K 12.60 12.97 12.96 30K 13.55 13.93 13.91 35K 14.40 14.80 14.75 40K 15.19 15.59 15.53 45K 15.92 16.33 16.25 50K 16.61 17.02 16.92

Average Staffing Levels Calculate by dividing PM by TDEV

Example for staffing levels size appl util sys 5K 1.96 2.63 3.55 10K 3.08 4.37 6.26 15K 4.01 5.87 8.71 20K 4.84 7.23 11.02 25K 5.60 8.51 13.21 30K 6.30 9.72 15.33 35K 6.97 10.87 17.39 40K 7.60 11.98 19.39 45K 8.20 13.05 21.35 50K 8.79 14.09 23.27

COCOMO Effort Multipliers product attributes required reliability 0.75 - 1.40 data-base size 0.94 - 1.16 product complexity 0.70 - 1.65 computer attributes execution time constraint 1.00 - 1.66 main storage constraint 1.00 - 1.56 virtual machine volatility 0.87 - 1.30 computer turnaround time 0.87 - 1.15

The Cocomo 2.0 Software Cost Estimation Model Barry Boehm, etal See web pages