User Manual COCOMO2

USC COCOMO II
Users manual
University of Southern California
COCOMO REFERENCE MANUAL
Chapter 1: Introduction
This manual is compatible with USC-COCOMO II.

2000 version 3.
Copyright Notice
This document is copyrighted, and all rights are
reserved by University of Southern California. This
document may not in whole, or in part, be copied,
photocopied, reproduced, translated, or reduced to any
electronic medium or machine readable from without
prior consent.
Copyright 1995-2003
All rights reserved
Warranty
This manual is provided as is without warranty of any
kind, either express or implied, including, but not
limited to the implied warranties of merchantability and
fitness for a particular purpose. Moreover, USC
reserves the right to revise this manual and to make
changes periodically without obligation to notify any
person or organization of such revision or changes.
Trademark Acknowledgement
USC has made every effort to supply trademark
information about company names, products and
services mentioned in this document. Trademarks
indicates below were derived from various sources.
UNIX is a registered trademark of AT&T Bell
laboratories
Motif is a trademark of Open Software Foundation, Inc.
FrameMaker and Frame Technology are registered
trademarks of Frame Technology Corporation.
Sun Microsystem and Sun Workstation are registered
trademarks, and OpenWindows, Sun-3, Sun-4, and
SPARCstation are trademarks, of Sun Microsystems,
Inc.
X Window System is a trademark of the Massachusetts
Institute of Technology.
MS Window 95, 98, 2000, NT, XP are a trademark of
Microsoft Corporation
Printed in the United States of America.
Acknowledgements
COCOMO 81, Version 1.0:
Principal Investigator Dr. Ellis Horowitz
Student Designers, Testers and programmers Alfredo
Arcilla, Joyce Balimbin, Gina Gaborno, Larry Klei,
Robert Kosai, Deseree Moon, Jason Pan, Thomas
Quayle, Isaiah Simmons, Scott Zechiel
COCOMO 81, Version 1.1:
Student Designers, Testers and programmers Ing-Jer
Huang
COCOMO 81, Version 10.0
Student Designers, Testers and programmers M.Susan
Lane, Ping Luo, Lorna Zorman
COCOMO 2.0, Version 2.0
Student Designers, Testers and programmers Wiryadi
Adidharma, Sen-Ho change, Shu-fen Cheng, Yu-Chuan
Lin, Steve K.Luk, Shawne Robison, Tuan Ton
COCOMO 2.0, Version 2.0.5
Student Designers, Testers and programmers Thomas
Majchrowski, Suppachai Sangtonkhamsuk, Lloyd
Manglapus
COCOMO II, 1997.2
Student Designers, Testers and programmers
Jongmoon Baik, Jungwon Park, James Chou, Dana
Flora-Adams, SangHyun, and Eunsook Bang
COCOMO II. 1998.0
Jongmoon Baik and CS655 students
COCOMO II, 2000.0
Jongmoon Baik and Keun Lee
COCOMO II, 2000.2
Student Designers, Testers and programmers Keun
Lee
COCOMO II, 2000.3
Student Designers, Testers and programmers Keun

Lee
Note This manual is sufficient for the X Windows,
MS Windows 95/98/2000/NT/XP, and Java versions of
USC COCOMO II. 2000.3 programs. Though there are
some user interface differences between these systems,
the core component of all versions is identical.
Some of the material used in this manual has been taken
from Software Engineering Economics, by Barry
Boehm, Prentice-Hall, with permission of the author.
Content
Chapter 1: Introduction 1
1.1 What is COCOMO? 1
1.1.1
Effort Estimation Equation
2
1.1.2
Schedule Estimation Equation
3
1.1.3
Scale Factors
3
1.1.4
Sizing methods 4
1.1.5
FP: Counting with Unadjusted Function Points
7
1.1.6
AAF: Adaptation Adjustment Factor 8
1.1.7
Effort Multipliers 8
1.2 Navigating COCOMO
9
1.3 Begin Using COCOMO
18
1.4 Running COCOMO: Windows, Sparc or Java 19
Chapter 2: File Menu
2.1 New 21
2.2 Project Load 22
2.3 Project Save 23
2.4 Project Save As
2.5 Model Load 25
2.6 Model Save 27
2.7 Model Save As
2.8 Make Report 29
2.9 Export
30
2.10 Save Screen 31
2.11 Print Screen 32
2.12 Print Preview 32
2.13 Print Setup 33
2.14 Exit
34
20
24
28
Chapter 5: Calibrate menu

5.1 File Load
51
5.2 File Save
51
5.3 File Save As 51
5.4 Project
53
5.5 Computer
54
50
Chapter 6: Phase Distribution

55
6.1 Waterfall
56
6.1.1 Project Phase Distribution
56
6.1.1.1 Overall Project Phase Distribution 56
6.1.1.2 Plans and Requirements Project Phase
Distribution
59
6.1.1.3 Programming Project Phase 59
6.1.1.4 Product Design Phase
60
6.1.1.5 Integration and Test Project Phase 61
6.2 MBASE
68
68
6.2.1.1 Overall Project Phase Distribution 69
6.2.1.2. Inception Project Phase Distribution 69
6.2.1.3 Elaboration Project Phase 71
6.2.1.4 Construction Design Phase
71
6.2.1.5 Transition Project Phase
73
6.2.2. Module Phase Distribution 73
6.2.2.1 Overall Module Phase Distribution 75
6.2.2.2 Inception Module Phase Distribution 76
6.2.2.3 Elaboration Module Phase Distribution 76
6.2.2.4 Construction Phase Distribution
78
6.2.2.5 Transition Module Phase Distribution 78
Chapter 7: Maintenance 79
7.1 Project maintenance 81
7.2 Module Maintenance 85
Chapter 3: Edit Menu 36

3.1 Add module 36
3.2 Clear All Module 36
3.3 Snapshot
37
3.4 Undo
39
3.5 Cut
39
3.6 Copy
40
3.7 Paste
40
Chapter 4: Parameters Menu
4.1 Product
42
4.2 Platform
42
4.3 personnel
43
4.4 Project
43
4.5 User Defined EAF
45
4.6 Early Design
46
4.7 Scale Factor
46
4.8 Equation
47
4.9 Person Month
49
4.10 Function Point
49
41
C h a p t e r 1 : Introduction
1.1
What is COCOMO?
COCOMO (COnstructive COst MOdel) is a screen-oriented, interactive software package that assists in
budgetary planning and schedule estimation of a software development project. Through the flexibility of COCOMO, a
software project manager (or team leader) can develop a model (or multiple models) of projects in order to identify
potential problems in resources, personnel, budgets, and schedules both before and while the potential software package
is being developed.
The COCOMO software package is based upon the software cost and schedule estimation model: COnstructive
COst MOdel version II (COCOMOII). This is the newly revised version of the original COnstructive COst MOdel
(COCOMO) first published by Dr. Barry Boehm in his book Software Engineering Economics, Prentice-Hall (1981),
and Ada COCOMO (1989) predecessors. The current model is described in [Boehm et al. 1995]
The primary objectives of the COCOMOII.1998 effort are:
To develop a software cost and schedule estimation model tuned to the life cycle practices of the 1990's and
2000's.
To develop software cost database and tool support capabilities for continuous model improvement.
To provide a quantitative analytic framework, and set of tools and techniques for evaluating the effects of
software technology improvements on software life cycle costs and schedules.
The full COCOMOII model includes three stages. Stage 1 supports estimation of prototyping or applications
composition efforts. Stage 2 supports estimation in the Early Design stage of a project, when less is known about the
projects cost drivers. Stage 3 supports estimation in the Post-Architecture stage of a project.
This version of USC COCOMOII implements stage 3 formulas to estimate the effort, schedule, and cost
required to develop a software product. It also provides the breakdown of effort and schedule into software life-cycle
phases and activities from the original COCOMO manual. These are still reasonably valid for waterfall model software
projects, but need to be interpreted for non-waterfall projects.
1.1.1
Effort Estimation Equation

(EQ 1-1)
PM = A x Size E x i =1 EM i + PM Auto
n
, where E = B + 0.01 x
SFj and PM Auto =

