<Project Name>

COCOMO II Estimation Sheet

1 Document Information
Title COCOMO II Estimation Sheet Version 0.1
Project <Project Name> Status Draft/Reviewed/Approved
Client <Client Name> Type Document
Rec # XYZ-COCOMO II Estimation Sheet Created 28-May-2006
Author <Author Name> Updated 29-May-2006

1.1 Revision History

Distribution Change
Ver. # Revision Date Author Date Ref. Brief Description
0.1 28-May-2006 12-Apr-2007

1.2 Distribution List

<DevMgr>
<Company Contact Person>
<Project Team>

1.3 Review and Approvals

Approved By / (Role) Reviewed By / (Role) Version #
Introduction
TS Cocomo II based estimated sheet is a toolkit for software sizing and estimation. One can estimate the size of work using F
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 this 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

How to estimate project size using this toolkit?

Pre-requisite of using this sheet is that user should have familiarity of Function Points (FP). He should be aware of FP countin
the FPs sheet for each feature/component of the application estimate the count and complexity of Internal Logical Files (ILF),
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 ap
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.

How to estimate effort using this toolkit?

After the FPs and SLOC is estimated go to the effort sheet and estimate the scaling factors and effort multipliers. Guidelines o
select appropriate value for an effort multiplier or the scaling factor are provided in comments of their respective description. A
have selected the appropriate values please check the consolidated size and effort estimates below.
Now the effort is calculated and its time to break this effort into different phases of the project. Please set the percentages in th
Distribution" sheet. Ensure that all percentage should sum to 100%. After setting the percentages please check the effort brea
"Effort Summary" sheet.

How to estimate Cost using this toolkit?

After the size and effort are estimated its time to estimate cost. First go to the "Rates" sheet to select primary and secondary r
After selecting the factor check what is the rate tier selected by the system. If "Borderline Case" appear next to the selected ra
should double check if the selected rate is appropriate.
After selecting the rate go to the cost sheet and adjust effort to quote. Round the effort numbers if you feel appropriate. Also c
blended rate is appropriate and competitive.

How to estimate schedule using this toolkit?

After the cost estimation is complete go to the "Plan sheet" to check if the project can be finished in appropriate duration. Adju
Resources, Slacks and Other Factors and then check if the estimated project duration is appropriate and feasible to the client.
schedule is not appropriate then re-adjust resources etc to verify if the required project duration can be achieved.
 ILF EIF EI EO
Features Comments Reference Low Avg High Low Avg High Low Avg High Low Avg
1EI - History and Ailment
1EQ - Searching through
History and Ailment
Patient History and 2 EO - 2 other view or
Clinical Information reports 0 0 0 0 0 0 1 5 1 0 0

Integration through EDI with

Government or one other
body:
1 EI Employee Salary
Report
2 EQ - Account Receivable
Billing and Payable
Total Artifacts 0 0 0 0 0 0 1 5 1 0 0

Total FP 32
EO EQ
High Low Avg High Total FPs DEV Days DEV Hours Total Days

0 1 0 0 32 10.66 85.00 28.06

0 0 0 0.00 0.00 0.00

0 1 0 0 10.66 85.00 28.06
Features Comments Reference Language
Java,JSP,J
Total:
Estimated SLOC Total FPs Dev Days Total Days
0 0.0000 0 0
0 0.0000 0 0
Cocomo II

PM = A*Size^E*Product(All Effort Multipliers - EM)

Exponent E = B+(0.01*SUM(Scaling Factors))

Scaling Factors
SF Description Level Value
Maturity Process Maturity Nominal 4.68

Experience of similar
PREC Projects Nominal 3.72
Flexibility required in the
FLEX System Nominal 2.03

TEAM Team Cohesiveness 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 Extra Low 0.49
Reusability concern with
respect to current and
RUSE future projects Low 0.95
PDIF Platform Difficulty Very 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 High 0.87
SCED Schedule Pressure Nominal 1

Constants Value
B 0.91
B2 1.23
A 2.94
E 1.0426
EM 0.254422511595

Consolidated Size and Effort

