Define the COCOMO Model and Explain Its Types (with Benefits)

The COCOMO (Constructive Cost Model) is a set of well-known software cost estimation models developed by Barry W. Boehm. In COCOMO, estimated effort is computed from size (typically KLOC), then adjusted using project attributes (e.g., product, computer, personnel, and project constraints) expressed via effort multipliers. The model is widely used in early planning because it provides a structured way to translate size and assumptions into approximate schedules and budgets.

Key idea: higher-fidelity COCOMO variants require more detailed inputs (cost drivers), which typically yields improved estimation accuracy for projects where those inputs can be assessed reliably. (When only coarse information is available, simpler variants are used.)

Core concepts and inputs

COCOMO’s estimates are driven primarily by:

• Software size (e.g., KLOC or equivalent sizing measures)
• Effort multipliers (derived from cost drivers)
• Development modes (historically: organic, semi-detached, embedded)

In the classical COCOMO family (often referred to as COCOMO 81), the project begins with a baseline effort estimate based on size and development mode, then may apply additional multipliers and more detailed model parameters depending on which type is selected.

Types of COCOMO models (and what changes between them)

COCOMO is commonly presented in three types (for the classical COCOMO 81 family):

1. Basic COCOMO (early, high-level estimates)
2. Intermediate COCOMO (adds cost drivers / multiplicative adjustments)
3. Detailed COCOMO (adds further granularity such as scale and phase-level estimation inputs)

The benefit progression is that each successive type uses more information, allowing better tailoring to project characteristics.

1) Basic COCOMO

Basic COCOMO is the simplest variant. It uses:

• Software size as the main input
• A development mode to select baseline parameters

What you get: quick estimates with minimal data.
Primary benefit: extremely fast early estimation when requirements are still volatile.

2) Intermediate COCOMO

Intermediate COCOMO improves the Basic model by incorporating effort multipliers (cost drivers). These account for differences such as:

• Product attributes (e.g., required reliability/complexity)
• Computer constraints (e.g., execution environment)
• Personnel capability and experience
• Project constraints (e.g., use of modern tools or schedule pressure)

What you get: more realistic estimates reflecting project-specific characteristics.
Primary benefit: balances accuracy with manageable data-collection effort.

3) Detailed COCOMO

Detailed COCOMO further refines estimates by using more detailed modeling structure than Intermediate. The intent is to capture where effort is spent and how attributes affect effort across phases (e.g., early design vs implementation-like activities, depending on the detailed model structure used).

What you get: the most tailored and potentially most accurate estimates within the classical family.
Primary benefit: supports stronger planning decisions when you can provide the required detailed inputs.