j=1
Size = (1 +
Adapted SLOC x (AT
100
ATPROD
REVL
) (New KSLOC + Equivalent KSLOC)
100
Equivalent KSLOC = Adapted KSLOC AAM (1 - AT
100
AA + AAF (1 + [0.02 SU UNFM])

, for AAF 50
100
AA + AAF (SU UNFM)
=
, for AAF > 50
100
AAM =
AAF = (0.4 DM) + (0.3 CM) + (0.3 IM)

Symbol
A
AT
ATPROD
B
E
EM
PM
PMAuto
SF
SLOC
AA
CM
DM
IM
KSLOC
REVL
SU
UNFM
Description
Constant, currently calibrated as 2.94
Percentage of components that are automatically translated
Automatic translation productivity
Scaling base-exponent for Effort that can be calibrated
Scaling exponent for Effort
Effort Multipliers: RELY, DATA, CPLX, RUSE, DOCU, TIME, STOR,
PVOL, ACAP, PCAP, PCON, APEX, PLEX, LTEX, TOOL, SITE, SCED
Person Months effort from developing new and adapted code
Person Months effort from automatic translation activities
Scale Factors: PREC, FLEX, RESL, TEAM, PMAT
Source Lines of Code
Percentage of Assessment and Assimilation
Percent Code Modified
Percent Design Modified
Percent of Integration Required for the Adapted Software
Thousands of Source Lines of Code
Percentage of Requirements Evolution and Volatility
Software understanding (zero if DM = 0 and CM = 0)
Programmer Unfamiliarity with software
1.1.2 Schedule Estimation Equation

Determine time to develop (TDEV) with an estimated effort, PM, that excludes the effect of the SCED effort multiplier:
(EQ 1-2)
SCED%
100
F = D + 0.2 [E - B]
TDEV = [C x (PM NS ) F ] x
Symbol
B
C
D
E
F
PMNS
SCED%
TDEV
Description
The scaling base-exponent for the effort equation
Schedule coefficient that can be calibrated
Scaling base-exponent for Schedule that can be calibrated
The scaling exponent for the effort equation
Scaling exponent for Schedule
Person Months estimated without the SCED cost driver (Nominal Schedule)
and without PMAuto
Required Percentage of Schedule Compression relative to Nominal Schedule
Time to Develop in calendar months
1.1.3 Scale Factors

Equation 1-2 defines the exponent, B, used in Equation 1-1. Table 1.1 provides the rating levels for the COCOMOII
scale drivers. The selection of scale drivers is based on the rationale that they are a significant source of exponential
variation on a projects effort or productivity variation. Each scale driver has a range of rating levels, from Very Low to
Extra High. Each rating level has a weight, W, and the specific value of the weight is called a scale factor. A project's
scale factors, Wi, are summed across all of the factors, and used to determine a scale exponent, B, via the following
formula:
(EQ 1-3)
For example, if scale factors with an Extra High rating are each assigned a weight of (0), then a 100 KSLOC project with
Extra High ratings for all factors will have SFj = 0, B = 1.01, and a relative effort E = 1001.01 = 105 PM. If scale factors
with Very Low rating are each assigned a weight of (5), then a project with Very Low (5) ratings for all factors will have
SFj = 5, B = 1.26, and a relative effort E = 331 PM. This represents a large variation, but the increase involved in a oneunit change in one of the factors is only about 4.7%.
Scale Factors Very Low

(SFj)
PREC
thoroughly
unprecedented
FLEX
rigorous
RESL1
little (20%)
Low
Nominal
High
Very High
Extra High
largely
unprecedented
occasional
relaxation
some (40%)
Somewhat
unprecedented
some
relaxation
often (60%)
generally
familiar
general
conformity
Generally
(75%)
largely
cooperative
largely
familiar
some
conformity
mostly (90%)
thoroughly
familiar
general goals
TEAM
very difficult some difficult Basically

highly
interactions
interactions
cooperative
cooperative
interactions
PMAT
Weighted average of Yes answers to CMM Maturity Questionnaire
Table 1.1: Scale Factors for COCOMO.II Early Design and Post-Architecture Models
full (100%)
seamless
interactions
1.1.4 Sizing Methods

SLOC: Lines of Code Counting Rules
In COCOMOII, the logical source statement has been chosen as the standard line of code. Defining a line of code is
difficult due to conceptual differences involved in accounting for executable statements and data declarations in different
languages. The goal is to measure the amount of intellectual work put into program development, but difficulties arise
when trying to define consistent measures across different languages. Breakage due to change of requirements also
complicates sizing. To minimize these problems, the Software Engineering Institute (SEI) definition checklist for a
logical source statement is used in defining the line of code measure. The Software Engineering Institute (SEI) has
developed this checklist as part of a system of definition checklists, report forms and supplemental forms to support
measurement definitions [Park 1992] [Goethert et al. 1992].
Figure 1-1 shows a portion of the definition checklist as it is being applied to support the development of the
COCOMOII model. Each checkmark in the Includes column identifies a particular statement type or attribute included
in the definition, and vice-versa for the excludes. Other sections in the definition clarify statement attributes for usage,
delivery, functionality, replications and development status. There are also clarifications for language specific statements
for ADA, C, C++, CMS-2, COBOL, FORTRAN, JOVIAL and Pascal.
. % significant module interfaces specified,% significant risks eliminated.
Some changes were made to the line-of-code definition that departs from the default definition provided in [Park 1992].
These changes eliminate categories of software, which are generally small sources of project effort. Not included in the
definition are commercial-off-the-shelf software (COTS), government-furnished software (GFS), other products,
language support libraries and operating systems, or other commercial libraries. Code generated with source code
generators is not included though measurements will be taken with and without generated code to support analysis.
The COCOMOII line-of-code definition can be calculated in several ways. One way is to use the software program,
Amadeus[Amadeus 1994] [Selby et al. 1991]. Another software program is code count.
Figure 1-1 Definition Checklist for Source Statements Counts
1.1.5 FP: Counting with Unadjusted Function Points

The function point cost estimation approach is based on the amount of functionality in a software project and a set of
individual project factors [Behrens 1983][Kunkler 1985][IFPUG 1994]. Function points are useful estimators since they
are based on information that is available early in the project life cycle. A brief summary of function points and their
calculation in COCOMOII is as follows.
Function points measure a software project by quantifying the information processing functionality associated with
major external data input, output, or file types. Five user function types should be identified as defined in the Table2.
External Input (Inputs) Count each unique user data or user control input type that (i)
enters the external boundary of the software system being
measured and (ii) adds or changes data in a logical internal file.
External Output
Count each unique user data or control output type that leaves the
(Outputs)
external boundary of the software system being measured.
Internal Logical File
Count each major logical group of user data or control information
(Files)
in the software system as a logical internal file type. Include each
logical file (e.g., each logical group of data) that is generated, used,
or maintained by the software system.
External Interface
Files passed or shared between software systems should be counted
Files (Interfaces)
as external interface file types within each system.
External Inquiry
Count each unique input-output combination, where an input
(Queries)
causes and generates an immediate output, as an external inquiry
type.
Table 2: User Function Types
Each instance of these function types is then classified by complexity level. The complexity levels determine a set of
weights, which are applied to their corresponding function counts to determine the Unadjusted Function Points quantity.
This is the Function Point sizing metric used by COCOMII. The usual Function Point procedure involves assessing the
degree of influence (DI) of fourteen application characteristics on the software project determined according to a rating
scale of 0.0 to 0.05 for each characteristic. The 14 ratings are added together, and added to a base level of 0.65 to
produce a general characteristics adjustment factor that ranges from 0.65 to 1.35.
Each of these fourteen characteristics, such as distributed functions, performance, and reusability, thus have a maximum
of 5% contribution to estimated effort. This is inconsistent with COCOMO experience; thus COCOMO.II uses
Unadjusted Function Points for sizing, and applies its reuse factors, cost driver effort multipliers, and exponent scale
factors to this sizing quantity.
1.1.6 AAF: Adaptation Adjustment Factors

Adaptation of Existing Code
COCOMO is not only capable of estimating the cost and schedule for a development started from "scratch", but
it is also able to estimate the cost and schedule for products that are built upon already existing code. Adaptation
considerations have also been incorporated into COCOMO, where an estimate for KSLOC will be calculated. This value
will be substituted in place of the SLOC found in the equations already discussed. This adaptation of code utilizes an
additional set of equations that are used to calculate the final count on source instructions and related cost and schedule.
These equations use the following values as components:
Adapted Source Lines of Code (ASLOC). The number of source lines of code adapted from existing software
used in developing the new product.
Percent of Design Modification (DM). The percentage of the adapted softwares design that received
modification to fulfill the objectives and environment of the new product.
Percent of Code Modification (CM). The percentage of the adapted softwares code that receives modification
to fulfill the objectives and environment of the new product.
Percent of Integration Required for Modified Software (IM). The percentage of effort needed for integrating
and testing of the adapted software in order to combine it into the new product.
Percentage of reuse effort due to Software Understanding (SU).
Percentage of reuse effort due to Assessment and Assimilation (AA).
Programmer Unfamiliarity with Software (UNFM)
These components are brought together in Figure 1-6. The AAF is the adaptation adjustment factor. The AAF is the
calculated degree to which the adapted software will affect overall development.
1.1.7 Effort Multipliers

There are a number of contributing factors to a projects delivery time and effort. Development productivity
was found to be affected by additional factors that were found to fall under the headings: product attributes, platform
attributes, personnel attributes, and project attributes.
Product attributes refer to the constraints and requirements placed upon the project to be developed. These
included
Required software reliability (RELY)

Database size (DATA)
Documentation match to life-cycle needs (DOCU)
Product complexity (CPLX)
Required Reusability (RUSE)
Platform attributes refer to the limitations placed upon development effort by the hardware and operating
system being used to run the project. These limitations are listed below.
Execution time constraint (TIME)

Main storage constraint (STOR)
Platform volatility (PVOL)
Personnel attributes refer to the level of skills that are possessed by the personnel. The skills in question are
general professional ability, programming ability, experience with the development environment and familiarity with the
projects domain. These skills are characterized below.
Analyst capabilities (ACAP)

Applications experience (AEXP)
Programmer capabilities (PCAP)
Platform experience (PEXP)
Programming language experience (LEXP)
Personnel Continuity (PCON)
Project attributes refer to the constraints and conditions under which project development takes place. The
issues that affect development are:
Use of software tools (TOOL)

Multisite Development (SITE)
These 16 factors are incorporated into calculating an estimated effort and schedule. Each of the factors has
associated with it up to six ratings. These ratings are very low, low, nominal, high, very high, and extra high. Each
rating has a corresponding real number based upon the factor and the degree to which the factor can influence
productivity. A rating less than 1 denotes a factor that can decrease the schedule and effort. A rating greater than 1
denotes a factor that extends the schedule or effort. Lastly, a rating equal to 1 does not extend nor decrease the schedule
and effort (this rating is called nominal).
These 16 factors (or effort multipliers) are incorporated into the schedule and effort estimation formulas by
multiplying them together (see Figure 1-7 for the COCOMO dialog box). The numerical value of the ith adjustment
factor (there are 16 of them) is called EMi and their product is called the adjustment factor or EAF. The actual effort,
PMtotal is the product of the nominal effort times the EAF.
In addition to the 16 EAF factors there are two user defined factors named USR1 and USR2. Their initial values
are all set to 1. They may be redefined by using the Parameters-User Defined EAF menu item.
A final effort multiplier, Required Development Schedule (SCED) is treated separately as it operates at the
overall project level rather than potentially varying from module to module.
FIGURE 1-2
1.2
Estimate Development Effort
Navigating COCOMO
This software is a stand-alone software system intended for a single user. The software is user interactive in
that it attempts to interface well with a user's needs, using extensive mouse interaction wherever possible.
On the screen in Figure 1-3 is the CLEF (Component Level Estimation Form). This is where all of the entered
information will be displayed. The top of the screen shows all of the subfunctions which the user may call. The choices
appear in pop down menus according to the major headings of Project, Model, and Phase.
In order to efficiently use COCOMO, you must become familiar with the Component Level Estimating Form
(CLEF). The different sections that are to be discussed have been given a corresponding number. These sections are
given a descriptive label as a point of reference as well as a summary of their contents and functions.
The sections found in Figure 1-3 and their descriptions are as follows:
FIGURE 1-3
COCOMO CLEF
1
2
13
14
15
16
6
7
17
18
8
9
10
19
20
21
22
11
12
1. Main Menu bar - This area contains the menu selection of the main functions of COCOMO. These
selections are File, View, Edit, Parameters, Calibrate, Phase Distribution and Help. File, View, Edit,
Parameters, Calibrate, and Phase Distribution are discussed in chapters 2, 3, 4, 5, and 6 respectively. Help is the
selection used to receive on-line assistance with the available functions.
10
2. Tool bar - This area contains image buttons like other windows applications for New Project, Open Project,
Save Project, Delete Module, Copy & Paste, Insert clipboard content, Insert a module, and About functions.
3. Project Name - This editable field displays the name of the currently displayed project. To edit the name
click twice upon this field and proceed to edit name. Upon completion of editing press the "Return" key. The
Default name of a new project is "<sample>".
4. Project Note - This button displays the Project Note Dialog Box as shown in Figure 1-4. In this box, user can
write brief description of the project.
FIGURE 1-4
Project Note
5. X - This column is reserved for identifying a module. Pressing upon this field for a given module will mark
the desired module. Marking is denoted by an x that appears in this column. Only one module can be marked
at a time. Modules are marked in order to perform module deletion, cutting, copying or pasting.
6. Module Name Column - This column is used to house the name of each module located in the Module Area.
The module name can be changed by clicking twice on the desired module name box and entering the changes
into the module name field. Upon completion of editing press "Return".
7. Module Size (SLOC) Column - This column is used to house the SLOC of each module located in the
Module Area. The value for SLOC can be computed in one of three ways. One, the value can be entered
directly in the SLOC field as shown in Figure 1-5. Two, by using the function point model as shown in Figure
1-6. Three, by using Adaptation Adjustment Factor as shown in Figure 1-7. Upon completion click on OK.
There is a limit to the range of input. The inputted value for SLOC must be within the range 0 - 9,999,999.
Note - COCOMO is not calibrated for Total SLOC < 2000.
11
FIGURE 1-5
12
SLOC Dialog Box - Source Lines of Code (SLOC)
FIGURE 1-6
SLOC Dialog Box - Function Points (FP)
There are two Ratio types, Jones and David. Jones is a set of the function point multipliers provided by Caper
Jones. David is a set of the function point multipliers provided by David Consulting Groups. Select on of two types
to estimate the SLOC using function point.
Also there are two methods to estimate SLOC using function point, Using Table and Input Calculated Function
Point.
13
FIGURE 1-7
14
SLOC Dialog Box - Adaptation Adjustment Factor (AAF)
7. Labor Rate Column - This column contains the amount of money at which a developer working on a particular
module would be paid per month. The labor rate can be edited by clicking on the corresponding Labor Rate box and
entering the new value via the edit area. The range on labor rate is between $0 and $99,999.
8. Effort Adjustment Factor (EAF) Column - This column displays the product of the cost drivers for each specific
module. By clicking on this field a dialog box appears (see Figure 1-7). This box displays all of the cost drivers, inter
cost drivers and their current ratings. The cost drivers are divided into the groupings: Product, Platform, Personnel and
Project. The inter cost drivers are rated as 0%, 25%, 50%, and 75 %. The ratings for each multiplier can be changed by
cycling through the available ratings until the desired rating is displayed. As the cost driver ratings are changed the total
product of the cost drivers is displayed in the upper right hand corner of the dialog box along with the module name. The
final rating of a cost driver is calculated using this formula for the interpolation.
Final rating = (Next cost driver rating - Current cost driver rating) * Current inter cost driver / 100
9. Totals Area - This area houses the calculated results of all of the modules combined. Within this area is the total
SLOC count for the module, the total nominal effort (PM), the total nominal productivity (SLOC/PM), the total
estimated effort (EST PM), the total estimated productivity (Prod), the total estimated project cost, the estimated cost per
instruction, the total estimated FSWP and the total estimated schedule for project completion (see each individual
column for more information). The latter six quantities have not only a most likely estimate but also an optimistic
estimate (no less than this, 90% of the time) and a pessimistic estimate (no greater than this, 90% of the time).
10. Status bar - This window displays a short definition of the column headings clicked upon and also displays a short
description of the result of the last function initiated by the user.
11. Schedule Button - This button displays the Schedule Dialog Box as shown in Figure 1-8.
12. Scale Factor Button - This button displays the Scale Factor Dialog Box as shown in Figure 1-9.
13. Risk Column - This column contains the Total risk level for each specific module. By clicking on this field a dialog
box appears (see Figure 1-10). This box displays all of the risk levels for the chosen module. The total risk of a module
is computed as:
total_risk=schedule_risk+product_risk+personnel_risk+process_risk+platform_risk+reuse_risk;
total risk of a module=total_risk/373.*100.;
For the definitions of schedule risk, product risk, platform risk, personnel risk, process risk, and reuse risk, see [Madachy
1997].
14. Full-time SoftWare Personnel (FSWP) Column - This column houses the calculated most likely estimate for the
number of full-time developers that would be needed to complete a module in the estimated development time.
15. Instruction Cost Column - This column contains the calculated most likely cost per instruction. This number is
calculated from Cost/SLOC in each module.
15
FIGURE 1-7
EAF Dialog Box
FIGURE 1-8
Schedule Dialog Box
16
16. Cost Column - This column contains the calculated most likely estimate of the development cost for a particular
module.
17. Productivity (PROD) Column - This column contains the calculated result of the modules individual SLOC
divided by the modules most likely effort estimate.
18. Estimated Person-Month (EST PM) Column - This column holds the modules most likely effort estimate
obtained from multiplying Effort Adjustment Factor (EAF) by Nominal Person Month (NOM PM).
19. Nominal Person-Month (NOM PM) Column - This column holds the modules most likely effort estimate without
incorporating the Effort Adjustment Factors (EAF).
FIGURE 1-9
Scale Factor Dialog Box
17
FIGURE 1-10
1.3
Risk Level Dialog Box
Begin Using COCOMO
To begin entering a new module, either click on the "Add Module" button on the Tool bar or on the pulldown menu
item(Edit|Add Module). At this point, a new module will appear in the CLEF with all values set to their respective
defaults. Double click upon the module name field in order to give the new module a name. Upon typing the module
name press "Return.". A value for SLOC and Labor rate may also be given by clicking on the respective field and
editing appropriately (see Figure 1-11).
FIGURE 1-11
18
Create Sample Module and give values to SLOC and Labor Rate
NOTE - In order to change any of the editable fields, just click on the desired field twice and begin editing the field.
Upon completing editing, either hit the "Return" key, or click on OK. All of the final results can be found at the bottom
of the CLEF in the Totals area (see Figure 1-12).
FIGURE 1-12
1.4
Totals area after calculations have been completed
Running COCOMO: Windows, Sparc or Java
Currently, there are three implementations of COCOMOII: a Windows 95/NT version, a Sun Microsystems Sparcstation
version, and a Java version.
To download any these versions, you should enter this in a web browser:
http://sunset.usc.edu/COCOMOII/cocomo.html
and scroll down to the section labeled COCOMOII Downloads(Software and Documentation)
or
ftp://ftp.usc.edu/pub/soft_engineering/COCOMOII/ where you will see 7 files:
c98sunos.tar.gz, c98windows.zip, c98java.tar.gz, usersman.ps, usersman.pdf, modelman.ps, modelman.pdf
To run java cocomo(Netscape Navigator3.0 or Microsoft Internet Explorer3.0 or higher), you should visit:
http://sunset.usc.edu/j_cocomo/cocomo.html
19
Chapter 2: File Menu

The COCOMO file types include: project file, model file, report file, calibration file, and csv file. The first three are
discussed here. The others are discussed in later chapters.
The project file in COCOMO stores a projects data, which include project name, project scale factors, project schedule
constraint, module name, SLOC, labor rate, effort adjustment factors (EAF), and COCOMO related calculation results.
The COCOMO system gives all project files an ".est" extension.
Regarding the model file, as we mentioned in chapter one, COCOMO incorporates 17 predictor factors, or cost driver
attributes, which are grouped into four categories: software product attributes, platform attributes, personnel attributes,
and project attributes. Each of these cost drivers attributes determines a multiplying factor, which estimates the effect of
the attribute in software development effort. There are also two user defined EAF factors plus the project-level required
development schedule EAF factor. Besides these cost drivers, COCOMO also has scale factors. These multiplying
factors and effort estimating equations constitute the model of a project. As we said previously, COCOMO has assigned
default values and equations for the annually calibrated default model. Each time a COCOMO project is created, its
effort estimate is based on the default model. COCOMO provides flexibility in changing the values of multiplying
factors and effort estimating equation, or schedule estimating equation. An adjusted model can no longer be considered
default values, and therefore it will be lost if COCOMO is exited without saving it in a model file. Upon saving this
model file, these altered values can be applied to another project by loading the saved model file. The COCOMO
system gives all model files a ".mod" extension.
The report file is a summary report of the COCOMO project. This report contains all entered and calculated values of a
project. These files are given a ".rpt" extension.
The File menu option will enable you to create, retrieve, save, or print COCOMO files.
To select the File menu and its options, click on File with the mouse. The File menu will appear as Figure 2-1.
20
FIGURE 2-1
File Menu
2.1 New
The New option creates a new project file in the COCOMO working window, replacing any previous project file in the
working window.
To Create a New Working File
1. Choose New from the File menu with mouse.
The working window will now be clear; the previous project file in the working window has been removed.
Note: New can be selected anytime; however, if the previous project file or model file has been modified, a warning
dialog box will appear and requests confirmation. (as seen in Figure 2-2)
21
FIGURE 2-2
Warning Dialog Box
2. If the modifications on the previous file are not to be saved, choose Yes, otherwise choose No. If the No is selected, a
Save File dialog will appear. (See Save Project and Save Model respectively)
2.2
Load Project
The Load Project option is used to retrieve a project file as well as loading it on the working window.
To Retrieve or Load a Project File
1. Choose Load Project from the File menu with the mouse.
2. If a previous project file has been modified in the working window, the dialog box as in Figure 2-3 will appear.
FIGURE 2-3
Warning Dialog Box
3. If the previous project file is to be saved, choose Yes, then a Save File dialog box will appear. (See Save Project). If
the modified file is not to be saved, choose No.
4. The Load Project dialog box will appear as seen in Figure 2-4.
22
FIGURE 2-4
Load Project Dialog Box
The file name of a COCOMO project has a default format with ".est" as an extension. With this window, the desired
project file can be selected from the Files scroll list for loading. If the desired project file does not exist in the scroll list,
it is necessary to choose an appropriate directory.
5. Choose desired directory for file loading
6. When the desired file is shown on the Files list, click it, and click the "OK" button to initiate project loading.
7. After a project file is loaded, its file name will be displayed on the PROJECT FILE field at upper left corner on the
working window, and all modules and related items will be displayed in the CLEF area. If the number of modules is
beyond the window scope, the scroll bar can be used to look at all items.
2.3
Save Project
The Save Project option is used to store the results of the current COCOMO project as a file with ".est" extension.
To Store the Results of Current Project
23
1. Choose Save Project from the File menu with the mouse. If the current project is loaded from a previously stored
project file, the Save Project will overwrite the same project file with the current project.
2. If the current project is a new one, i.e., being created by the New command, the Project Save dialog box will appear,
as seen in Figure 2-5.
FIGURE 2-5
Save Project Dialog Box
3. Look at the Files scroll window. If the file saving is to update (overwrite) a existing project file, the desired filename
should be found in the Files scroll list. If the filename can not be found from current list, change the directory from the
Directories scroll list until the desired filename is being shown. When the desired filename is on the list, click it.
4. If the file saving is to store a new project file, choose the desired directory, then type in a new filename.
5. After the desired filename is selected or inputted, click the OK button to initiate project saving.
2.4
Save As Project
The Save As Project option is to store the current project as a COCOMO project file, which has a file name different
from current file.
To Store Current Project With different File Name
1. Choose Save As Project from the File menu with the mouse.
24
2. The Save Project dialog box will appear, as seen in Figure 2-6.
FIGURE 2-6
Save Project Dialog Box
3. Look at the Files scroll window. If the file saving is to update (overwrite) a existing project file, the desired filename
4. If the file saving is to store a new project file, choose the desired directory, then type in a new filename in the
SELECTION box.
5. After the desired filename is selected or inputted, click the OK button to initiate project saving. After a project file is
saved, the project file name will be displayed on the PROJECT FILE field at the upper left corner of the working
window.
2.5
Load Model
The Load Model command is used when a specific model, in which the values of multiplying factors and scale factors
are different from the COCOMO default model, is to be applied to the current project.
The Load Model option is used to retrieve a model file as well as loading it for the current project.
To Retrieve or Load a Model File
25
1. Choose Load Model from the File menu.

2. If a previous model has been modified in the current project, the following dialog box will appear.
FIGURE 2-7
Warning Dialog Box
3. If the previous model file is to be saved, choose Yes, then a Save Model dialog box will appear. (See Save Model). If
the modified model is not to be saved, choose No.
4. The Load Model dialog box will appear as seen in Figure 2-8.
FIGURE 2-8
26
Load Model Dialog Box
The file name of a COCOMO model has a default format with ".mod" as an extension. With this window, the desired
model file can be selected from the Files scroll list for loading. If the desired model file does not exist in the scroll list,
look for it in the other directories.
5. Choose desired directory for file loading
6. When the desired file is shown on the Files list, click it, and click the "OK" button to initiate model loading.
7. After a model file is loaded, its file name will be displayed on the MODEL FILE field at upper left corner on the
working window, and the related costs of current project will be recalculated and shown on the working window.
2.6
Save Model
The Save Model option is used to store the results of the current COCOMO model as a file with ".mod" extension.
To Store the Results of Current Model
1. Choose Save Model from the File menu. If the current model is loaded from a previously stored model file, the Save
Model will overwrite the same model file with the current model.
2. If the current model is a new one, the Save Model dialog box will appear, as seen in Figure 2-9.
FIGURE 2-9
Save Model Dialog Box
3. Look at the Files scroll window. If the file saving is to update (overwrite) a existing model file, the
desired filename should be found in the Files scroll list. If the filename can not be found from current list, change the
27
directory from the Directories scroll list until the desired filename is being shown. When the desired filename is on the
list, click it.
4. If the file saving is to store a new model file, choose the desired directory, then type in the filename.
5. After the desired filename is selected or inputted, click the OK button to initiate model saving.
2.7
Save As Model
The Save As Model option is to store the current model as a COCOMO model file, which has a file name different from
current model.
To Store Current Model With different File Name
1. Choose Save As Model from the File menu.
2. The Save Model dialog box will appear, as seen in Figure 2-10.
FIGURE 2-10
28
Save As Model Dialog Box
3. Look at the Files scroll window. If the file saving is to update (overwrite) a existing model file, the desired filename
4. If the file saving is to store a new model file, choose the desired directory, then type in the filename in the
SELECTION box.
5. After the desired filename is selected or inputted, click the OK button to initiate model saving. After a model file is
saved, the project file name will be displayed on the MODEL FILE field at the upper left corner of the working window.
2.8
Make Report
The Make Report option creates a COCOMO report in the form of a text file for printing.
To Create Project Report

1. Choose Make Report from the File menu.
2. The Make Report dialog box will appear, as seen in Figure 2-11.
FIGURE 2-11
Make Report Dialog Box
3. Look at the Files scroll window. If the file saving is to update (overwrite) a existing report file, the desired filename
Directories scroll list until the desired filename is shown. When the desired filename is on the list, click it.
29
4. If the file saving is to store a new report file, choose the desired directory, then type in the filename.
5. Choose desired directory for file saving: Look at the filter input box. The path found in this box represents the
directory where the report file is going to be saved. This path will be changed after each directory change. To change
the directory, click the appropriate directory choice from the Directories scroll list, then click the "Filter" button.
6. After the desired filename is selected or inputted, click the OK button to initiate report file saving.
7. To print a COCOMO project report, execute the local commands for your system in order to send the file for printing.
2.9
Export
The Export option lets you select a directory to write files that can be imported into Excel.
To Export
1. Choose Export from the File menu.
2. The Export dialog box will appear, as seen in Figure 2-12.
Figure 2-12
File Export Dialog Box
3. When you click on OK, a dialog box appears if Main.csv and Phases.csv already exist, as shown in Figure 2-13.
4. If Yes is selected, COCOMO saves two files(main.csv and phase.csv) in the chosen directory.
If No is selected, these files will not be replaced.
30
Figure 2-13
2.10
Subsequent File Export Dialog Box
Save Screens
The Save Screens option allows the user to save the image of any Cocomo window.
To Save Screens
1. Choose Save Screens from the File menu.
2. The Save Screens dialog box will appear, as seen in Figure 2-14.
3. Follow the directions on the dialog box.
Figure 2-14
Save Screens Dialog Box
31
2.11
Print Screen
The Print Screen option prints the screen of the main Cocomo window.
To Print Screen
1. Choose Print Screen from the File menu.
2. The Print Screen dialog box will appear, as seen in Figure 2-15.
Figure 2-15
Print Screen Dialog Box
3. The Name of the printer can be selected from the dropdown list. Alternatively, you can print to a file by clicking on
the Print to file checkbox.
4. Properties of the printer can be set by clicking on the Properties button.
5. The Print range can be All or Pages (e.g. from 1 to 3).
6. The Number of copies can be selected by clicking the up and down arrows, or by typing a number directly.
7. Select OK when finished to print or select Cancel to not print.
2.12
Print Preview
The Print Preview option displays that which will appear when printed, if Print Screen is selected from the File menu.
To Preview what is to be printed
32
1. Choose Print Preview from the File menu.

2. The Print Preview dialog box will appear, as seen in Figure 2-16.
Figure 2-16
3.
4.
5.
6.
Print Preview Dialog Box
Select the Print button to print.

The Next Page button to advance to the next Page.
The Zoom In button zooms in, and the Zoom Out button becomes enabled so that the user can zoom out.
The Close button closes the Print Preview dialog.
2.12
Print Setup
The Print Setup option allows the user to set up printing.

To set up Printing
1. Choose Print Setup from the File menu.
33
2. The Print Setup dialog box will appear, as seen in Figure 2-17.
Figure 2-17
3.
4.
5.
6.
7.
Print Setup Dialog Box
The Name of the printer can be selected from the dropdown list.
Properties of the printer can be set by clicking on the Properties button.
The Size and Source of the paper can be selected from the dropdown lists.
The Network button can be selected to connect to a printer on a network.
Select OK when finished to print or select Cancel to not print.
2.13
Exit
The Exit option leaves the COCOMO system.

To Exit COCOMO
1. Choose Exit from the File menu with the mouse.
2. This causes your system to terminate the cocomo program.
34
35
Chapter 3: Edit Menu

The Edit Menu option supplies several useful commands, which will enable you to establish a project more conveniently.
To select the Edit menu and its options, click on Edit with the mouse, then the Edit menu will appear as Figure 3-1.
FIGURE 3-1
3.1
Edit Menu
Add Module
The Add Module option adds a new module to the project that is currently being worked upon by the user. This Add
Module function can be done by pressing the Add Module button in the Tool bar area.
3.2
Clear All Module
The Clear All option erases all modules of the current project on the working window.
To Erase All Modules of Current Project
36
1. Choose Clear from the Edit menu.

During the execution of the Clear command, if some changes have occurred on the currently viewed project and have not
been saved, the warning dialog box will appear as Figure 3.2.
2. If you really want to clear, click Yes. If not, click No.
3. After Clear, all modules of current project will disappear.
FIGURE 3-2
3.3
Warning Dialog Box
Snapshot
The Snapshot option enables users to compare the effort estimation change for a project so that he/she can decide to
apply the change or not. This function makes COCOMO more convenient and powerful for software project decision
analyses.
The Snapshot command stores the current set of modules, effort adjustment factors and all other data associated with a
project. At a later time this data can be restored.
To Compare the Overall Change of a Project
1.
Choose Snapshot from the Edit menu. The Snapshot dialog box will initially appear as Figure 3-3.
37
FIGURE 3-3
Snapshot Dialog Box-1
In the dialog box, the lower section represents the current results for the project. The upper section is previously
snapped results. The current project can be snapped by clicking upon the Snap button. After completing this action the
upper and lower section of the Snapshot window will contain identical information. At this point changes can be made
to the current project values after clicking upon the Done button.
2. Upon completing the modification of the project values, a comparison can be made between the previously snapped
project and the modified project by clicking again upon the Snapshot option in the Edit menu.
3. Now the values in the upper part of the window will likely be different from the current values, in the lower part. To
restore the upper values, click on Revert. The two sets of values are interchanged.
38
FIGURE 3-4
Snapshot Dialog Box-2
4. When finished, click the Done button.
3.4
Undo
The Undo option retracts the previous cut or paste done on a module.
To Retract Previous Cut/Paste for a Module
1. Choose Undo from the Edit menu with the mouse.
2. The changed module will go back to its previous status.
3.5
Cut
The Cut option copies a module into the cut buffer and removes it from the current project. The cut module can be used
for Paste.
To Cut a Module and Remove It From the CLEF
1. Check the module which is to be cut. The Check boxes for modules are located in the leftmost column of the CLEF
area. Place the mouse in the box just to the left of the module name, and click.
39
2. Choose Cut from the Edit menu with the mouse.

3. The cut module disappears.
3.6
Copy
The Copy option copies a module. The copied module can be used for Paste.
To Copy a Module
1. Check the module which is to be copied. The Check boxes for modules are located in the leftmost column of the
CLEF area.
2. Choose Copy from the Edit menu with the mouse.
3. The cross sign in the check box disappears.
3.7
Paste
The Paste option pastes a previously copied or cut module in the CLEF.
To Paste a Previously Copied or Cut Module
1. Check the module above which the previously copied or cut module is to be pasted. The Check boxes for modules are
located in the leftmost column of CLEF area.
2. Choose Paste from the Edit menu with the mouse.
3. The pasted module appears at the checked position, and the modules lower than it were pushed one row down.
4. If there is no module checked, the Paste will attach the previously copied or cut module at the end.
40
C h a p t e r 4 : Parameters Menu
The Parameters menu option will enable you to look at, or change the values of effort adjustment factors, scale factors
and effort/schedule estimating equations factors for the current project.
To choose the Parameters menu and its options, click on Parameters with the mouse. The Parameters menu will appear
as Figure 4-1.
FIGURE 4-1
Parameters Menu
Post Architecture
There are five sub options in Post Architecture option as displayed in figure 4-1.
41
4.1
Product
The Product option displays five cost drivers: RELY, DATA, DOCU, CPLX, and RUSE and their corresponding ratings
and multiplier values.
Select Product from the Parameters menu with the mouse. The Product Dialog Box will appear as Figure 4-2.
FIGURE 4-2
Product Dialog Box
To modify these values, go straight to those edit boxes and type new values. When finished with the modification, click
the OK button.
4.2
Platform
The Platform option displays three cost drivers: TIME, STOR and PVOL, and their corresponding ratings and multiplier
values.
Select Platform from the Parameters menu with the mouse. The Platform Dialog Box will appear as Figure 4-3.
FIGURE 4-3
42
Platform Dialog Box
the OK button.
4.3
Personnel
The Personnel option displays six cost drivers: ACAP, AEXP, PCAP, PEXP, LEXP, and PCON and their corresponding
ratings and multiplier values.
Select Personnel from the Parameters menu with the mouse. The Personnel Dialog Box will appear as Figure 4-4.
the OK button.
4.4
Project
The Project option displays three cost drivers: TOOL, SCED, and SITE and their corresponding ratings and multiplier
values.
Select Project from the Parameters menu with the mouse. The Project Dialog Box will appear as Figure 4-5.
the OK button.
43
FIGURE 4-4
44
Personnel Dialog Box
FIGURE 4-5
4.5
Project Dialog Box
User Defined EAF
The User Defined EAF option displays two cost driver: USR1 and USR2, and their corresponding ratings and multipliers.
Select User EAF from the Parameters menu with the mouse. The User EAF Dialog Box will appear as Figure 4-6.
FIGURE 4-6
User Defined EAF Dialog Box
the OK button.
45
4.6 Early Design

The Early Design Factors option displays nine development attributes: RCPX, RUSE, PDIF, PERS, PREX, FCIL, SCED,
USR1, USR2, and their corresponding ratings and values.
Select Early Design Factors from the Parameters menu with the mouse. The Early Design Factor Dialog Box will appear
as Figure 4-7.
FIGURE 4-7
Early Design Factors Dialog Box
4.7 Scale Factors

The Scale Factors option displays five development attributes: PREC, FLEX, RESL, TEAM and PMAT, and their
corresponding ratings and values.
Select Scale Factors from the Parameters menu with the mouse. The Scale Factor Dialog Box will appear as Figure 4-8.
46
FIGURE 4-8
Scale Factors Dialog Box
OK button.
4.8 Equation
The Equation option displays effort and schedule equations.
Select Equation from the Parameters menu with the mouse. The Equation Dialog Box will appear as Figure 4-9.
47
FIGURE 4-9
Equation Dialog Box
the OK button.
FIGURE 4-10
48
Person Month Dialog Box
4.9 Person Month

The Person Month option modifies the value of hors per person and month.
Type the value in field and click OK to apply new hour value to project. Figure 4-10 shows person month option box.
4.10 Function Point

The Function Point Factors option displays five function types: Internal Logical Files, External Interface Files, External
Inputs, External Outputs, External Inquiries, and their corresponding ratings and weight values.
Select Function Point from the Parameters menu with the mouse. The Function Point Dialog Box will appear as Figure
4-11.
FIGURE 4-11
Function Point Dialog Box
the OK button.
49
Chapter 5: Calibrate Menu

COCOMOII now has the ability to archive your own software project data. Using this data, COCOMOII will compute
various coefficients and exponents involved in the effort and schedule equations. This will make your COCOMOII
estimates even more reliable.
Each software project to be archived is described as a complete COCOMOII project. It may include multiple modules,
each with their own SLOC estimate and EAF factors. In addition, a software project consists of a name, date/time, actual
effort and actual schedule. The actual effort and actual schedule must be supplied by the COCOMOII user. Entering
revised values for effort and schedule are always possible. Effort is given in units of person/months. Schedule is given in
units of months.
FIGURE 5-1
50
Calibrate Menu
5.1
File Load
The Calibrate File Load option is used to retrieve a calibration project file as well as loading all project data on the
working project window(Figure5-2).
FIGURE 5-2
5.2
Load Calibration Dialog Box
File Save
The Calibrate File Save command saves the current calibration data in the file whose name was previously identified
using File Save As.
5.3
File Save As
The Calibrate File Save As command stores the current calibration data as a *.cal file, which has a different file name
from the current file. This command works precisely the same as the File Save As for *.est and *.mod files (see Figure 54).
51
FIGURE 5-3
Save Calibration Dialog Box
FIGURE 5-4
Save As Calibration Dialog Box
52
5.4
Project
A windows appears (shown in Figure 5-5) which displays the archived project data.
- To remove the window, click on Cancel.
- To delete an existing entry, first place an x at the leftmost end of the row and click on Delete. A warning box appears
as shown in Figure 5-6.
- To display the entire set of values for an archived project, click on Display. Since the display of an archived project
eliminates the display of any existing CLEF data, a warning message appears as shown in Figure 5-7.
- To insert a new archived project from the CLEF, click on Insert.
FIGURE 5-5
Projects Dialog Box
FIGURE 5-6
Delete Warning Dialog
53
FIGURE 5-7
5.5
Display Warning Dialog
Compute
This command takes all of the data that has been archived and uses it to compute new constant and exponent values for
the effort equation and similarly for the schedule equation. There are two options to calibrate equation parameters. One
is the Constant Term and the other one is Development Mode. Those two options are explained below in detail. They are
displayed in this window and compared to the values currently used by COCOMOII. To get COCOMOII to use these
values, click on Accept, as shown Figure 5-8.
FIGURE 5-8
54
Compute Dialog Box
Chapter 6: Phase Distribution

The Phase Distribution is one of the menu selections in the menu bar that can be accessed by either clicking upon Phase
Distribution in the main menu. Its function is to display a breakdown of the software effort and schedule into the phases
of the development cycle. There are two models for the phases; Waterfall Model and MBASE Model. The phases of
Waterfall model are plans & requirements, design, programming and integration & test. And the phases of MBASE
model are Inception, Elaboration, Construction, and Transition. These phases are described as follows:
Waterfall Model
Plans & Requirements - In this phase, a statement for the required functions, interfaces and performance is created.
These expectations are used to define the capabilities of the software product as expressed by representatives of all
interested parties.
Product Design - In this phase, a hardware/software architecture, control structure and data structure for the product are
defined. A draft of the user's manual and test plans are also created during this phase.
Programming - In this phase, the design of the previous phase is implemented in the creation of complete sets of
software components.
Integration & Test - In this phase, the various software components are brought together in order to achieve a properly
functioning software product composed of loosely coupled modules. The requirements as defined in the first phase are
used to determine the fitness of the delivered product.
MBASE Model
Inception phase - The first phase of the software life cycle, where the seed idea for the development is brought to the
point of being sufficiently well founded to warrant entering into the elaboration. Activities are
Understanding the organization background and analyzing the problem domain
Identifying feasible solutions
Understanding the requirements of the life cycle and obtaining concurrence from the system stakeholders
Elaboration - most of the system requirements are determined and the system architecture is designed.
Identifying and resolving the critical risks
Analyzing the problem domain
Identifying and enunciating a feasible architecture as the proposed solution
Determining the feasibility of proposed solution
Estimating the requirements of the life cycle and planning for their use
Identifying responsibilities of the system stakeholders
55
Construction - In this phase, the design of the previous phase is implemented in the creation of complete sets of software
components.
Requirements Management
Detailed Design
Coding
Unit and Integration Testing

Inspections
Configuration Management
Quality Assurance
Transition - In this phase, the transition plan, user manual, support plan will be done.
The phase distribution menu has two selections: project phase distribution and module phase distribution. The project
phase distribution allows the user to view the development phases for the entire project all together or individually. The
module phase distribution allows the user to view the development phases for a particular module either all together or
individually. These two variations of phase distribution are discussed further in this chapter under sections 6.1 and 6.2 in
this chapter. (figure 6-1)
NOTE: These phase distribution estimates are retained from the COCOMO81 model, which assumed a waterfall
(sequentially phased) process model. If your project's process model is not a waterfall, these phase distributions are
either inapplicable or need to be reinterpreted.
6.1
Waterfall

In order to view the phase distribution of an entire project, the user can click on the Project Phase Distribution button
under the Phase Distribution menu (see FIGURE 6-1). Four formats for viewing will appear in another menu: overall
phase, plan & requirements, programming, and integration & test. Each of these menu selections will be discussed in
sections 6.1.1 - 6.1.4, respectively. The phase distribution of plan & requirements, programming and integration & test
are broken down into sub-phases. These phases include: requirements analysis, product design, programming, test
planning, verification & validation, project office, CM/QA, and manuals. For each of these sub-phases the percentage of
the phase, the estimated effort, the estimated schedule, and the estimated FSWP is displayed. A description of each of
these sub-phases follows:
Requirements analysis: Determination, specification review and update of software functional, performance, interface,
and verification requirements.
FIGURE 6-1
56
Phase Distribution Sub-menu
Product Design: Determination, specification, review and update of hardware-software architecture, program design, and
database design.
Programming: Detailed design, code, unit test, and integration of individual computer program components. Includes
programming personnel planning, tool acquisitions, database development, component level documentation, and
intermediate level programming management.
Test Planning: Specification, review, and update of product test and acceptance test plans. Acquisition of associated test
drivers, test tools, and test data.
Verification & Validation(V&V): Performance of independent requirements validation, design V&V, product test, and
acceptance test. Acquisition of requirements and design V&V tools. "Are we building the product right?" and "are we
building the right product?"
Project Office Functions: Project level management functions. Includes project level planning and control, contract and
subcontract management, and customer interface.
57
Configuration Management and Quality Assurance (CM/QA): Configuration management includes product
identification, change control, status accounting, operation of program support library, development and monitoring of
end item acceptance plan. Quality assurance includes development and monitoring of project standards, and technical
audits of software products and processes.
Manuals: Development and update of users' manuals, operators' manuals and maintenance manuals.
6.1.1.1 Overall Project Phase Distribution

The overall phase distribution allows the user to view an entire project's estimated effort, schedule and number of
personnel needed for phase completion. Upon clicking on "Overall Phase," a window will be displayed showing the
phase breakdown of the current project in COCOMO (see FIGURE 6-2). This window displays the project name, project
SLOC, and the total estimated effort for the project. Looking at FIGURE 6-1, this information can be seen in the upper
left corner of the window.
FIGURE 6-2
Phase Distribution window displaying a sample project's overall phase distribution
In addition, each phase of the project's development cycle is represented by the estimated effort, the estimated schedule
and the estimated number of personnel needed for phase completion. Again looking at FIGURE 6-2, the information has
been separated into columns. The first column displays the phase name. The second column displays the percentage
that the corresponding phase takes in the estimated effort. The third column displays the estimated effort for each phase.
The fourth column displays the percentage of the estimated schedule that is dedicated to the corresponding phase's
58
completion. The fifth column displays the estimated schedule for phase completion. And the last column displays the
estimated number of personnel needed for phase completion (Staff).
Note: The programming phase has been broken down into two additional phases: "Detailed Design" and "Code and Unit
Test." The detailed design is a follow-up to the product design phase. In this sub phase, those points developed in the
product design are elaborated to a point necessary to breakdown agreed functions into units necessary for coding. The
code and unit test sub-phases house the actual coding effort of the individual units of code. The testing of these units
(upon completion) is also encompassed within this sub phase.
6.1.1.2 Plans and Requirements Project Phase Distribution

The plans and requirements phase distribution allows the user to view the components of this particular phase. When the
Plans and Requirements distribution is chosen from the Project Phase distribution menu, the window shown in FIGURE
6-3 is displayed. This window displays the following information: project phase, the total estimated project effort, and
the total estimated project schedule. In addition the window displays the estimated effort for the activities of
requirements analysis, product design, programming, test planning, verification & validation, project office, CM/QA,
and manuals. These activity estimates are accompanied with a percentage of the phase effort that they encompass, the
estimated effort, schedule and FSWP for the activity's completion as shown in FIGURE 6-3. To exit from this window
click the OK button.
FIGURE 6-3
Plans and Requirements Phase window for the overall project
6.1.1.3 Programming Project Phase
59
The programming phase distribution allows the user to view the components of this particular phase. When the
Programming distribution is chosen from the Project Phase distribution menu, the window shown in FIGURE 6-4 is
displayed. This window displays the following information: project name, the total project SLOC, the total estimated
project effort, and the total estimated project schedule. In addition the window displays the estimated effort for the
activities of requirements analysis, product design, programming, test planning, verification & validation, project office,
CM/QA, and manuals. These activities are accompanied with a percentage of the phase effort that they encompass, the
FIGURE 6-4
Programming Phase window for the overall project
6.1.1.4 Product Design Phase

The product design phase distribution allows the user to view the components of this particular phase. When the Product
Design distribution is chosen from the Project Phase distribution menu, the window shown in FIGURE 6-5 is displayed.
This window displays the following information: project name, the total project SLOC, the total estimated project effort,
and the total estimated project schedule. In addition the window displays the estimated effort for the activities of
requirements analysis, product design, programming, test planning, verification & validation, project office, CM/QA,
60
FIGURE 6-5
6.1.1.5
Product Design window for the overall project
Integration and Test Project Phase
The integration & test phase distribution allows the user to view the components of this particular phase. When the
Integration and Test distribution is chosen from the Project Phase distribution menu, the window shown in FIGURE 6-6
is displayed. This window displays the following information: project name, the total project SLOC, the total estimated
project effort, and the total estimated project schedule. In addition the window displays the estimated effort for the
activities of requirements analysis, product design, programming, test planning, verification & validation, project office,
CM/QA, and manuals. These activity estimates are accompanied with a percentage of the phase effort that they
encompass the estimated effort, schedule and FSWP for the activity's completion as shown in FIGURE 6-6. To exit
from this window click the OK button.
61
FIGURE 6-6
Integration and Test window for the overall project
6.1.2 Module Phase Distribution

Four formats for viewing will appear in another menu: overall phase, plan & requirements, programming, and integration
& test (see FIGURE 6-7). Each of these menu selections will be discussed in sections 6.2.1 - 6.2.4, respectively. The
phase distribution of plan & requirements, programming and integration & test are broken down into activities. These
activities include: requirements analysis, product design, programming, test planning, verification & validation, Module
office, CM/QA, and manuals. For each of these activities, the percentage of the phase, the estimated effort, the estimated
schedule, and the estimated FSWP is displayed. A description of each of these activities follows:
Requirements analysis: Determination, specification review and update of software functional, performance,
interface, and verification requirements.
Product Design: Determination, specification, review and update of hardware-software architecture, program design, and
database design.
62
FIGURE 6-7
Phase Distribution Module Sub-menu
Programming: Detailed design, code, unit test, and integration of individual computer program components.
Includes programming personnel planning, tool acquisitions, database development, component level
documentation, and intermediate level programming management.
Test Planning: Specification, review, and update of product test and acceptance test plans. Acquisition of
associated test drivers, test tools, and test data.
Verification & Validation(V&V): Performance of independent requirements validation, design V&V, product
test, and acceptance test. Acquisition of requirements and design V&V tools. "Are we building the product
right?" and "are we building the right product?"
Module Office Functions: Module level management functions. Includes Module level planning and control,
contract and subcontract management, and customer interface.
Configuration Management and Quality Assurance (CM/QA): Configuration management includes product
identification, change control, status accounting, operation of program support library, development and
monitoring of end item acceptance plan. Quality assurance includes development and monitoring of Module
standards, and technical audits of software products and processes.
63
Manuals: Development and update of users' manuals, operators' manuals and maintenance manuals.
In order to view the phase distribution of an entire Module, the user can click on the Module Phase Distribution button
under the Phase Distribution menu. When choosing any of the views of phase distribution, you will be confronted with a
module selection window (see FIGURE 6-8). At this point, you may choose which module is to be viewed by clicking
on the desired module name, which will be highlighted after the click. Click the OK button in order to initiate phase
distribution of the chosen module.
FIGURE 6-8
6.1.2.1
Module selection window
Overall Module Phase Distribution
The overall phase distribution allows the user to view an entire Module's estimated effort, schedule and number of
phase breakdown four formats for viewing will appear in another menu: overall phase, plan & requirements,
programming, and integration & test (see FIGURE 6-9). To exit from this window click the OK button.
In addition, each phase of the Module's development cycle is represented by the estimated effort, the estimated schedule
and the estimated number of personnel needed for phase completion. Again looking at FIGURE 6-9, the information has
been separated into columns. The first column displays the phase name. The second column displays the percentage
estimated number of personnel needed for phase completion (FSWP).
64
FIGURE 6-9
Phase Distribution window displaying a sample Module's overall phase distribution
code and unit test sub phase houses the actually coding effort of the individual units of code. The testing of these units
6.1.2.2
Plans and Requirements Module Phase Distribution
The plans and requirements phase distribution allows the user to view the components of this particular phase. When the
Plans and Requirements distribution is chosen from the Module Phase distribution menu, the window shown in FIGURE
6-10 is displayed. This window displays the following information: Module name, the total Module SLOC, the total
estimated Module effort, and the total estimated Module schedule. In addition the window displays the activities
requirements analysis, product design, programming, test planning, verification & validation, Module office, CM/QA,
65
FIGURE 6-10
6.1.2.3
Plans and Requirements Phase window for the overall Module
Programming Module Phase Distribution
The programming phase distribution allows the user to view the components of this particular phase. When the
Programming distribution is chosen from the Module Phase distribution menu, the window shown in FIGURE 6-11 is
displayed. This window displays the following information: Module name, the total Module SLOC, the total estimated
Module effort, and the total estimated Module schedule. In addition the window displays the activity's requirements
analysis, product design, programming, test planning, verification & validation, Module office, CM/QA, and manuals.
These activity estimates are accompanied with a percentage of the phase effort that they encompass, the estimated effort,
schedule and FSWP for the activity's completion as shown in FIGURE 6-11. To exit from this window click the OK
button.
6.1.2.4
Product Design Phase Distribution
The product design phase distribution allows the user to view the components of this particular phase. When the Product
Design distribution is chosen from the Module Phase distribution menu, the window shown in FIGURE 6-12 is
displayed. This window displays the following information: Module name, the total Module SLOC, the total estimated
Module effort, and the total estimated Module schedule. In addition the window displays the activities requirements
analysis, product design, programming, test planning, verification & validation, Module office, CM/QA, and manuals.
These activity estimates are accompanied with a percentage of the phase effort that they encompass, the estimated effort,
schedule and FSWP for the activity's completion as shown in FIGURE 6-12. To exit from this window click the OK
button.
66
FIGURE 6-11
Programming Phase window for the overall Module
FIGURE 6-12
Product Design window for the overall Module
67
6.1.2.5
Integration and Test Module Phase Distribution
The integration & test phase distribution allows the user to view the components of this particular phase. When the
Integration and Test distribution is chosen from the Module Phase distribution menu, the window shown in FIGURE 613 is displayed. This window displays the following information: Module name, the total Module SLOC, the total
estimated Module effort, and the total estimated Module schedule. In addition the window displays the activities
requirements analysis, product design, programming, test planning, verification & validation, Module office, CM/QA,
FIGURE 6-13
6.2
Integration & Test window for the overall Module
MBASE

In order to view the phase distribution of an entire project, the user can click on the Project Phase Distribution button
under the Phase Distribution menu (see FIGURE 6-14). Five formats for viewing will appear in another menu: overall
phase, Inception, Elaboration, Construction, and Transition. Each of these menu selections will be discussed in sections
6.2.1.1 - 6.2.1.5, respectively.
68
FIGURE 6-14
Phase Distribution Sub-menu
6.2.1.1 Overall Project Phase Distribution

The overall phase distribution allows the user to view an entire project's estimated effort, schedule and number of
phase breakdown of the current project in COCOMO (see FIGURE 6-15). This window displays the project name,
project SLOC, and the total estimated effort for the project. Looking at FIGURE 6-14, this information can be seen in
the upper left corner of the window.
In addition, each phase of the project's development cycle is represented by the estimated effort, the estimated schedule
and the estimated number of personnel needed for phase completion. Again looking at FIGURE 6-15, the information
has been separated into columns. The first column displays the phase name. The second column displays the percentage
69
FIGURE 6-15
Phase Distribution window displaying a sample project's overall phase distribution
code and unit test sub-phases house the actual coding effort of the individual units of code. The testing of these units
6.2.1.2 Inception Project Phase Distribution

The inception phase distribution allows the user to view the components of this particular phase. When the inception
distribution is chosen from the Project Phase distribution menu, the window shown in FIGURE 6-16 is displayed. This
window displays the following information: project phase, the total estimated project effort, and the total estimated
project schedule. In addition the window displays the estimated effort for the activities of requirements capture, analysis
and design, implementation, test, management, environment and deployment. These activity estimates are accompanied
with a percentage of the phase effort that they encompass, the estimated effort, schedule and Staff for the activity's
completion as shown in FIGURE 6-16. To exit from this window click the OK button.
70
FIGURE 6-16
Inception Phase window for the overall project
6.2.1.3 Elaboration Project Phase

The elaboration phase distribution allows the user to view the components of this particular phase. When the elaboration
and design, implementation, test, management, environment and deployment. These activities are accompanied with a
percentage of the phase effort that they encompass, the estimated effort, schedule and Staff for the activity's completion
as shown in FIGURE 6-17. To exit from this window click the OK button.
6.2.1.4 Construction Design Phase

The construction design phase distribution allows the user to view the components of this particular phase. When the
construction distribution is chosen from the Project Phase distribution menu, the window shown in FIGURE 6-18 is
displayed. This window displays the following information: project phase, the total estimated project effort, and the total
estimated project schedule. In addition the window displays the estimated effort for the activities of requirements
capture, analysis and design, implementation, test, management, environment and deployment These activity estimates
are accompanied with a percentage of the phase effort that they encompass, the estimated effort, schedule and Staff for
the activity's completion as shown in FIGURE 6-18. To exit from this window click the OK button.
71
FIGURE 6-17
Elaboration Phase window for the overall project
FIGURE 6-18
Construction window for the overall project
72
6.2.1.5 Transition Project Phase

The transition phase distribution allows the user to view the components of this particular phase. When the transition
and design, implementation, test, management, environment and deployment. These activity estimates are accompanied
with a percentage of the phase effort that they encompass the estimated effort, schedule and Satff for the activity's
completion as shown in FIGURE 6-19. To exit from this window click the OK button.
FIGURE 6-19
Transition window for the overall project
6.2.2 Module Phase Distribution

Five formats for viewing will appear in another menu: overall phase, inception, elaboration, construction, and transition
(see FIGURE 6-20). Each of these menu selections will be discussed in sections 6.2.2.1 - 6.2.2.5, respectively. The
phase distribution of inception, elaboration, construction and transition are broken down into activities. These activities
include: requirements capture, analysis and design, implementation, test, management, environment and deployment.
For each of these activities, the percentage of the phase, the estimated effort, the estimated schedule, and the estimated
Staff is displayed.
73
FIGURE 6-20
Phase Distribution Module Sub-menu
In order to view the phase distribution of an entire Module, the user can click on the Module Phase Distribution button
under the Phase Distribution menu. When choosing any of the views of phase distribution, you will be confronted with a
module selection window (see FIGURE 6-21). At this point, you may choose which module is to be viewed by clicking
on the desired module name, which will be highlighted after the click. Click the OK button in order to initiate phase
distribution of the chosen module.
FIGURE 6-21
74
Module selection window
6.2.2.1 Overall Module Phase Distribution

The overall phase distribution allows the user to view an entire Module's estimated effort, schedule and number of
phase breakdown four formats for viewing will appear in another menu: overall phase, plan & requirements,
programming, and integration & test (see FIGURE 6-22). To exit from this window click the OK button.
In addition, each phase of the Module's development cycle is represented by the estimated effort, the estimated schedule
and the estimated number of personnel needed for phase completion. Again looking at FIGURE 6-22, the information
has been separated into columns. The first column displays the phase name. The second column displays the percentage
FIGURE 6-9
Phase Distribution window displaying a sample Module's overall phase distribution
75
6.2.2.2 Inception Module Phase Distribution

The inception phase distribution allows the user to view the components of this particular phase. When the inception
distribution is chosen from the Module Phase distribution menu, the window shown in FIGURE 6-23 is displayed. This
window displays the following information: Module name, the total estimated Module effort, and the total estimated
Module schedule. In addition the window displays the activities requirements capture, analysis and design,
implementation, test, management, environment and deployment. These activity estimates are accompanied with a
percentage of the phase effort that they encompass, the estimated effort, schedule and FSWP for the activity's completion
FIGURE 6-23
Inception Phase window for the overall Module
6.2.2.3 Elaboration Module Phase Distribution

The elaboration phase distribution allows the user to view the components of this particular phase. When the elaboration
Module schedule. In addition the window displays the activity's requirements capture, analysis and design,
76
FIGURE 6-24
FIGURE 6-25
Elaboration Phase window for the overall Module
Construction window for the overall Module
77
6.2.2.4 Construction Phase Distribution

The construction design phase distribution allows the user to view the components of this particular phase. When the
Product Design distribution is chosen from the Module Phase distribution menu, the window shown in FIGURE 6-25 is
displayed. This window displays the following information: Module name, the total estimated Module effort, and the
total estimated Module schedule. In addition the window displays the activities requirements capture, analysis and
design, implementation, test, management, environment and deployment. These activity estimates are accompanied with
a percentage of the phase effort that they encompass, the estimated effort, schedule and Staff for the activity's completion
6.2.2.5 Transition Module Phase Distribution

The transition phase distribution allows the user to view the components of this particular phase. When the transition
Module schedule. In addition the window displays the activities requirements capture, analysis and design,
FIGURE 6-26
78
Transition window for the overall Module
Chapter 7: Maintenance
Maintenance is one of the menu selections in the menu bar that can be accessed by either clicking upon "Maintenance" in
the menu bar or pressing Meta+M. Its function is to calculate and display an estimate of the effort and cost necessary to
maintain a post development software product for a user-defined number of years (maximum five years). Maintenance
encompasses the process of modifying existing operational software while leaving its primary functions intact. This
process excludes the following types of activities:
Major re-design and re-development (more than 50% new code) of a new software product performing
substantially the same functions
Design and development of a sizeable (more than 20% of the source instructions comprising the existing
product) interfacing software package which requires relatively little redesigning of the existing product
Data processing system operations, data entry, and modification of values in the database
Maintenance does include the following types of activities:
Re-design and re-development of small portions of an existing software product

Design and development of small interfacing software packages, which require some redesign of the existing
software product
Modification of the software product's code, documentation, or database structure
Maintenance effort and costs are determined by essentially the same cost driver attributes used to determine the software
development costs and effort (exceptions are the RELY, SCED and MODP factors which will be discussed in greater
detail later in this chapter). The maintenance calculations are heavily based upon the Maintenance change Factor (MCF)
and the Maintenance Adjustment Factor (MAF). The MCF is similar to the Annual change Traffic in COCOMO81,
except that maintenance periods other than a year can be used (see EQ 7-1).
Maintenance Change Factor (EQ 7-1)
The initial maintenance size is obtained in one to two ways. The first equation in EQ 7-2 is used when the base code size
is known and percentage of change to the base code is known. The second equation in EQ 7-2 is used when the fraction
of code added or modified to the existing base code during the maintenance period is known.
Initial Maintenance Size(EQ 7-2)
As shown in EQ 7-2, the initial maintenance size estimate is adjusted with a Maintenance Adjustment Factor (see EQ 73).
79
Maintenance Adjustment Factor(EQ 7-3)
The resulting maintenance effort estimation formula is the same as the COCOMOII Post Architecture development
model (see EQ 7-4).
Maintenance Effort(EQ 7-4)
FIGURE 7-1
Maintenance sub-menu
As stated previously, three cost drivers for maintenance differ from development. Those cost drivers are software
reliability (RELY), modern programming practices (MODP) and schedule (SCED). The reason for the change in MODP,
RELY is that increased investment in software reliability and use of modern programming practices during software
development have a strong positive effect upon the maintenance stage. The SCED attribute is controlled by the number
80
of years value entered by the user. As a result the SCED driver is no longer editable in the EAF window, but is
calculated from the user inputted value for number of years when the maintenance function is engaged. For more
information on these cost drivers please refer to the introduction of this manual.
The Maintenance menu option offers sub-menu for either a maintenance effort estimation upon either an entire project or
an individual module (see Figure 7-1). These separate options are discussed in section 7.1 and 7.2.
7.1
Project Maintenance
In order to view the maintenance estimation calculations for an entire project, the user can click on Project under the
Maintenance menu (see Figure 7-1). Upon clicking upon this selection a window will appear displaying the Scale factor
button (see Figure7-2).
The Scale rate can be changed by clicking upon the corresponding button. This action
FIGURE 7-2
Project Maintenance Dialog Box
will result in the appearance of an Scale dialog box where the cost driver ratings can be changed as described in the
introduction (see Figure 7-3).
Upon completing the adjustment of the cost drivers click the OK button or click the Cancel button to return to the CLEF
without viewing maintenance estimations.
81
After exiting the Scale dialog box, you will be returned to the Project Maintenance Dialog box to continue inputting the
editable values.
Click upon the OK button upon completion of editing the displayed fields or click upon the Cancel button if no changes
are desired to the default values (if more assistance, the Help button is available to receive on-line assistance).
FIGURE 7-3
Project Maintenance Scale Dialog Box
FIGURE 7-4
Project Maintenance window (page 1)
82
When the OK button is clicked in the Project Maintenance Dialog Box, a window displaying the first of four pages that
contains the project name, the current development mode, the total number of source instructions for development of the
project (EDSI) that is loaded in the CLEF, the nominal effort of the project, the actual effort of the project, the
development cost, the inputted maintenance labor rate, the inputted percent of code added during maintenance per year,
the inputted percent of code modified during maintenance per year (see Figure 7-4) and the calculated annual change
traffic. The second page of the maintenance window can be seen by clicking upon the Next button. It contains the
settings for the 16 cost drivers, SCED is not applicable (see Figure 7-5).
FIGURE 7-5
The third page of the maintenance window contains the effort and cost estimation for the next N number of years (as
defined by the user). With each year is listed the KDSI (EDSI * 103), the nominal effort for development (PM nom), the
actual effort for maintenance (PM maint), the number of full time software personnel necessary to maintain the project
for the year (FSWP), the number of instructions that are to be maintained be per personnel(KDSI/FSWP) and the total
cost for maintenance for the year (see Figure 7-6).
The fourth window of the maintenance window contains the cumulative figures for effort and cost for maintenance for
the total number of years (see figure 7-7). This first displays the total number of effort estimated for maintenance, then
sums the effort of development and maintenance together. It also displays the total cost of maintenance of the project and
then displays the summed total cost of development and maintenance for the entire project.
83
FIGURE 7-6
FIGURE 7-7
84
Note - Each individual page can be seen by cycling through the pages pressing either the Previous or Next buttons as
needed.
7.2
Module Maintenance
In order to view the maintenance estimation calculations for an entire module, the user can click on Module under the
Maintenance menu (see Figure 7-1). Upon clicking upon this selection a window will appear displaying the current
module names. Choose only one of the modules by highlighting the appropriate module name and then clicking upon
OK (see Figure 7-8).
FIGURE 7-8
Module Selection window
Upon exiting the module selection window, another window will be appear that displays, the selected module name, an
EAF button, an editable labor rate field, editable number of years of maintenance field, an editable percent of added
source instructions field per year of maintenance and an editable percent of modified source instructions field per year of
maintenance (see Figure 7-9).
FIGURE 7-9
Module Maintenance Dialog Box
85
The EAF rate can be changed by clicking upon the corresponding button. This action will result in the appearance of an
EAF dialog box where the cost driver ratings can be changed as described in the introduction (see Figure 7-10).
FIGURE 7-10
Module Maintenance EAF Dialog Box
Upon completing the adjustment of the cost drivers click the OK button or click the Cancel button to return to the CLEF
without viewing maintenance estimations.
After exiting the EAF dialog box, you will be returned to the Module Maintenance Dialog box to continue inputting the
editable values.
Click upon the OK button upon completion of editing the displayed fields or click upon the Cancel button if no changes
are desired to the default values (if more assistance, the Help button is available to receive on-line assistance).
When the OK button is clicked in the Module Maintenance Dialog Box, a window displaying the first of four pages that
contains the module name, the current development mode, the total number of source instructions for development of the
module (EDSI) hat is loaded in the CLEF, the nominal effort of the module, the actual effort of the module, the
development cost, the inputted maintenance labor rate, the inputted percent of code added during maintenance per year,
86
the inputted percent of code modified during maintenance per year (see figure 7-11) and the calculated annual change
traffic.
FIGURE 7-11
Module Maintenance window (page 1)
The second page of the maintenance window can be seen by clicking upon the Next button. It contains the settings for
the 16 cost drivers, SCED is not applicable (see Figure 7-12).

FIGURE 7-12
87
The third page of the maintenance window contains the effort and cost estimation for the next N number of years (as
defined by the user). With each year is a listed the KDSI (EDSI * 103), the nominal effort for development (PM nom),
the actual effort for maintenance (PM maint), the number of full time software personnel necessary to maintain the
module for the year (FSWP), the number of instructions that are to be maintained be per personnel(KDSI/FSWP) and the
total cost for maintenance for the year (see Figure 7-13).
FIGURE 7-13
The fourth window of the maintenance window contains the cumulative figures for effort and cost for maintenance for
the total number of years (see Figure 7-14). This first displays the total number of effort estimated for maintenance, then
sums the effort of development and maintenance together. It also displays the total cost of maintenance of the module
and then displays the summed total cost of development and maintenance for the entire module.
88
FIGURE 7-14
Note - Each individual page can be seen by cycling through the pages pressing either the Previous or Next buttons as
needed.
89

User Manual COCOMO2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User Manual COCOMO2

Uploaded by

Copyright:

Available Formats

USC COCOMO II

University of Southern California

COCOMO REFERENCE MANUAL

This manual is compatible with USC-COCOMO II.

COCOMO REFERENCE MANUAL

Student Designers, Testers and programmers Keun

COCOMO REFERENCE MANUAL

Chapter 5: Calibrate menu

Chapter 6: Phase Distribution

Chapter 3: Edit Menu 36

COCOMO REFERENCE MANUAL

COCOMO REFERENCE MANUAL

Effort Estimation Equation

SFj and PM Auto =

Adapted SLOC x (AT

Equivalent KSLOC = Adapted KSLOC AAM (1 - AT

AA + AAF (1 + [0.02 SU UNFM])

AAF = (0.4 DM) + (0.3 CM) + (0.3 IM)

COCOMO REFERENCE MANUAL

1.1.2 Schedule Estimation Equation

1.1.3 Scale Factors

COCOMO REFERENCE MANUAL

Scale Factors Very Low

very difficult some difficult Basically

1.1.4 Sizing Methods

. % significant module interfaces specified,% significant risks eliminated.

COCOMO REFERENCE MANUAL

COCOMO REFERENCE MANUAL

Figure 1-1 Definition Checklist for Source Statements Counts

COCOMO REFERENCE MANUAL

1.1.5 FP: Counting with Unadjusted Function Points

COCOMO REFERENCE MANUAL

1.1.6 AAF: Adaptation Adjustment Factors

1.1.7 Effort Multipliers

Required software reliability (RELY)

Execution time constraint (TIME)

COCOMO REFERENCE MANUAL

Analyst capabilities (ACAP)

Use of software tools (TOOL)

Estimate Development Effort

COCOMO REFERENCE MANUAL

COCOMO REFERENCE MANUAL

COCOMO REFERENCE MANUAL

SLOC Dialog Box - Source Lines of Code (SLOC)

COCOMO REFERENCE MANUAL

SLOC Dialog Box - Function Points (FP)

COCOMO REFERENCE MANUAL

SLOC Dialog Box - Adaptation Adjustment Factor (AAF)

COCOMO REFERENCE MANUAL

COCOMO REFERENCE MANUAL

EAF Dialog Box

Schedule Dialog Box

COCOMO REFERENCE MANUAL

COCOMO REFERENCE MANUAL

Scale Factor Dialog Box

Risk Level Dialog Box

Begin Using COCOMO

COCOMO REFERENCE MANUAL

Totals area after calculations have been completed

Running COCOMO: Windows, Sparc or Java

COCOMO REFERENCE MANUAL

Chapter 2: File Menu

COCOMO REFERENCE MANUAL

COCOMO REFERENCE MANUAL