COCOMO IN A NUTSHELL

Step # 1 : Choose the COCOMO version There are three versions of COCOMO : Basic Intermediate Detailed Step # 2 : Choose the COCOMO mode There are three software development modes : (Explained Later) Organic Semidetached Embedded Step # 3 : Calculate the nominal estimate of Effort (Enom) in person-months(PM) Enom = a * (KLOC)b Product Type Organic Semidetached Embedded Multiplier(a) Basic 2.4 3.0 3.6 Exponent (b) Intermediate 3.2 3.0 2.8 1.05 1.12 1.2

Step # 4 : Calculate the nominal development time (Td) Organic : Td = 2.5 * (Enom)0.38 Semidetached : Td = 2.5 * (Enom)0.35 Organic : Td = 2.5 * (Enom)0.32 If we are using the basic model we have got the estimates and nothing more needs to be done. Step # 5 : Fine-tune the estimates by computing the Effort Adjustment Multipier (for Intermediate version only) The fifteen cost drivers are : Product Attributes RELY : Required Level Of Reliability DATA: Size of database used by the system CPLX : Complexity of software product Computer Attributes 1

TIME: Execution Time constraints STOR: Main storage constraints VIRT : Virtual Memory Volatility TURN : Computer Turnaround Time

Personnel Attributes ACAP: Analyst capability AEXP: Experience in the application area PCAP : Programmer capability VEXP : Experience with the host virtual machine LEXP : Experience with the programming language Project Attributes MODP: Effect of modern programming practices TOOL: Use of advanced software development tools SCED : Schedule constraints Next, categorize the cost drivers as low, very low, nominal, high, very high and extra high. Attributes Very Low Low Nominal High Very High 1.40 1.16 1.3 1.30 1.21 1.30 1.15 0.71 0.82 0.70 * * 0.82 0.83 1.10 * Extra High * * 1.65 1.66 1.56 * * * * * * * * * * 1.62

Product Related RELY 0.75 DATA * CPLX 0.70 Computer Related TIME * STOR * VIRT * TURN * Personnel Related ACAP 1.46 AEXP 1.29 PCAP 1.42 VEXP 1.21 LEXP 1.14 Project Related MODP 1.24 TOOL 1.24 SCED 1.23 The 16th cost driver : REQUIREMENT 0.91 VOLATILITY

0.88 0.94 0.85 * * 0.87 0.87 1.19 1.13 1.17 1.10 1.07 1.10 1.10 1.08 *

1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00

1.15 1.08 1.15 1.11 1.06 1.15 1.07 0.86 0.91 0.86 0.90 0.95 0.91 0.91 1.04 *

The product of the 16 values chosen will be the Effort Adjustment Multiplier of the nominal effort & time calculated for the Basic version above. Additionally, COCOMO also suggests phasewise distribution of estimated effort. For example, for a software of organic mode the prescribed distribution of effort in percentage terms is : Phase Product Design Detailed Design Coding & Unit Testing Integration TOTAL Small (2K) 16 26 42 16 100% Intermediate (8K) 16 25 40 19 100% Medium (32K) 16 24 38 22 100% Large (128 K) 16 23 36 25 100%

PARAMETERS FOR IDENTIFYING THE COCOMO MODE : Organic Mode Characteristics: Small product size (< 50 KLOC) Small, in-house development team Development team experienced in application area Relaxed(negotiable, informal) specifications on function & performance requirements. Minimal communication overhead Stable development environment Minimal schedule pressure Existing, proven technology used Some examples are engineering, scientific and business applications, inventory control system etc. Semi-detached Mode Characteristics: Size may range upto 300 KLOC Development team personnel is a mix of experienced and inexperienced in the application & development environment Mix of relaxed and rigid specifications Lies between the organic & embedded mode Moderate schedule pressure Examples are DBMS, simple command and control systems Embedded Mode Characteristics: Size may vary from 20 to 1000 KLOC Rigorous specifications Product must operate within time constraints on internal and external interface service, processing and interrupt service Product must meet rigid, formal quality standards Close coupling required among software, hardware and operators to meet function and performance requirements Extensive testing required Leading edge technology required Other system components developed concurrently with software Strong schedule pressure Examples are avionics software systems, operating systems, real-time systems. */*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/

FEATURE POINT ANALYSIS (for Scientific & Engineering-oriented software)

A 6th function, algorithms is introduced in addition to those in Function Point Analysis The weights are : Inputs Outputs 4 5

Inquiries 4

Files 4

Interfaces 7

Algorithms 3

As in FPA, multiply the number of each of the above with corresponding weights and calculate the total sum. This summation is the Unadjusted Feature Points. Next, compute the Feature Point Complexity Adjustment Factor, based on logical & data complexity. This is done by assigning Logical Complexity Value (LCV) & Data Complexity Value (DCV) as follows : LCV 1 2 3 4 5 DCV 1 2 3 4 5 Logical Complexity Status Simple algorithms & simple calculations Majority of simple algorithms & calculations Algorithms & calculations of average complexity Some difficult or complex algorithms & calculations Many difficult or complex algorithms & calculations Data Complexity Status Simple data with few variables and low complexity Numerous variables but simple data relationships Multiple files, fields and data interactions Complex file structures and data interactions Very complex file structures and data interactions

Now, sum up the values of the assigned LCV & DCV and estimate the adjustment multiplier from the table below :
LCV+DCV Adj. Mul. 2 0.6 3 0.7 4 0.8 5 0.9 6 1.0 7 1.1 8 1.2 9 1.3 10 1.4

Adjusted Feature Points = Unadjusted Feature Points * Adjustment Multiplier