0% found this document useful (0 votes)
7 views10 pages

Software Engineering

The COCOMO Model, proposed by Barry Boehm in 1981, is a software cost estimation model that predicts the effort, cost, and schedule for software development projects based on the analysis of 63 projects. It categorizes projects into three types: Organic, Semi-detached, and Embedded, and includes phases such as planning, system design, detailed design, coding, and testing. While it offers systematic cost estimation and helps identify key factors impacting project cost, it has limitations such as assuming project size as the main factor and not accounting for team-specific characteristics.

Uploaded by

mehatab661
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views10 pages

Software Engineering

The COCOMO Model, proposed by Barry Boehm in 1981, is a software cost estimation model that predicts the effort, cost, and schedule for software development projects based on the analysis of 63 projects. It categorizes projects into three types: Organic, Semi-detached, and Embedded, and includes phases such as planning, system design, detailed design, coding, and testing. While it offers systematic cost estimation and helps identify key factors impacting project cost, it has limitations such as assuming project size as the main factor and not accounting for team-specific characteristics.

Uploaded by

mehatab661
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

SOFTWARE

ENGINEERING
COCOMO MODEL
• The Constructive Cost Model (COCOMO) It was
proposed by Barry Boehm in 1981 and is based on
the study of 63 projects, which makes it one of the
best-documented models.
• It is a Software Cost Estimation Model that helps
predict the effort, cost, and schedule required for a
software development project.
• COCOMO Model is a procedural cost estimate
model for software model and is often used as
a process of reliably predicting the various
parameters associated with making a project
such as size, effort, cost, time, and quality.

• The key parameters that define the quality of


any software product , which are also an
outcome of COCOMO, are primarily effort and
schedule.
Types Of Projects In COCOMO
Model
software projects are categorized into three
types based on their complexity, size, and the
development environment. These types are:
1. Organic

2. Semi-detached

3. Embedded
STRUCTURE
OF COCOMO
MODEL
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 data flow between them.
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.
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:
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.

You might also like