Introduction TS Cocomo II based estimated sheet is a toolkit for software sizing and estimation.

One can estimate the size of work using FP and SLOC. Effort is then estimated using Cocomo II. Effort can then be distributed into different project phases and the project cost is 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 Celsius is to 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 in 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 develop a 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 rules. In the FPs sheet for each feature/component of the application estimate the count and complexity of Internal Logical Files (ILF), External Interface Files (EIF), External Inputs (EI), External Outputs (EO) and External Queries (EQ). There are 3 columns Low, Avg. and High under each category; these columns should have the count of low, average and high complexity components against each application 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 backend tables then FP cannot measure its size. Example of such features is any special code libraries that are invoked on schedule or through some other means to do certain functions. For such functions estimate the lines of code in SLOC sheet. Provide feature details, the programming language it will be written in and the estimated

How to estimate project size using this toolkit?

Howthe toFPs estimate effort using this After and SLOC is estimated go to toolkit? the effort sheet and estimate the scaling factors and effort multipliers. Guidelines on how to select appropriate value for an effort multiplier or the scaling factor are provided in comments of their respective description. After you 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 the "Effort Distribution" sheet. Ensure that all percentage should sum to 100%. After setting the percentages please check the effort break-up in the "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 rate factors. After selecting the factor check what is the rate tier selected by the system. If "Borderline Case" appear next to the selected rate then you 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 check if the blended rate is appropriate and competitive.

Howthe tocost estimate schedule using toolkit? After estimation is complete go to this the "Plan sheet" to check if the project can be finished in appropriate duration. Adjust Resources, Slacks and Other Factors and then check if the estimated project duration is appropriate and feasible to the client. If the schedule is not appropriate then re-adjust resources etc to verify if the required project duration can be achieved.

Features Comments Feature 1 Feature 2 Feature 3 Feature 4 Total Artifacts Total FP 24

Reference

ILF EIF EI EO EQ Low Avg High Low Avg High Low Avg High Low Avg High Low 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 1 0 0 0 0 0 3 2 0 0 0 0 0

EQ Avg High 0 0 0 0 0 0 0 0 0 0

Total FPs 3 11 4 6

Features Feature 5 Feature 6 Feature 7

Comments

Reference

Language Estimated SLOC SQL 300 Java 500 Java 100 Total: 900

Total FPs 8.5714 9.4340 1.8868 19.8922

Cocomo II PM = A*Size^E*Product(All Effort Multipliers - EM) Exponent E = B+(0.01*SUM(Scaling Factors)) Scaling Factors
SF Maturity PREC FLEX TEAM RESL Description Process Maturity Experience of similar Projects Flexibility required in the System Team Conhesiveness Project Risk and Architectural Complexity Level Nominal Very High Very Low Extremely High Nominal Value 4.68 1.24 0 0 2.83

Effort Multiplier EM
EM Description System reliability, complexity and size indicator Reusablity cocern with respect to current and future projects Platform Difficulty Personal capability of team. Like technical capability of Programmers, Designers and testers. Application, Language and tool experience Using Case tools for development etc Schedule Pressure Value 0.91 2.94 0.9975 0.3769362 Level Value

RCPX

Very Low

0.6

RUSE PDIF

Nominal Extra Low

1 0.87

PERS PREX FCIL SCED Constants B A E EM

High High Nominal Nominal

0.83 0.87 1 1

Consolidated Size and Effort

Technology Increase due to lifecycle SLOC per FP SLOC PM Man-days Java 0% 53 2326.285714 2.5725 48.8782

FP from LOC Hours per FP SF Scale Very Low Low Nominal High Very High Extremely High EM Scale Extra Low Very Low Low Nominal High Very High Extremely High PREC

43.8922 8.9088 FLEX 6.20 4.96 3.72 2.48 1.24 0.00 RCPX 0.49 0.60 0.83 1.00 1.33 1.91 2.72 RUSE 0.95 0.95 0.95 1.00 1.07 1.15 1.24 0.00 1.01 2.03 3.04 4.05 5.07 TEAM RESL Maturity 5.48 0.00 7.80 4.38 1.41 6.24 3.29 2.83 4.68 2.19 4.24 3.12 1.10 5.65 1.56 0.00 7.07 0.00 PDIF PERS PREX FCIL 0.87 2.12 1.59 1.43 0.87 1.62 1.33 1.30 0.87 1.26 1.22 1.10 1.00 1.00 1.00 1.00 1.29 0.83 0.87 0.87 1.81 0.63 0.74 0.73 2.61 0.50 0.62 0.62

SCED 1.00 1.00 1.00 1.00 1.14 1.43 1.43

Summary Units
Category Percentage of Development Requirements/Design Development Test Planning Testing Documentation Deployment Off-shore Management On-site Management 25% 45% 8% 10% 5% 1% 5% 1% 100%