Technology Java,JSP,J2EE
Increase due to
lifecycle 0%
SLOC per FP 60
SLOC 1920
PM 1.4766
Man-days 28.0560
FP from LOC 32.0000
Hours per FP 7.0140 Usually this number should be between 6 to 10 hours depending up

SF Scale PREC FLEX TEAM

Very Low 6.20 0.00 5.48
Low 4.96 1.01 4.38
Nominal 3.72 2.03 3.29
High 2.48 3.04 2.19
Very High 1.24 4.05 1.10
Extremely High 0.00 5.07 0.00

EM Scale RCPX RUSE PDIF

Extra Low 0.49 0.95 0.87
Very Low 0.60 0.95 0.87
Low 0.83 0.95 0.87
Nominal 1.00 1.00 1.00
High 1.33 1.07 1.29
Very High 1.91 1.15 1.81
Extremely High 2.72 1.24 2.61
Instructions/Comments
Recommended values for CMMi level 2 companies is Nominal. For Level 3 its High

For Projects of new domain (that is domain we have not worked on) always select low. Select
Nominal or High for projects that we are creating from scratch but we have some knowledge
about domain. Select very high or extremely high for Next Releases of existing projects

We usually use Nominal but check comments on description for details

Team Cohesiveness is always extremely high in projects where team is small and not
distributed across the globe

We usually use Nominal but check comments on description for details

Instructions/Comments

The kind of projects we have in Technosoft we normally use extra low or very low. Check
comments on description for details

We usually use Low but check comments on description for details

We usually use Very Low but check comments on description for details

We usually use High but check comments on description for details

We usually use High but check comments on description for details

We usually use High for .NET and Nominal for java but check comments on description for
details
We usually use Nominal but check comments on description for details
umber should be between 6 to 10 hours depending upon above parameters

RESL Maturity
0.00 7.80
1.41 6.24
2.83 4.68
4.24 3.12
5.65 1.56
7.07 0.00

PERS PREX
2.12 1.59
1.62 1.33
1.26 1.22
1.00 1.00
0.83 0.87
0.63 0.74
0.50 0.62
FCIL SCED
1.43 1.00
1.30 1.00
1.10 1.00
1.00 1.00
0.87 1.14
0.73 1.43
0.62 1.43
Summary Units
Category Percentage of Development
Requirements Analysis 7%
Architecture & Design 7%
Development 38%
Customer Review Changes 10%
Test Planning 4%
Testing 10% 24%
Bug Fixes 10%
Documentation 0%
Training 0% 2%
Deployment 2%
Project Planning 2%
Project Monitoring 6%
12%
CM 2%
Audits 2%
100%

NOTE: Above numbers are estimated distribution on the basis of experience and on the basis of previous projects
the basis of previous projects
Category Effort (Days) Effort (Hours) Comments/Assumptions
Requirements Analysis 1.96 15.71 Requirements Analysis Hours
Architecture & Design 1.96 15.71 Architecture, FS and A&D Hours
Development 10.66 85.29
Customer Review Changes 2.81 22.44
Test Planning 1.12 8.98 Output are Test Plan and Test Cases
Testing 2.81 22.44 Output is Test Results
Bug Fixes 2.81 22.44
Outputs are Deployment and Build
Documentation 0.00 0.00 Documents
Training 0.00 0.00
Deployment 0.56 4.49 Effort to deploy application
Project Planning 0.56 4.49
Project Monitoring 1.68 13.47
CM 0.56 4.49
Audits 0.56 4.49
Total Effort 28.06 224.45
Cost Units
Units per hour per days
Architect/Designer 0 0
Developer (Blended rate for
Senior and Junior Developer) 0 0
Testing Lead 0 0
Tester 0 0
Technical Writing Cost 0 0
Manager 0 0
On-site Manager 0 0

Discount Percentage: Comments (Reason for Discount):

We have kept some margin because team is new but this
Discount by Dev Team: 10.0% shouldn't be billed to customer
Discount by Sales Team: 15.0% New Customer Discount
Total Discount: 25.0%

Total Project Cost

