Counting Conversion Functionality
IFPUG 4.3 CPM provides guidelines for measuring Conversion Functionality. In summary it recommends that you include in your project size as conversion functionality, any elementary processes and logical files that required to convert existing functionality to satisfy the new requirements of the software but this conversion functionality is not implemented with the software.
How to Count Conversion Functionality in SCOPE
There are two suggested methods, both have the same overall result.
- Recommended Method : Create "Conversion" Count Session
- Create a specific Count Session within the Release and name the Count Session so you know it is Conversion Functionality e.g. "CR0129- Conversion functionality" .
- Link the "Conversion" Count Session to your Project
- Open the "Conversion" Count Session and mark as impacted (Added) the elementary processes and logical files that satisfy the IFPUG definition for being conversion functionality.
- When the Release is selected to "Update to Baseline" select to "Exclude" the Count Session (e.g. "CR0129- Conversion functionality") from the Update. This will ensure that none of your conversion functionality will be included in the Production Release Baseline size.
- Result : Conversion Functionality will correctly be included (recorded as impact = Added) in both the Work in Progress-Release Size and also the Project Size, but will NOT be included in the Baseline Size.
- Alternative Method : Use an Attribute to identify "Conversion" functionality
- Open the Count Session that has the "Conversion" functionality mark as impacted (Deleted) the elementary processes and logical files that satisfy the IFPUG definition for being conversion functionality.
- Create an Attribute Category called "Project Requirements Type", then under the Category create two Attributes - called "Conversion Functionality" and "Delivered Functionality". Link the Attribute "Conversion Functionality" to all the functionality you identified as being counted as 'Conversion Functionality.
- When the Release is selected to "Update to Baseline" accept to include all Count Sessions. SCOPE will automatically remove all functionality that is marked as Deleted.
- Result : Conversion Functionality will correctly be included (but recorded as impact = Deleted ) in both the Work in Progress- Release Size and also the Project Size, but will NOT be included in the Baseline Size.