Types of Functional Size Reporting

SCOPE reports the functional size in 4 different ways. Each Type of report is used for a different purpose and has a different scope of functions included in the Size. The types of SCOPE reports are as follows:

  1. Release Baseline Functional Size
  2. Release Impacted Functional Size
  3. Release Reworked Functional Size
  4. Count Session Impacted Functional Size

The type of report can be selected at the time of reporting.

Release Baseline Functional Size

Reports the ‘Net’ size of the Release after all the impacts from the Count Sessions have been applied. Although the functions marked as deleted are displayed on the screen, these deleted functions will be excluded from the reports and the calculated net reported size.

The Baseline Release Functional Size for a Work in Progress Release will be the same as the size that will be reported in the Production Release after it is used to update the Production Release.

This size measures the total amount of functionality that is delivered to the User by the application and will be supported.

Note: In IFPUG CPM terminology this report would be equivalent to the Application Baseline Size (Production Release) or the Development Project Size (WIP Release).

Release Impacted Functional Size

Reports the aggregated size of the Count Sessions listed under the selected Release. It is the total size of this Work in Progress Release and is the aggregated size of the unique functions impacted by the Count Sessions listed for the Release. This is different from a Release Reworked Report in that if more than one Count Session impacts a Process or Data Group then the impacted function is only included once in the total size. E.g.: if the WIP Release had two Change Requests (i.e. separate Count Sessions) that changed a process of 4 function points, then the impacted process would only contribute 4 function points to the Release Impacted Functional Size. However the impacted process would contribute 4 function points to the size of each Count Session within the Release.

This size measures the total amount of unique functionality that is worked on during the Release and ignores any rework. It is the net size of the Release irrespective of how many times a function was impacted by Change Requests.

Note: In IFPUG CPM terminology this report would be equivalent to the sum of the Enhancement Project Counts for a particular Release of an Application except that it excludes duplicate counting of Enhancement Projects that impact the same function.

Release Reworked Functional Size

Reports the cumulative size of the Count Sessions listed under the selected Release. It is the total size of all the work done in this Work in Progress Release . This is different from a Release Impacted Report in that if more than one Count Session impacts a Process or Data Group then the impacted function is only included each time it is impacted in the total size. E.g. if the WIP Release had two Change Requests (i.e. separate Count Sessions) that changed a process of 4 function points, then the impacted process would contribute 8 (i.e. 4 + 4) function points to the Release Reworked Functional Size.

This size measures the total amount of functionality that is worked on during the Release and includes any rework. It is the total aggregated size of the Release and takes into account for the size if a function was impacted by more than one Change Request. Many suppliers use this report for billing purposes as it actually reflects the work they were asked to do.

Note: In IFPUG CPM terminology this report would be equivalent to the actual sum of the Enhancement Project Counts for a particular Release of an Application.

Count Session Impacted Functional Size

Reports thesize of each Change Request (Enhancement Project) as a Count Session within a Release. It is the total size of all impacted (added, changed, and deleted) processes and data groups for the selected Count Session listed within the Work in Progress Release.

This size measures the total amount of functionality that is worked on during by the Change Request for the Count Session.

Note: In IFPUG CPM terminology this report would be equivalent to the size of an Enhancement Project Count for a particular Release of an Application.

See also Report Selection.