COCOMO Model — Definition, Types & Benefits

Definition

COCOMO (Constructive Cost Model), developed by Barry Boehm, is an algorithmic cost/effort estimation model for software projects. It estimates effort (person-months, PM) and development time (months, TDEV) from the estimated size of the software (measured in KLOC — thousands of lines of code).

Types of COCOMO

1. Basic COCOMO — a quick, top-down estimate using only size:

$$E = a_b (KLOC)^{b} \text{ PM}, \qquad \text{TDEV} = c_b (E)^{d} \text{ months}$$

Project type	a	b	c	d
Organic	2.4	1.05	2.5	0.38
Semi-Detached	3.0	1.12	2.5	0.35
Embedded	3.6	1.20	2.5	0.32

• Organic: small, simple, experienced team, flexible requirements.
• Semi-Detached: medium project, mixed experience, moderate requirements.
• Embedded: large, complex, tight/hardware-constrained requirements.

2. Intermediate COCOMO — more accurate; adds 15 cost-driver attributes (product, hardware, personnel, project characteristics) each rated and multiplied into an Effort Adjustment Factor (EAF):

$$E = a (KLOC)^{b} \times \text{EAF}$$

3. Detailed COCOMO — most accurate; analyzes each phase (planning, design, coding, testing, etc.) separately with its own effort multipliers, and pays attention to the project's modules/components.

Benefits of COCOMO

1. Objective estimates — effort, schedule, staff, cost derived from size; reduces guesswork.
2. Scalability across project types — organic/semi-detached/embedded formulas fit different project natures.
3. Sensitivity analysis (basic/intermediate) — shows how cost drivers (personnel skill, complexity, reliability) change the estimate, guiding trade-offs.
4. Phase-wise planning (detailed) — effort broken down by development phase and component for finer project control.
5. Calibration — coefficients can be tuned to an organization's historical data to improve accuracy.
6. Risk awareness — cost drivers highlight where effort is high, prompting mitigation.

Limitations (for balance)

• Dependent on size accuracy (KLOC/FP) — poor size prediction ⇒ poor effort estimate.
• Requires historical data for calibration; the fixed coefficients may not fit new technology.
• Difficulty handled only through the intermediate set of cost drivers; does not address requirement volatility well.

Summary table

Type	Size needed	Accuracy	Use
Basic	KLOC only	Low/rough	Quick early estimates
Intermediate	KLOC + cost drivers	Medium	Standard project estimation
Detailed	Per-phase component size + drivers	High	Detailed planning/control

Summary: COCOMO is a size-driven algorithmic model (basic/intermediate/detailed variants) that estimates effort and schedule with increasing accuracy, helping managers plan, staff, schedule, and control software projects.