Category

Effort

Requirements/Design Effort Development Effort Test Planning Testing Effort Documentation Effort Deployment Effort

12.22 22.00 3.91 4.89 2.44 0.49

Comments/Assumptions Outputs are Technical Design and Information Architecture doc. Information Architecture doc will have guidelines for interface design. Source Code Output are Test Plan and Test Cases Output is Test Results Outputs are Deployment and Build Documents Effort to deploy application

Off-shore Management

Output is Detailed Project Plans, Risk and 2.44 Issues tracking, Weekly status reports etc. Client Communication. Output is usually any 0.49 list of issues or improvement opportunities 48.88

On-site Management Effort Total Effort

Rate Tiers
Units Low Architect/Designer Developer (Blended rate for Senior and Junior Developer) Testing Lead Tester Technical Writing Cost Manager On-site Manager Medium 20 15 20 15 15 25 60 Weightage Gold-Standard Sufficient 7 5 30 20 30 20 20 40 100 Weighted Value 0.7 0.25 High 50 30 50 30 30 70 150

Primary Rate Factors

Customer Buying Orientation Hours Availability for Technology

Secondary Rate Factors

Customer Type Build Domain Competency Build Technology Competency Scope Creep Risk Payment Pattern One Time Customer Doesn't Matter Doesn't Matter High Delayed Payments 1 1 2 2 2 20 0.1 0.05 0.1 0.2 0.2 1.6

Selected Rate

High

Buying Orientations Price-Oriented Solution-Oriented Gold-Standard Hours Availability Surplus Sufficient Less Customer Type Good Existing Customer Existing Customer One Time Customer Strategic Value Customer

Value

Description 0 Price is the main factor in making decision for this project Price, quality and other factors combined make the criteria for 1 winning project Customer is highly focused on quality and project features and 2 would give it prime importance in making decisions

Value

Description 0 Hours Inventory has many hours free in this technology area Hours Inventory has some hours free but technology area is 1 utilized more than break-even 2 Hours Inventory has very low hours free in this technology are Description 0 1 2 0

Value

Build Technology Competency Yes Doesn't Matter Avoid Technology

Value 0 1 2

Description

Build Domain Competency Yes Doesn't Matter Avoid Domain Payment Pattern Upfront Timely Payments Timely Payments Delayed Payments Scope Creep Risk High Moderate Low

Value 0 1 2 Value 0 1 2 Value 2 1 0

Description

Description

Description

Selected 50 30 50 30 30 70 150

ng decision for this project combined make the criteria for

quality and project features and n making decisions

s free in this technology area s free but technology area is

ours free in this technology area

Cost Units
Units per hour Architect/Designer Developer (Blended rate for Senior and Junior Developer) Testing Lead Tester Technical Writing Cost Manager On-site Manager per days 50 400

30 50 30 30 70 150

240 400 240 240 560 1200

Total Project Cost

Category Requirements/Design Effort Development Effort Test Planning Testing Effort Documentation Effort Deployment Effort Off-shore Management On-site Management Effort Total Effort (Days) Estimated 12.2 22.0 3.9 4.9 2.4 0.5 2.4 0.5 48.9 Effort (Days) to Quote Cost 11.0 21.0 4.0 5.0 3.0 1.0 3.0 1.0 49.0 Blended Rate $4,400 $5,040 $1,600 $1,200 $720 $400 $1,680 $1,200 $16,240 $41.43

Total Support Cost

Man Months Man Days Category Designers Developers Testers Managers 1 5 Hours per day Total Hours Cost 0.5 2.5 $125 8 40 $1,200 1 5 $150 0.5 2.5 $175 Total $1,650

Assumptions
Test Planning, Documentation and Management activities are carried out in parallel to other main activities of design, development and testing

Resources
Designers Developers Testers 1 2 1

Others
Possible Critical Chain Delay in Development Possible Fixation Delay in Testing Working days in a month Ratio of calendar days 5% 5% 21 1.476190476

Project Plan - Waterfall

Phase Duration (days) Duration (months) Requirements/Design Phase 11.0 0 Month 16 Day Development Phase 11.0 0 Month 16 Day Testing Phase 5.3 0 Month 8 Day Total 27.3 1 Month 9 Day Slack 3.0 Grand Total 30.3 1 Month 14 Day

Iterative Plan
Iterations 1 2 3 4 5 Total Iteration Duration 1 (without Slacks) 100% 27.28 0% 0.00 0% 0.00 0% 0.00 0% 0.00 100%

Slacks
Initial Ramp-up Deployment for testing etc Code/Peer Reviews Shipment Packaging & Review Total Slack 0.5 0.5 1 1 3

Requirements/Design 11.0 0.0 0.0 0.0 0.0

Development Testing 11.0 5.3 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0