Professional Documents
Culture Documents
Cocomo II Estimation
Cocomo II Estimation
TS Cocomo II based estimated sheet is a toolkit for software sizing and estimation. One can estimate the size of work using FP
SLOC. Effort is then estimated using Cocomo II. Effort can then be distributed into different project phases and the project cos
calculated. There is a Rates Sheet for selecting appropriate rate for a specific customer.
FP (Function Points)
Function points are a unit measure for software much like an hour is to measuring time, miles are to measuring distance or Ce
measuring temperature
SLOC
Source Line of Code, one line in a computer program. In many languages, each SLOC ends with a semicolon. SLOC is used i
COCOMO as the basis for estimating software-development time.
Cocomo II
COCOMO is a model designed by Barry Boehm to give an estimate of the number of programmer-months it will take to develo
software product
Pre-requisite of using this sheet is that user should have familiarity of Function Points (FP). He should be aware of FP counting
the FPs sheet for each feature/component of the application estimate the count and complexity of Internal Logical Files (ILF), E
Interface Files (EIF), External Inputs (EI), External Outputs (EO) and External Queries (EQ). There are 3 columns Low, Avg. a
under each category; these columns should have the count of low, average and high complexity components against each app
feature. Guidelines on how to judge complexity are provided in comments of ILF, EIF and other headings at the top. Totals are
automatically calculated.
If there are some features in the applications which doesn't support creation of front-end or maintenance of back-end tables th
cannot measure its size. Example of such features is any special code libraries that are invoked on schedule or through some
means to do certain functions. For such functions estimate the lines of code in SLOC sheet. Provide feature details, the progra
language it will be written in and the estimated LOC count and system will automatically calculate its FPs.
Total FP 24
EQ
Avg High Total FPs
0 0 3
0 0 11
0 0 4
0 0 6
0 0
Features Comments Reference Language Estimated SLOC
Feature 5 Java 300
Feature 6 Java 500
Feature 7 Java 100
Total: 900
Total FPs
5.6604
9.4340
1.8868
16.9811
Cocomo II
Scaling Factors
SF Description Level Value
Maturity Process Maturity Nominal 4.68
Experience of similar
PREC Projects Very High 1.24
Flexibility required in the
FLEX System Very Low 0
TEAM Team Conhesiveness Extremely High 0
Project Risk and
RESL Architectural Complexity Nominal 2.83
Effort Multiplier EM
EM Description Level Value
System reliability,
complexity and size
RCPX indicator Very Low 0.6
Reusablity cocern with
respect to current and
RUSE future projects Nominal 1
PDIF Platform Difficulty Extra Low 0.87
Personal capability of
team. Like technical
capability of Programmers,
PERS Designers and testers. High 0.83
Application, Language and
PREX tool experience High 0.87
Using Case tools for
FCIL development etc Nominal 1
SCED Schedule Pressure Nominal 1
Constants Value
B 0.91
A 2.94
E 1
EM 0.38
30
50
30
30
70
150
Resources
Designers 1
Developers 2
Testers 1
Others
Possible Critical Chain Delay in
Development 5%
Possible Fixation Delay in
Testing 5%
Working days in a month 21
Ratio of calendar days 1.48
Iterative Plan
Iteration Duration
Iterations 1 (without Slacks)
1 100% 27.28
2 0% 0.00
3 0% 0.00
4 0% 0.00
5 0% 0.00
Total 100%
Slacks
Initial Ramp-up 0.5
Deployment for testing etc 0.5
Code/Peer Reviews 1
Shipment Packaging & Review 1
Total Slack 3