The ALLOCATION_STRUCTURE Worksheet

 

 

Structure ScreenThe user will be presented with the ALLOCATION_STRUCTURE worksheet as shown below:

Structure Screen

 

 

 

 


An example of the three allocation levels in use is as follows:

 

 

 

 

The following example of system functionality mapped to the allocation STRUCTURE would appear on the DETAILS worksheet:

 

FUNCTIONAL_MODULE

SUB_MODULE

DETAIL

DESCRIPTION

Alerts

Management

AL1

Management Alert 1

Alerts

Management

AL2

Management Alert 2

Alerts

Management

AL3

Management Alert 3

 

·         It will be necessary for the project to categorize or map its system functionality into distinct levels of work and units of work in order to use the CAM-TOOL. The CAM-TOOL supports up to 3 levels of work. For example, all functional modules do not have to have submodules or details and all submodules do not have to have details. The CAM-TOOL will work with a combination of the three different levels.

 

·         The project should estimate or track software development level of effort (e.g., programming time, testing time, etc.) associated to the system functionality related to the allocation STRUCTURE. For example, if there is “Detail” level system functionality, then it is optimal to track the work expended on details like a specific report. However, if the system has only been divided into distinct submodules, then one can only capture level of effort at the submodule level.

 


 

 

Allocation Base

Description

SOFTWARE DEVELOPMENT HOURS

Estimated or actual development hours expended on specific system functionality

STORAGE/DATABASE SIZE

Estimated or actual storage size or database size related to specific system functionality

LINES OF CODE (LOC)

Estimated or actual lines of code related to specific system functionality

FUNCTION POINTS

Estimated or actual function points related to specific system functionality

SCREENS

Estimated or actual screens related to specific system functionality