COCOMO: Difference between revisions
imported>Newtbytes Undid revision 1280731719 by 99.242.75.55 (talk) |
imported>Mudcap |
||
| Line 3: | Line 3: | ||
{{refimprove|date=October 2015}} | {{refimprove|date=October 2015}} | ||
The '''Constructive Cost Model''' ('''COCOMO''') is a | The '''Constructive Cost Model''' ('''COCOMO''') is a parametric [[Estimation in software engineering|software cost estimation model]] developed by [[Barry Boehm|Barry W. Boehm]]. The model parameters are derived from fitting a [[Regression analysis|regression]] formula using data from historical projects (63 projects for COCOMO 81 and 161 projects for COCOMO II). | ||
== History == | == History == | ||
| Line 26: | Line 26: | ||
|isbn = 0-13-822122-7}}</ref> as a model for estimating effort, cost, and schedule for software projects. It drew on a study of 63 projects at [[TRW Inc.|TRW]] Aerospace where Boehm was Director of Software Research and Technology. The study examined projects ranging in size from 2,000 to 100,000 [[lines of code]], and programming languages ranging from [[assembly language|assembly]] to [[PL/I]]. These projects were based on the [[waterfall model]] of software development which was the prevalent software development process in 1981. | |isbn = 0-13-822122-7}}</ref> as a model for estimating effort, cost, and schedule for software projects. It drew on a study of 63 projects at [[TRW Inc.|TRW]] Aerospace where Boehm was Director of Software Research and Technology. The study examined projects ranging in size from 2,000 to 100,000 [[lines of code]], and programming languages ranging from [[assembly language|assembly]] to [[PL/I]]. These projects were based on the [[waterfall model]] of software development which was the prevalent software development process in 1981. | ||
References to this model typically call it ''COCOMO 81''. In 1995 ''COCOMO II'' was developed and finally published in 2000 in the book ''Software Cost Estimation with COCOMO II''.<ref name="cocomo2">[[Barry Boehm]], Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz, Ray Madachy, Donald J. Reifer, and Bert Steece. ''[[Software Cost Estimation with COCOMO II (book)|Software Cost Estimation with COCOMO II]]'' (with CD-ROM). Englewood Cliffs, NJ:Prentice-Hall, 2000. {{ISBN|0-13-026692-2}}</ref> COCOMO II is the successor of COCOMO 81 and is claimed to be better suited for estimating modern software development projects; providing support for more recent [[software development process]]es and was tuned using a larger database of 161 projects. The need for the new model came as software development technology moved from mainframe and overnight batch processing to desktop development, code reusability, and the use of off-the-shelf software components. | References to this model typically call it ''COCOMO 81''. In 1995 ''COCOMO II'' was developed and finally published in 2000 in the book ''Software Cost Estimation with COCOMO II''.<ref name="cocomo2">[[Barry Boehm]], Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz, [[Raymond_Madachy|Ray Madachy]], Donald J. Reifer, and Bert Steece. ''[[Software Cost Estimation with COCOMO II (book)|Software Cost Estimation with COCOMO II]]'' (with CD-ROM). Englewood Cliffs, NJ:Prentice-Hall, 2000. {{ISBN|0-13-026692-2}}</ref> COCOMO II is the successor of COCOMO 81 and is claimed to be better suited for estimating modern software development projects; providing support for more recent [[software development process]]es and was tuned using a larger database of 161 projects. The need for the new model came as software development technology moved from mainframe and overnight batch processing to desktop development, code reusability, and the use of off-the-shelf software components. | ||
COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. The first level, ''Basic COCOMO'' is good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to its lack of factors to account for difference in project attributes (''Cost Drivers''). ''Intermediate COCOMO'' takes these Cost Drivers into account and ''Detailed COCOMO'' additionally accounts for the influence of individual project phases. | COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. The first level, ''Basic COCOMO'' is good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to its lack of factors to account for difference in project attributes (''Cost Drivers''). ''Intermediate COCOMO'' takes these Cost Drivers into account and ''Detailed COCOMO'' additionally accounts for the influence of individual project phases. | ||
Last one is Complete COCOMO model which addresses the shortcomings of both basic & intermediate. | Last one is Complete COCOMO model which addresses the shortcomings of both basic & intermediate. | ||
== Intermediate | == Tools == | ||
''Intermediate COCOMO'' computes software development effort as function of program size and a set of "cost drivers" that include subjective assessment of product, hardware, personnel and project attributes. This extension considers a set of four "cost drivers", each with a number of subsidiary attributes: | |||
An online [https://softwarecost.org/tools/COCOMO COCOMO II tool] implementation of the model is available for software cost estimation.<ref>Ray Madachy. [https://softwarecost.org/tools/COCOMO COCOMO II Tool]. softwarecost.org. Accessed October 2025.</ref> It is developed by [[Raymond Madachy|Ray Madachy]], a co-author of COCOMO II, and conforms to the book definition for the post-architecture model. An example estimate from the tool is shown below. | |||
[[File:COCOMO Tool Example.png|thumb|center|500px|Example software cost estimate from COCOMO II tool.]] | |||
== Intermediate COCOMO == | |||
''Intermediate COCOMO'' computes software development effort as function of program size and a set of "cost drivers" that include subjective assessment of product, hardware, personnel and project attributes. This extension considers a set of four "cost drivers", each with a number of subsidiary attributes: | |||
* Product attributes | * Product attributes | ||
| Line 198: | Line 204: | ||
The Intermediate Cocomo formula now takes the form: | The Intermediate Cocomo formula now takes the form: | ||
:{{math|1=''E'' = {{abbr|''a'' | :{{math|1=''E'' = {{abbr|''a''|coefficient}}(KSLOC){{sup|{{abbr|''b''|exponent}}}}(EAF)}} | ||
where ''E'' is the effort applied in person-months, ''' | where ''E'' is the effort applied in person-months, '''KSLOC''' is the estimated number of thousands of source lines of code delivered for the project, and '''EAF''' is the factor calculated above. The coefficient ''a'' and the exponent ''b'' are given in the next table for different project types. | ||
:{| class="wikitable" | :{| class="wikitable" | ||
!Software project | !Software project | ||
!width="20%"|a | !width="20%"|a | ||
!width="20%"|b | !width="20%"|b | ||
!width="20%"|c | !width="20%"|c | ||
|- | |- | ||
! Organic | ! Organic | ||
| Line 226: | Line 232: | ||
The Development time ''D'' and also the most effective number of Persons ''P'' calculation uses ''E'' in the same way as in the Basic COCOMO: | The Development time ''D'' and also the most effective number of Persons ''P'' calculation uses ''E'' in the same way as in the Basic COCOMO: | ||
:{{math|1=''D'' = 2.5 ''E''{{sup|''c'' | :{{math|1=''D'' = 2.5 ''E''{{sup|''c''}}}} | ||
:{{tmath|1=P = E/D}} | :{{tmath|1=P = E/D}} | ||
Note that in addition to the EAF, the parameter ''a | Note that in addition to the EAF, the parameter ''a'' is different in ''Intermediate COCOMO'' from the Basic model: | ||
:{| class="wikitable" | :{| class="wikitable" | ||
!Software project | !Software project | ||
!width="20%"|''a | !width="20%"|''a'' | ||
|- | |- | ||
! Organic | ! Organic | ||
| Line 275: | Line 281: | ||
| issue=5 | | issue=5 | ||
| pages=416–42 | | pages=416–42 | ||
| url = | | url = https://www.pitt.edu/~ckemerer/CK%20research%20papers/EmpiricalValidationSwCost_Kemerer87.pdf | ||
| doi=10.1145/22899.22906}} | | doi=10.1145/22899.22906}} | ||
| Line 281: | Line 287: | ||
<!-- Do not add links to commercial products here - it will be deleted as SPAM --> | <!-- Do not add links to commercial products here - it will be deleted as SPAM --> | ||
* [https://web.archive.org/web/20170902182304/http://openscience.us/repo/effort/cocomo/coc81.html COCOMO 81 data] on tera-PROMISE | * [https://web.archive.org/web/20170902182304/http://openscience.us/repo/effort/cocomo/coc81.html COCOMO 81 data] on tera-PROMISE | ||
* [ | * [https://shape-of-code.coding-guidelines.com/2016/05/19/cocomo-how-not-to-fit-a-model-to-data/ Analysis of the COCOMO 81 data] obtains a different value for the Organic exponent. | ||
<br> | <br> | ||
Latest revision as of 00:03, 1 November 2025
Template:Short description Script error: No such module "Distinguish". Template:Refimprove
The Constructive Cost Model (COCOMO) is a parametric software cost estimation model developed by Barry W. Boehm. The model parameters are derived from fitting a regression formula using data from historical projects (63 projects for COCOMO 81 and 161 projects for COCOMO II).
History
The constructive cost model was developed by Barry W. Boehm in the late 1970s[1] and published in Boehm's 1981 book Software Engineering Economics[2] as a model for estimating effort, cost, and schedule for software projects. It drew on a study of 63 projects at TRW Aerospace where Boehm was Director of Software Research and Technology. The study examined projects ranging in size from 2,000 to 100,000 lines of code, and programming languages ranging from assembly to PL/I. These projects were based on the waterfall model of software development which was the prevalent software development process in 1981.
References to this model typically call it COCOMO 81. In 1995 COCOMO II was developed and finally published in 2000 in the book Software Cost Estimation with COCOMO II.[3] COCOMO II is the successor of COCOMO 81 and is claimed to be better suited for estimating modern software development projects; providing support for more recent software development processes and was tuned using a larger database of 161 projects. The need for the new model came as software development technology moved from mainframe and overnight batch processing to desktop development, code reusability, and the use of off-the-shelf software components.
COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. The first level, Basic COCOMO is good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to its lack of factors to account for difference in project attributes (Cost Drivers). Intermediate COCOMO takes these Cost Drivers into account and Detailed COCOMO additionally accounts for the influence of individual project phases. Last one is Complete COCOMO model which addresses the shortcomings of both basic & intermediate.
Tools
An online COCOMO II tool implementation of the model is available for software cost estimation.[4] It is developed by Ray Madachy, a co-author of COCOMO II, and conforms to the book definition for the post-architecture model. An example estimate from the tool is shown below.
Intermediate COCOMO
Intermediate COCOMO computes software development effort as function of program size and a set of "cost drivers" that include subjective assessment of product, hardware, personnel and project attributes. This extension considers a set of four "cost drivers", each with a number of subsidiary attributes:
- Product attributes
- Required software reliability extent
- Size of application database
- Complexity of the product
- Hardware attributes
- Run-time performance constraints
- Memory constraints
- Volatility of the virtual machine environment
- Required turnabout time
- Personnel attributes
- Analyst capability
- Software engineering capability
- Applications experience
- Virtual machine experience
- Programming language experience
- Project attributes
- Use of software tools
- Application of software engineering methods
- Required development schedule
Each of the 15 attributes receives a rating on a six-point scale that ranges from "very low" to "extra high" (in importance or value). An effort multiplier from the table below applies to the rating. The product of all effort multipliers results in an effort adjustment factor (EAF). Typical values for EAF range from 0.9 to 1.4.
| Cost Drivers | Ratings | |||||
|---|---|---|---|---|---|---|
| Very Low | Low | Nominal | High | Very High | Extra High | |
| Template:Rh colspan=7 |Product attributes | ||||||
| Required software reliability | 0.75 | 0.88 | 1.00 | 1.15 | 1.40 | |
| Size of application database | 0.94 | 1.00 | 1.08 | 1.16 | ||
| Complexity of the product | 0.70 | 0.85 | 1.00 | 1.15 | 1.30 | 1.65 |
| Template:Rh colspan=7 |Hardware attributes | ||||||
| Run-time performance constraints | 1.00 | 1.11 | 1.30 | 1.66 | ||
| Memory constraints | 1.00 | 1.06 | 1.21 | 1.56 | ||
| Volatility of the virtual machine environment | 0.87 | 1.00 | 1.15 | 1.30 | ||
| Required turnabout time | 0.87 | 1.00 | 1.07 | 1.15 | ||
| Template:Rh colspan=7 |Personnel attributes | ||||||
| Analyst capability | 1.46 | 1.19 | 1.00 | 0.86 | 0.71 | |
| Applications experience | 1.29 | 1.13 | 1.00 | 0.91 | 0.82 | |
| Software engineer capability | 1.42 | 1.17 | 1.00 | 0.86 | 0.70 | |
| Virtual machine experience | 1.21 | 1.10 | 1.00 | 0.90 | ||
| Programming language experience | 1.14 | 1.07 | 1.00 | 0.95 | ||
| Template:Rh colspan=7 |Project attributes | ||||||
| Application of software engineering methods | 1.24 | 1.10 | 1.00 | 0.91 | 0.82 | |
| Use of software tools | 1.24 | 1.10 | 1.00 | 0.91 | 0.83 | |
| Required development schedule | 1.23 | 1.08 | 1.00 | 1.04 | 1.10 | |
The Intermediate Cocomo formula now takes the form:
- E = a(KSLOC)b(EAF)Script error: No such module "Check for unknown parameters".
where E is the effort applied in person-months, KSLOC is the estimated number of thousands of source lines of code delivered for the project, and EAF is the factor calculated above. The coefficient a and the exponent b are given in the next table for different project types.
Software project a b c Organic 3.2 1.05 0.38 Semi-detached 3.0 1.12 0.35 Embedded 2.8 1.20 0.32
The Development time D and also the most effective number of Persons P calculation uses E in the same way as in the Basic COCOMO:
- D = 2.5 EcScript error: No such module "Check for unknown parameters".
- Template:Tmath
Note that in addition to the EAF, the parameter a is different in Intermediate COCOMO from the Basic model:
Software project a Organic 2.4 Semi-detached 3.0 Embedded 3.6
The parameters b and c are the same in both models.
See also
- Comparison of development estimation software
- Cost overrun
- COSYSMO
- Estimation in software engineering
- Function point
- Object point
- Putnam model
- SEER-SEM
- Software development effort estimation
- Software engineering economics
- PRICE Systems
References
<templatestyles src="Reflist/styles.css" />
- ↑ Script error: No such module "citation/CS1".File:.docx icon.svgDOC
- ↑ Script error: No such module "citation/CS1".
- ↑ Barry Boehm, Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz, Ray Madachy, Donald J. Reifer, and Bert Steece. Software Cost Estimation with COCOMO II (with CD-ROM). Englewood Cliffs, NJ:Prentice-Hall, 2000. Template:ISBN
- ↑ Ray Madachy. COCOMO II Tool. softwarecost.org. Accessed October 2025.
Script error: No such module "Check for unknown parameters".
Further reading
- Script error: No such module "Citation/CS1".
External links
- COCOMO 81 data on tera-PROMISE
- Analysis of the COCOMO 81 data obtains a different value for the Organic exponent.