Data Collection Set

1. Count the Source Lines of Code (SLOC) you deliver, and generate a brief Size Report (see below). See below for possible Code Counters. If you cannot find code counter(s) for particular programming languages, please let us know, and we will provide you with guidelines for manually counting the code.

2.  Do the combined COCOMO II and COQUALMO data gathering questionaire and the COCOMO II TOOL Components Questionnaire.  If you wish, you may use the COCOMO II-1998 spreadsheet to help you select the values for the drivers. The spreadsheet and manual are designed to assist the user in identifying the appropriate driver rating levels [and numeric values]. This all takes place on the 2nd through the last worksheets of the workbook.  The first worksheet just uses those values to calculate the effort and schedule assuming you have only one module.

3.  Do the COCOTS data gathering questionaire.

4.  Do the CORADMO data gathering questionaire.

Size Report

Below is an example portion of size metrics report. This example shows the case where a component may be composed of multiple languages:
 
Component Size Language Type % Breakage DM CM IM AA SU UNFM AAM Equivalent Size Source Code Counter
User Interface 2538 Java New 10               2538    
User Interface 320 HTML New 15               320    
Add User 438 Java Modified 5 30 35 40 4 20 .4 .44 193 CS577a Team 2 prototype  
Image Processing 3320 C++ New 20               3320    
                             
Total 6616                     6371    

Code Counters

You can use any of the following counters, or any other code counters you may have access to (for instance, code counters used by your company, to which you have access):