Function Points FAQs

Decommissioned Functionality

Home

Issue Description

Background

General Discussion

 



ISSUE

Should functionality, which is no longer used, but still exists within the application programs, be included within the scope of application baseline function point counts? Should functions/programs that exist in ‘adhoc’ program libraries be included?

BACKGROUND

It is understood that within the older, legacy systems there is a significant amount of decommissioned or unused functionality. These programs still exist within program libraries but are no longer used. Typically these are reporting functions. The mechanisms (eg menus), which enable these functions to be initiated, may or may not still be operational.

 Some applications, in addition to the standard preformatted reports, maintain adhoc libraries of report requests that have been developed over time. These reports, or stored queries, are identifiable and serve a business purpose. Typically, a report in the adhoc library is initiated by a developer in response to an ‘adhoc’ user request. The report code may be further refined or modified to satisfy the requirements of the latest request.

Home


RESOLUTION

Decommissioned functionality, where it is identified as such, and where the programs still exist within program libraries and could potentially be used, is included within the scope of the application baseline function point count.

Under IFPUG guidelines adhoc functionality is not normally counted as part of a development or enhancement project. This type of development activity is included under the category of Support Maintenance. For project counts, where the report or query is migrated to production or stored for future reference or use, in a recognised, indexed program library it should be treated as a permanent application function. Care should be taken to count only unique elementary processes. Adhoc program libraries tend to have many variations of the initial function.


Home

Issue Description

Background

Resolution