Scribd
Upload
25 views

Lecture (13 14) COCOMO

cocomo model of software engineering

Uploaded by

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

Lecture (13 14) COCOMO

cocomo model of software engineering

Uploaded by

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

COCOMO Model

1
Objectives
At the end of this lesson the student would be
able to:
 Differentiate among organic,

semidetached and embedded software


projects.
 Explain basic COCOMO.

 Differentiate between basic COCOMO

model and intermediate COCOMO model.


 Explain the complete COCOMO model.

2
Project Planning
 Boehm postulated that any software development project
can be classified into one of the following three categories
based on the development complexity:
 Organic: A development project can be considered of organic
type, if the project deals with developing a well understood
application program, the size of the development team is
reasonably small, and the team members are experienced in
developing similar types of projects.
 Semidetached: A development project can be considered of
semidetached type, if the development consists of a mixture of
experienced and inexperienced staff. Team members may
have limited experience on related systems but may be
unfamiliar with some aspects of the system being developed.
 Embedded: A development project is considered to be of
embedded type, if the software being developed is strongly
coupled to complex hardware, or if the stringent regulations
on the operational procedures exist.
3
COCOMO
 COCOMO (Constructive Cost Estimation Model)
was proposed by Boehm [1981]. According to
Boehm, software cost estimation should be done
through three stages: Basic COCOMO,
Intermediate COCOMO, and Complete
COCOMO.

4
Basic COCOMO Model

 The basic COCOMO model gives an approximate


estimate of the project parameters. The basic
COCOMO estimation model is given by the
following expressions:
Effort = a1 х (KLOC)a2 PM
 Tdev = b1 x (Effort)b2 Months

Where
 KLOC is the estimated size of the software product
expressed in Kilo Lines of Code,
 a1, a2, b1, b2 are constants for each category of software
products,
 Tdev is the estimated time to develop the software,
expressed in months,
 Effort is the total effort required to develop the software
product, expressed in person months (PMs).
5
Estimation of development effort

Organic : Effort = 2.4(KLOC)1.05 PM


Semi-detached : Effort = 3.0(KLOC)1.12 PM
Embedded : Effort = 3.6(KLOC)1.20 PM

6
Estimation of development time

 Organic : Tdev = 2.5(Effort)0.38 Months


 Semi-detached : Tdev = 2.5(Effort)0.35
Months
 Embedded : Tdev = 2.5(Effort)0.32 Months

7
the effort required to develop a product increases very rapidly
with project size.
8
The development time is a sublinear function of the size of the
product, i.e. when the size of the product increases by two times,
the time to develop the product does not double but rises
moderately. 9
Example
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 software engineers be Rs. 15,000/-
per month. Determine the effort required to develop the
software product and the nominal development time.
From the basic COCOMO estimation formula for organic
software:
Effort = 2.4 х (32)1.05 = 91 PM
Nominal development time = 2.5 х (91)0.38 = 14
months
Cost required to develop the product = 14 х 15,000
= Rs. 210,000/-

10
Intermediate COCOMO model

 The basic COCOMO model assumes that effort and


development time are functions of the product size
alone.
 Therefore, in order to obtain an accurate
estimation of the effort and project duration, the
effect of all relevant parameters must be taken
into account.
 The intermediate COCOMO model recognizes this
fact and refines the initial estimate obtained using
the basic COCOMO expressions by using a set of
15 cost drivers (multipliers) based on various
attributes of software development
11
 In general, the cost drivers can be classified as being
attributes of the following items:
 Product: The characteristics of the product that are
considered include the inherent complexity of the product,
reliability requirements of the product, etc.
 Computer: Characteristics of the computer that are
considered include the execution speed required, storage
space required etc.
 Personnel: The attributes of development personnel that
are considered include the experience level of personnel,
programming capability, analysis capability, etc.
 Development Environment: Development environment
attributes capture the development facilities available to the
developers. An important parameter that is considered is the
sophistication of the automation (CASE) tools used for
software development.
12
Complete COCOMO model

 Both the basic and intermediate COCOMO


models is that they consider a software product
as a single homogeneous entity
 Differences
 several smaller sub-systems having widely different
characteristics.
 may be considered as organic type, some semidetached,
and some embedded.
 may be different,
 reliability requirements may be high
 some the development team might have no previous
experience of similar development.

13
 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
subsystems.
 The cost of each subsystem is estimated
separately.
 This approach reduces the margin of error in the
final estimate.

14

You might also like