Scribd
Upload
27 views

Cocomo Model

Uploaded by

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

Cocomo Model

Uploaded by

aaqibalam291
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

COCOMO Model

COCOMO—A HEURISTIC ESTIMATION TECHNIQUE


● Stands for Constructive COst estimation Model
● It is the most widely used estimating technique.
● It is a regression based model developed by Barry Boehm.
● Boehm postulated that any Software development project can be
classified into one of the following three categories based on the
development complexity - organic(application) , semidetached(utility) and
embedded(system).
Organic Projects
● Relatively small group work in familiar environment to develop well
understood applications programs.
● Here little innovation is required, constraints and deadlines are few and
the development environment is stable.
● These are relatively simple and small projects with small teams that are
experienced and work together well.
● Examples include simple business applications, payroll systems, and
inventory management , library management system , hotel management
system etc.
Semi-detached Projects
● These projects are moderately complex, involving larger teams with
varying levels of experience.
● Project teams consist of mixture of experienced and inexperienced staff.
● It is of medium size, some innovation is required, constraints and
deadlines are moderate and the development environment is somewhat
fluid.
● Examples include medium-sized embedded systems or scientific software.
Embedded Projects
● These are large, complex projects with strict requirements and
constraints, often involving tight integration with hardware.
● In this the software is strongly coupled to complex hardware.
● The project team is large , great deal of innovation is required ,
constraints and deadlines are tight and the development environment
consist of many complex interfaces.
● Examples include real-time operating systems, military software, or air
traffic control , ATM’s etc.
Types of COCOMO
● Basic COCOMO
● Intermediate COCOMO
● Detailed COCOMO
Basic COCOMO Model
● It takes the form
Numerical
Q. Assume that the size of an organic type software product has been estimated to be 32,000 lines of
source code. Assume that the average salary of a software developer is Rs. 15,000 per month.
Determine the effort required to develop the software product, the nominal development time, and
the cost to develop the product.

Sol:
3200LOC = 32KLOC
Estimation formula for organic software:
Effort = a(KLOC)^b
= 2.4*(32) ^ 1.05
= 91pm
Development time = c*(Effort)^d

= 2.5 * (91)^0.38

=14 months

Staff cost required to develop the product = 91 * Rs. 15,000

= Rs. 1,465,000
Q. Suppose that a project was estimated to be 400KLOC. Calculate effort and
time for each of three mode of development.

Solution :

Organic

Effort = a(KLOC)^b

= 2.4 * (400)^1.05 = 1295pm

Development Time = c * (Effort) ^ d

= 2.5 * (1295) ^ 0.38 = 38months

Semi-detect

Effort = a(KLOC)^b = 3 * (400)^1.12 = 2462pm


Development Time = c * (Effort) ^ d
= 2.5 * (2462) ^ 0.35 = 38.4 months

Embedded
Effort = a(KLOC)^b
= 3.6 * (400)^1.2 = 4772pm
Development Time = c * (Effort) ^ d
= 2.5 * (4772) ^ 0.32 = 38 months
Intermediate COCOMO
● Extension of basic COCOCMO
● Why use - Basic model lacks accuracy
● Computers software development effort as a function of program size
● The intermediate COCOMO model refines the initial estimate obtained using the
basic COCOMO expressions by scaling the estimate up or down based on the
evaluation of a set of attributes of software development.
● The intermediate COCOMO model uses a set of 15 cost drivers (multipliers) that
are determined based on various attributes of software development.
● These cost drivers are multiplied with the initial cost and effort estimates
(obtained from the basic COCOMO) to appropriately scale those up or down.
Complete COCOMO
A major shortcoming of both the basic and the intermediate COCOMO models is that they
consider a software product as a single homogeneous entity. However, most large systems are
made up of several smaller sub-systems. These sub-systems often have widely different
characteristics.
The complete COCOMO model considers these differences in characteristics of the subsystems
and estimates the effort and development time as the sum of the estimates for the individual
sub-systems.
In other words, the cost to develop each sub-system is estimated separately, and the complete
system cost is determined as the subsystem costs. This approach reduces the margin of error in
the final estimate.

You might also like