Discounted
Effort (Days) Effort for Rounded Effort
Category Estimated Sales Effort (Hours)
Requirements Analysis 2.0 1.5 1.5 12.00
Architecture & Design 2.0 1.5 1.5 12.00
Development 10.7 8.0 8.0 64.00
Customer Review Changes 2.8 2.1 2.5 20.00
Test Planning 1.1 0.8 1.0 8.00
Testing 2.8 2.1 2.5 20.00
Bug Fixes 2.8 2.1 2.5 20.00
Documentation 0.0 0.0 0.0 0.00
Training 0.0 0.0 0.0 0.00
Deployment 0.6 0.4 0.5 4.00
Project Planning 0.6 0.4 0.5 4.00
Project Monitoring 1.7 1.3 1.5 12.00
CM 0.6 0.4 0.5 4.00
Audits 0.6 0.4 0.5 4.00
Total 28.1 21.0 23.0 184.00
Blended Rate

Effort and Cost to Quote

Effort
Category Effort (Days) (Hours) Cost
Analysis and Design 3.0 24.00 0.00
Development 8.0 64.00 0.00
Customer Review Changes 2.5 20.00 0.00
Test Planning 1.0 8.00 0.00
Testing 2.5 20.00 0.00
Defect Fixation during Internal
Testing 2.5 20.00 0.00

User Manuals and Install Guides 0.0 0.00 0.00

Training 0.0 0.00 0.00
Deployment 0.5 4.00 0.00
Project Management 3.0 24.00 0.00
Total 23.0 184.0 $0.00

Total Support Cost

Man Months 1
Man Days 5
Category Hours per day Total Hours Cost
Designers 0.5 2.5 $0
Developers 8 40 $0
Testers 1 5 $0
Managers 0.5 2.5 $0
Total $0
nt):
use team is new but this

Cost
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0
Assumptions

Test Planning, Documentation and Management activities are carried out

in parallel to other main activities of design, development and testing

Resources
Designers 1
Developers 1
Testers 1
Others
Comunication Delay in Analysis
and Design 25%
Possible Critical Chain Delay in
Development 15%
Possible Fixation Delay in
Testing 20%
Working days in a month 21
Ratio of calendar days 1.47619047619

Project Plan - Waterfall

Phase Duration (days) Duration (months)
Requirements/Design Phase 3.8 0 Month 6 Day
Development Phase 9.2 0 Month 14 Day
Testing Phase 3.0 0 Month 4 Day
Total 16.0 0 Month 24 Day
Slack 4.0
Grand Total 20.0 0 Month 29 Day

Iterative Plan
Iteration Duration
Iterations 2 (without Slacks)
1 50% 7.98
2 50% 7.98
3 0% 0.00
4 0% 0.00
5 0% 0.00
Total 100%
Slacks
Initial Ramp-up 1
Deployment for testing etc 1
Code/Peer Reviews 1
Shipment Packaging & Review 1

Total Slack 4

Requirements/Design Development Testing

2.0 5.0 2.0
2.0 5.0 2.0
0.0 0.0 0.0
0.0 0.0 0.0
0.0 0.0 0.0
Assumptions

Test Planning, Documentation and Management activities are carried out

in parallel to other main activities of design, development and testing

Resources
Business Analyst 1
Architects & Designers 1
Developers 1
Testers 1
Others
Comunication Delay in Analysis
and Design 25%
Possible Critical Chain Delay in
Development 15%
Possible Fixation Delay in
Testing 20%
Working days in a month 21
Ratio of calendar days 1.47619047619

Project Plan - Waterfall

Phase Duration (days) Duration (months)
Requirements Analysis 1.9 0 Month 3 Day
Design Phase 1.9 0 Month 3 Day
Development Phase 9.2 0 Month 14 Day
Testing Phase 3.0 0 Month 4 Day
Total 16.0 0 Month 24 Day
Slack 4.0
Grand Total 20.0 0 Month 29 Day

Iterative Plan
Iteration Duration
Iterations 3 (without Slacks)

1 20% 6.00
2 50% 5.00

3 30% 6.00
4 0% 0.00
5 0% 0.00
Total 100%
Slacks
Initial Ramp-up 1
Deployment for testing etc 1
Code/Peer Reviews 1
Shipment Packaging & Review 1
Total Slack 4

Comments
Includes A&D Phase plus percentage of
Development Phase
Percentage of development phase
Percentage of development phase and
testing
0.0
0.0