DSCA_-_Currently_Used_DSCA_Function_Point_Counting_Practice_Resolutions_....pdf

CURRENTLY USED

DSCA FUNCTION POINT COUNTING PRACTICES RESOLUTIONS

2 OCTOBER 2013

Extract

Acronyms.

APM – IFPUG SNAP Assessment Practices Manual CPM – IFPUG Function Point Counting Practices Manual EI – external input EIF – external interface file EO – external output EQ – external inquiry FTR – file type referenced IFPUG – International Function Point Users Group ILF – internal logical file RET – record element type SNAP – Software Non-functional Assessment Process

1. All DSCA function point counts will be based on the counting rules in the IFPUG CPM, except as discussed below. All SNAP counts will be based on the IFPUG Snap Assessment Practices Manual.

2. The Super File rule from the IFPUG CPM 3.4 is recognized. For each ILF and EIF which contains more than 100 DETs, each file RET is considered a unique ILF (EIF) assuming all other IFPUG counting rules apply. The statistical justification for this rule can be obtained at the DSCA-CPO SharePoint site, Library: Function Points, SNAP Points and Software Metrics, item 81, “Super File Rule.”

3. The IFPUG General Systems Characteristics will be used, per the standard IFPUG CPM procedure.

4. The possible selections in Tools/Edit drop down menus may be “turned on” or “off” depending on what aspect of the main application functionality is currently being used. Per Mechanicsburg, this is necessary functionality as it is part of the user’s view of the execution of certain internal business rules. Each selection choice in drop down menus which “turn on” or “off” during the operation of the application is counted as a unique low EI.

5. The Report Generator Rule from CPM 3.4 (pg. 22) is recognized. For each report type (elementary process), count one EQ (or EO), and count one low EI for each selectable field.

6. Sometimes, users also require COTS functionality. The COTs functionality most likely to be used in conjunction with the regular operation of the application is counted. For example, count some of the COTS functionality inherent in Impromptu for DSAMS such as the ability to change report font size, color, etc.

7. Notification messages often appear as error messages or confirmation messages, but require the use of an internal calculation. These are counted as EOs, per David Longstreet

(www.softwaremetrics.com, "Function Points Applied to New and Emerging Technologies," pg 16 ("Messages")).

8. Algorithms are counted under SNAP, 1.2 Logical and Mathematical Operations.

9. Visual Basic “Grid” update functionality (EI) is assumed to be High. Visual Basic “Grid” responses in EQs and EOs are assumed to be Average.

10. Some software defects are discovered at user acceptance testing or later by the user. These defects may reflect errors in the original requirements delivered by the user and are the responsibility of the user. Since the development effort to program these original requirements are presumed to be in good faith, the effort needed to correct these defects will be considered original software development. The associated function points will be countable as “enhancement” function points.

11. An ILF is considered “maintainable” if it is likely that its data will be changed at least annually, assuming all other ILF counting rules apply.

12. An ILF may be maintained either through a process similar to using a typical input screen, or it may be maintained manually by a programmer. Both methods are considered to be part of elementary processes. Function points resulting from manual programmer maintenance will be counted as conversion function points.

13. All maintainable database tables will be counted -- to include those identified as “service” tables – assuming all other ILF counting rules apply. This is because the correlation between ILFs and function points was found to be higher when all tables are considered than if service tables are not considered.

14. Hard coded data tables will be counted as ILFs (or RETs) if they are maintained manually through conversion functionality and all other ILF counting rules apply, such as in paragraph 11 above.

15. “Help” will counted under SNAP, when the Help is more fully researched. Do not count Help at the present time.

16. DSAMS backfits are counted as conversion functionality.

17. Multiple media are counted as individual instances of functionality, per CPM 3.4, page 22, “Identical reports, produced on different media due to specific user requirements, are counted as separate External Outputs.” Additionally, multiple file type formats, such as .wpd, .xls, .dbf, etc., are interpreted/counted as additional individual instances of EO or EQ functionality. For example, five EOs that can be generated in .wpd, .xls, and .dbf formats for each will be counted as seven EOs; if those five EOs can also be displayed on a screen, then 12 EOs will be counted.

18. Impromptu’s alias table functionality is considered countable as those tables are considered necessary from a user’s viewpoint.

19. Drop downs or pop-ups allowing the user to select a “country” are considered unique EQs in themselves, because the list of countries that do business through DSCA changes and is therefore considered “maintained” in either an associated ILF or EIF.

20. Ensure that data validations are counted based on unique instances of processing logic.

Multiple instances of the same processing logic for several DETs will be counted as a single data validation.

21. The system clock is counted as a low EIF.