Escolar Documentos
Profissional Documentos
Cultura Documentos
CHAPTER 4
Cost estimation should never be an activity that is performed independently of technical work.
In the early life-cycle phases, cost estimation is closely related to design activities, where the
interaction between these activities is iterated many times as part of doing design trade
studies and early risk analysis. Later on in the life-cycle, cost estimation supports
management. The purpose of software cost estimation is to:
Define the resources needed to produce, verify, and validate the software product and
manages these activities.
Quantify, in so far as is practical, the uncertainty and risk inherent in this Estimate.
We should have to keep in our mind that there are many factors that influences the cost of
the product. The effects of this factors, and hence the cost of the development or
maintenance effort, are difficult to estimate. Primary among the cost factors are the individual
abilities of project personnel and their familiarity with the application area the complexity of
the products, the size of product, the available time, the required level of reliability, the level
of technology utilized and the availability, familiarity, and stability of the system used
developed the product
The major factors that influence the software costs are as follows:
Programmer ability
Programmer complexity
Product size
Required reliability
Level of Technology
COCOMO MODEL
The software cost estimation model this report will focus on is the Consecutive Cost Model,
also known as COCOMO. It was developed in 1981 by Barry Bohem proposed three levels
of the model; basic, intermediate, detailed. We have chosen to use the intermediate level for
our cost estimation model. The basic steps to determine the cost are:
Obtain an initial estimate of development effort from the estimate thousands of lines
of source code (KLOC).
Ei = A × (KDLOC)
Determine a set of A 15 multiplying factors from different attributes of the Project.
Adjust the effort estimate by multiplying the initial estimates with all the Multiplying
factors.
The value of constants A and B depends on the project type. In this model, the projects are
categorized into three modes – organic, semidetached and embedded. Organic Mode: This
mode is usually carried out in house by developer teams that are familiar with application
domain.
System A B
Organic 3.2 1.05
Semidetached 3.0 1.12
Embedded 2.8 1.2
So, according to this our project falls under the category of organic.
A = 3.2
B = 1.05
Ei = 3.2 × (KLOC)
1.05
= 3.2 × (.700)
1.05
= 2.24
From the requirements, the rating of different cost driver attributes assessed.
= 1.54
E= EAF × Ei
= 1.54 × 2.24
= 3.4 PM
D= 3.4 × (2.95)
0.38
= 7.6 M
=8.0 M (approx.)
Where,
Person Required:
= 15
M = 15 PM / 5 M
M = 3P
= Rs 3,000
Total duration of project is 5 months. So, for completion of the project each individual
Programmer would get = Rs 5,000 × 4
= Rs 15,000
= Rs 45,000