Skip to main content

COCOMO

Short answer

COCOMO is an algorithmic cost estimation model that computes effort, development time, and staffing from software size in KLOC and project mode. For a 50 KLOC organic project, using formulas E=2.4×KLOC^1.05 and D=2.5×E^0.38, effort is about 146 person-months, time 16.6 months, needing about 9 people.

Explain COCOMO.

COCOMO (Constructive Cost Model) is an algorithmic software cost estimation model developed by Barry Boehm (1981). It estimates effort (person-months), development time (months) and staffing from the size of the software in thousands of delivered source lines (KLOC). It is a parametric estimating technique.

Models

  1. Basic COCOMO: estimates from size only.
  2. Intermediate COCOMO: adds 15 cost drivers (product, hardware, personnel, project attributes) as an effort adjustment factor (EAF).
  3. Detailed COCOMO: applies drivers by phase.

Project modes (Basic COCOMO)

ModeDescriptionabcd
OrganicSmall team, familiar problem, simple2.41.052.50.38
Semi-detachedMedium team, mixed experience3.01.122.50.35
EmbeddedTight constraints, hardware-dependent3.61.202.50.32

Formulas

  • Effort E = a × (KLOC)ᵇ person-months
  • Development time D = c × Eᵈ months
  • Average staff = E / D persons

(Intermediate: E = a × (KLOC)ᵇ × EAF, with a = 3.2, 3.0, 2.8 for the three modes.)

Worked example: 50 KLOC product

ModeEffort (PM)Time (months)Staff
Organic2.4 × 50^1.05 = 145.92.5 × 145.9^0.38 = 16.68.8
Semi-detached3.0 × 50^1.12 = 239.92.5 × 239.9^0.35 = 17.014.1
Embedded3.6 × 50^1.20 = 393.62.5 × 393.6^0.32 = 16.923.3

Answer (organic): effort about 146 person-months, time about 16.6 months, about 9 people.

Advantages

  • Simple, transparent, well documented, quick early estimate.

Limitations

  • Depends on accurate size (KLOC) estimate.
  • Calibrated on old data (1970s projects); not ideal for modern agile, reuse or RAD.
  • Ignores some factors in the basic form.

COCOMO II (1995 onward) updates the model with Application Composition, Early Design and Post-Architecture stages, uses function points or object points, and scale factors.

✓ Answer checked by Claude Opus 5.5 (high effort)

All ICT Project Management chapter 15 questions →