This white paper describes an approach to using Function Point Analysis (FPA) in the identification and measuring of software reuse. "Reuse" is defined as "using existing software components in the development or enhancement of applications". Other forms of reuse exist, such as regression testing, requirements templates, design templates, and so on; however, these forms of reuse are outside of the scope of this document. The General Systems Characteristics (GSC) #10 regarding "reusability" which describes the degree to which the application and the code in the application have been specifically designed, developed, and supported to be usable in other applications — will not be discussed in this document.

In today’s faster, better, cheaper mode of business, software reuse is an important issue. The Function Point Analyst may need to perform an analysis to determine where reuse opportunities exist for an in-house project team. He or she may also need to investigate reused components from external sources such as Commercial-Off-the-Shelf (COTS) packages, with or without customization. FPA helps provide quantifiable information to better understand and manage reuse.

Note: The New Environments Committee (NEC) white papers on Component-Based Development and Middleware Applications are recommended supplemental references on this subject.
The specific Function Point Analysis procedures addressed in this paper are:

• Determining the scope of the count
• Identifying the application boundary
• Determining the data and transactional functions

For the exact definitions of user, boundary, and data or transactional functions, please see the IFPUG Counting Practices Manual.

Login as a member to access this resource.

Non-Members: $20.00, purchase the publication here: https://ifpug.memberclicks.net/boundaries