COCOMO Model
The Constructive Cost Model (COCOMO) is a
software cost estimation model that helps predict
the effort, cost, and schedule required for a
software development project.
Developed by Barry Boehm in 1981, COCOMO
uses a mathematical formula based on the size of
the software project, typically measured in lines of
code (LOC).
COCOMO Model
The key parameters that define the quality of any
software product, which are also an outcome of
COCOMO, are primarily effort and schedule:
1. Effort: Amount of labor that will be required to
complete a task. It is measured in person-
months units.
2. Schedule: This simply means the amount of
time required for the completion of the job,
which is, of course, proportional to the effort
put in. It is measured in the units of time such
as weeks, and months.
Types of Projects in the COCOMO Model
1. Organic:
A software project is said to be an organic type
if the team size required is adequately small, the
problem is well understood and has been solved
in the past and also the team members have a
nominal experience regarding the problem.
Types of Projects in the COCOMO Model
2. Semi-detached:
A software project is said to be a Semi-detached type
if the vital characteristics such as team size, experience,
and knowledge of the various programming
environments lie in between organic and embedded.
The projects classified as Semi-Detached are
comparatively less familiar and difficult to develop
compared to the organic ones and require more
experience better guidance and creativity.
Eg: Compilers or different Embedded Systems can be
considered Semi-Detached types.
Types of Projects in the COCOMO Model
3. Embedded:
A software project requiring the highest level of
complexity, creativity, and experience requirement
falls under this category.
Such software requires a larger team size than
the other two models and also the developers
need to be sufficiently experienced and creative to
develop such complex models.
The Six phases of detailed COCOMO are:
1. Planning and requirements:
This initial phase involves defining the scope,
objectives, and constraints of the project. It
includes developing a project plan that outlines
the schedule, resources, and milestones.
2. System design: :
In this phase, the high-level architecture of the
software system is created. This includes
defining the system’s overall structure, including
major components, their interactions, and the
The Six phases of detailed COCOMO are:
3. Detailed design:
This phase involves creating detailed specifications
for each component of the system. It breaks down
the system design into detailed descriptions of each
module, including data structures, algorithms, and
interfaces.
4. Module code and test:
This involves writing the actual source code for each
module or component as defined in the detailed
design. It includes coding the functionalities,
implementing algorithms, and developing interfaces.
The Six phases of detailed COCOMO are:
5. Integration and test:
This phase involves combining individual modules
into a complete system and ensuring that they
work together as intended.
6. Cost Constructive model:
The Constructive Cost Model (COCOMO) is a
widely used method for estimating the cost and
effort required for software development projects.
Types of COCOMO Model
There are three types of COCOMO Model:
1. Basic COCOMO Model
2. Intermediate COCOMO Model
3. Detailed COCOMO Model
Types of COCOMO Model
1. Basic COCOMO Model
The Basic COCOMO model is a straightforward
way to estimate the effort needed for a
software development project.
It uses a simple mathematical formula to predict
how many person-months of work are required
based on the size of the project, measured in
thousands of lines of code (KLOC).
Types of COCOMO Model
E = a*(KLOC)b PM
Tdev = c*(E)d
Person required = Effort/ Time
Where,
E is effort applied in Person-Months
KLOC is the estimated size of the software product indicate in
Kilo Lines of Code
Tdev is the development time in months
a, b, c are constants determined by the category of software
project given in below table.
Types of COCOMO Model
2. Intermediate COCOMO Model
The basic COCOMO model assumes that the
effort is only a function of the number of lines of
code and some constants evaluated according to
the different software systems.
Various other factors such as reliability,
experience, and Capability.
These factors are known as Cost Drivers
(multipliers) and the Intermediate Model utilizes
15 such drivers for cost estimation.
Types of COCOMO Model
Intermediate COCOMO Model equation:
E = a*(KLOC)b * EAF PM
Tdev = c*(E)d
Where,
E is effort applied in Person-Months
KLOC is the estimated size of the software product indicate in
Kilo Lines of Code
EAF is the Effort Adjustment Factor (EAF) is a multiplier used
to refine the effort estimate obtained from the basic COCOMO
model.
Tdev is the development time in months
a, b, c are constants determined by the category of software
project given in below table.
Types of COCOMO Model
3. Detailed COCOMO Model
Detailed COCOMO goes beyond Basic and Intermediate
COCOMO by diving deeper into project-specific factors.
It considers a wider range of parameters, like team
experience, development practices, and software
complexity.
By analyzing these factors in more detail, Detailed
COCOMO provides a highly accurate estimation of effort,
time, and cost for software projects.
It’s like zooming in on a project’s unique characteristics
to get a clearer picture of what it will take to complete it
successfully.
Advantages of the COCOMO Model
1. Systematic cost estimation: Provides a systematic way
to estimate the cost and effort of a software project.
2. Helps to estimate cost and effort: This can be used to
estimate the cost and effort of a software project at
different stages of the development process.
3. Helps in high-impact factors: Helps in identifying the
factors that have the greatest impact on the cost and
effort of a software project.
4. Helps to evaluate the feasibility of a project: This can
be used to evaluate the feasibility of a software
project by estimating the cost and effort required to
complete it.
Disadvantages of the COCOMO Model
1. Assumes project size as the main factor: Assumes that
the size of the software is the main factor that
determines the cost and effort of a software project,
which may not always be the case.
2. Does not count development team-specific
characteristics: Does not take into account the specific
characteristics of the development team, which can have
a significant impact on the cost and effort of a software
project.
3. Not enough precise cost and effort estimate: This does
not provide a precise estimate of the cost and effort of a
software project, as it is based on assumptions and
averages.
