COnstructive COst MOdel

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
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
LOC, COCOMO I & COCOMO II Subject: Software Engineering Coordinator: Mr Anoj Kumar Presented By: Kamal Kishore (2012ca34) Jyoti Shrivastava (2012ca52)
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)
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
Chapter 23 – Project planning Part 2. Estimation techniques  Organizations need to make software effort and cost estimates. There are two types of technique.
Information System Economics Software Project Cost Estimation.
© The McGraw-Hill Companies, Software Project Management 4th Edition Software effort estimation Chapter 5.
BRUE Behavioral Reverse Engineering in UML as Eclipse Plugin MSE Presentation 1 Sri Raguraman.
Cost22 1 Question of the day u If you were the boss, what would you do for cost estimation?
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.
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.
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.
CS /39 Illinois Institute of Technology CS487 Software Engineering David A. Lash.
A Brief Introduction to COCOMO Hossein Saiedian EECS810: Software Engineering.
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.
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
Student Curriculum Planning System MSE Project Presentation I Kevin Sung.
Cost Estimation. Problem Our ability to realistically plan and schedule projects depends on our ability to estimate project costs and development efforts.
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.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
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
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M18 - Version 9.01 SMU CSE 7315 Planning and Managing a Software Project.
©Ian Sommerville, adapted by Werner Wild 2004Project Management Slide 1 Software cost estimation u Predicting the resources required for a software development.
University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 Trends in Productivity and COCOMO Cost Drivers over the.
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.
EFFORT ESTIMATION RISK MANAGEMENT. Total time required by the project to get completed. The overall cost of the project.
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.
1. 2 Software Project Planning After the finalization of SRS, we would like to estimate size, effort cost and development time of the project. Also, in.
CSE SW Project Management / Module 18 - Introduction to Effort Estimating Models Copyright © , Dennis J. Frailey, All Rights Reserved CSE7315M18.
Project Estimation. Planning Prerequisites The planning process requires the following inputs: –Required human effort (man-months) –Project duration (months)
بشرا رجائی برآورد هزینه نرم افزار.
Project Cost Management
כ"ז/שבט/תשע"ח An Overview of Software Development Effort and Cost Estimation Techniques Professor Ron Kenett Tel Aviv University School of Engineering.
Software Engineering.
Software Estimating Technology: A Survey
COCOMO III Workshop Summary
Software Effort Estimation
Software Project Management
Software Cost Estimation
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
Software Planning
Constructive Cost Model
Software Engineering.
Chapter 26 Estimation for Software Projects
Software Systems Cost Estimation
COCOMO Model Basic.
Organization of SRS Functional Requirements: They describe what has to do and what the software should not do. They specify which outputs should be produced.
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.
Chapter 23 Software Cost Estimation
Software Cost Estimation
COCOMO MODEL.
Presentation transcript:

COnstructive COst MOdel COCOMO COnstructive COst MOdel

COCOMO The COstructive COst MOdel (COCOMO) is the most widely used software estimation model in the world. The COCOMO model predicts the effort and duration of a project based on inputs relating to the size of the resulting systems and a number of "cost drives" that affect productivity.

COCOMO As per Boehm, 1981 software development project can be classified into three categories based on development complexity: Organic (Applications -> data processing programs) A well-understood application program Semidetached (Utilities -> compiler, linkers etc) and Experienced and inexperienced staff Embedded (System programs -> OS, real-time system programs) Software, to be developed is strongly coupled with complex hardware To classify a project one need to know Characteristic of product, development team and development environment

Basic Model Basic COCOMO model takes the form where E is effort applied in Person-Months, and D is the development time in months. The coefficients ab, bb, cb and db are given in table on next slide.

When effort and development time are known, the average staff size to complete the project may be calculated as: When project size is known, the productivity level may be calculated as:

Example Suppose that a project was estimated to be 400 KLOC. Calculate the effort and development time for each of the three modes i.e., organic, semidetached and embedded.

Solution The basic COCOMO equation take the form: E = ab (KLOC)bb D = cb (E)db Estimated size of the project = 400 KLOC (i) Organic mode E = 2.4(400)1.05 = 1295.31 PM D = 2.5(1295.31)0.38 = 38.07 PM (ii) Semidetached mode E = 3.0(400)1.12 = 2462.79 PM D = 2.5(2462.79)0.35 = 38.45 PM (iii) Embedded mode E = 3.6(400)1.20 = 4772.81 PM D = 2.5(4772.8)0.32 = 38 PM

Exercise A project size of 200 KLOC is to be developed. Software development team has average experience on similar type of projects. The project schedule is not very tight. Calculate the effort, development time, average staff size and productivity of the project.

Solution The semi-detached mode is the most appropriate mode; keeping in view the size, schedule and experience of the development team. Hence, E = 3.0(200)1.12 = 1133.12 PM D = 2.5(1133.12)0.35 = 29.3 PM = 1133.12/29.3 = 38.67 persons

Productivity = KLOC/E = 200/1133.12 = 0.1768 KLOC/ PM P =176 LOC / PM

Intermediate Model According to COCOMO, the major productivity drivers include: Product attributes: required reliability, database size, product complexity Computer attributes: execution time constraints, storage constraints, virtual machine (VM) volatility, turnabout time Personnel attributes: analyst capability, application experience, VM experience, programming language experience Project attributes: modern programming practices, software tools, schedule constraints

Software Project Planning Multipliers of different cost drivers Cost Drivers RATINGS Very low Low Nominal High Very high Extra high Product Attributes RELY DATA CPLX Computer Attributes TIME STOR VIRT TURN 0.75 0.88 1.00 1.15 1.40 -- -- 0.94 1.00 1.08 1.16 -- 0.70 0.85 1.00 1.15 1.30 1.65 -- -- 1.00 1.11 1.30 1.66 -- -- 1.00 1.06 1.21 1.56 -- 0.87 1.00 1.15 1.30 -- -- 0.87 1.00 1.07 1.15 --

Software Project Planning Cost Drivers RATINGS Very low Low Nominal High Very high Extra high Personnel Attributes ACAP AEXP PCAP VMEXP LEXP Project Attributes MODP TOOL SCED 1.46 1.19 1.00 0.86 0.71 -- 1.29 1.13 1.00 0.91 0.82 -- 1.42 1.17 1.00 0.86 0.70 -- 1.21 1.10 1.00 0.90 -- -- 1.14 1.07 1.00 0.95 -- -- 1.24 1.10 1.00 0.91 0.82 -- 1.24 1.10 1.00 0.91 0.83 -- 1.23 1.08 1.00 1.04 1.10 -- Multiplier values for effort calculations

Intermediate COCOMO equations EAF: effort adjustment factor

Example A new project with estimated 400 KLOC embedded system has to be developed. Project manager has a choice of hiring from two pools of developers: Very highly capable (lot of application experience) with very little experience in the programming language being used Or Developers of low quality (very less application experience) but a lot of experience with the programming language. What is the impact of hiring all developers from one or the other pool ?

Solution This is the case of embedded mode and model is intermediate COCOMO. Hence, = 2.8(400)1.20 = 3712 PM Case I: Developers are very highly capable with very little experience in the programming being used. EAF = 0.82 x 1.14 = 0.9348 E = 3712 x .9348 = 3470 PM D = 2.5 (3470)0.32 = 33.9 M

Case II: Developers are of low quality but lot of experience with the programming language being used. EAF = 1.29 x 0.95 = 1.22 E = 3712 x 1.22 = 4528 PM D = 2.5 (4528)0.32 = 36.9 M