Limitations of COCOMO Model
Limitations of COCOMO Model
model
SE-607
Software Engineering Economics
Limitations of COCOMO
Dependency on accurate KLOC
The cocomo model heavily relies on an
accurate estimate number of lines of code
(KLOC) early in the project. However KLOC is
difficult to measure at initial stage which can
lead to inaccurate results.
Neglects non coding Effort and
time factor
The model focus on coding efforts, neglects
other essential activities such as testing,
documentation and project management also
team dynamics and individuals skill level.
Limitations of COCOMO
Outdated model for modern
practices
COCOMO was developed in 1980’s,primarily for
waterfall based software development. Modern
methodologies like agile, continuous integration
are not adequately addressed by the original
model.
Lack of Adoptability for small
projects
It tends to work better for large projects, for
smaller projects it may provide inaccurate
estimates as it was designed with large projects
in mind.
Limitations of COCOMO
Complexity
COCOMO involves intricate calculations and
many parameters which make it challenging
for users especially for those who don’t have
a background in Software engineering or
project management.
Assumptions
The model is based on specific assumptions
about project size, team experiences and
productivity. These assumptions do not hold
true for all type of project leading to
potential inaccuracies.
Limitations of COCOMO
Subjectivity
Some parameters in cocomo require
subjective judgments, such as assessment of
team capability or project complexity. This
subjectivity can lead to variability to
estimates based on different evaluators.
Dependency on historical data
Cocomo relies on historical project data for
calibration. If relevant data is lacking or if
post projects differ significantly from the
current projects, the estimates can be
unreliable.
Limitations of COCOMO
Lack of documentation
It ignores all the documenting and
requirements which leads to the main
reason of accuracy limitations.
Assumes static requirements
Cocomo model assumes that software
requirements remains stable
throughout the development life cycle,
which rarely happens in real projects
especially for dynamic systems.