F UNCTION POINT ANALYSIS
C ounting Function Points
IFPUG CPM Version 4.2
this application; and is dependent upon the user’s external business view of the application.
• The boundary is determined based on the user's point of
view. The focus is on what the user can understand and
• The boundary between related applications is based on
separate business functions as seen by the user, not on
• For enhancement projects, the initial boundary must conform to the boundaries already established for the application or applications being modified.
I nternal Logical File (ILF)
321 Main Street
Woodbridge, New Jersey 07095
U ser View
A user is any person that specifies Functional User
Requirements and/or any person or thing that communicates or interacts with the software at any time.
A user view represents a formal description of the user’s
business needs in the user’s language. Developers translate the user information into information technology language in order to provide a solution. A function point count is accomplished using the information in a language that is common to both
user(s) and developers.
A user view is a description of the business functions; is
approved by the user; can be used to count function points; can vary in physical form (e.g., catalog of transactions, proposals, requirements document, external specifications, detailed
specifications, user handbook)
User Identifiable is a defined requirement for processes and/or groups of data that are agreed upon, and understood by both
the user and the software developers.
C ounting Boundary
The application boundary defines what is external to the
application; is the conceptual interface between “internal” application and “external” user world; acts as a “membrane” through which data passes into and out from the application; encloses the logical data maintained by the application; assists in identifying logical data referenced by, not maintained within,
An internal logical file (ILF) is a user identifiable group of logically related data or control information maintained within the boundary of the application. The primary intent of an ILF is to hold data maintained through one or more elementary
processes of the application being counted.
Internal Logical Files Identification Rules
• The group of data or control information is a logical and user identifiable.
• The group of data is maintained through an elementary
process within the application boundary being counted.
ILF & EIF Data Element (DET) Type Identification Rules
• Count a DET for each unique user recognizable, nonrepeated field maintained in or retrieved from the ILF or EIF through the execution of an elementary process.
• When two applications maintain and/or reference the same ILF/EIF, but each maintains/references separate DETs,
count only the DETs being used by each application to size
• Count a DET for each piece of data required by the user to establish a relationship with another ILF or EIF.
ILF & EIF Record Element Type (RET) Identification Rule
• Count an RET for each optional or mandatory subgroup of
the ILF; OR
• If there are no subgroups, count the ILF as one RET.
Data Element Types
1 – 19
20 - 50
E xternal Interface File (EIF)
An external interface file (EIF) is a user identifiable group of logically related data or control information referenced by the application, but maintained within the boundary of another
application. The primary intent of an EIF is to hold data
referenced through one or more elementary processes within
the boundary of the application counted. This means an EIF
counted for an application must be in an ILF in another
Please join StudyMode to read the full document