Fp Counting Function Points Reference Guide
F UNCTION POINT ANALYSIS
C ounting Function Points
Reference Guide
IFPUG CPM Version 4.2
this application; and is dependent upon the user’s external business view of the application.
Boundary Rules:
• The boundary is determined based on the user's point of view. The focus is on what the user can understand and describe. • The boundary between related applications is based on separate business functions as seen by the user, not on technological concerns.
• 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)
www.softwarems.com
321 Main Street
Woodbridge, New Jersey 07095
Tel: 732-750-0020
Email: info@softwarems.com
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;
C ounting Function Points
Reference Guide
IFPUG CPM Version 4.2
this application; and is dependent upon the user’s external business view of the application.
Boundary Rules:
• The boundary is determined based on the user's point of view. The focus is on what the user can understand and describe. • The boundary between related applications is based on separate business functions as seen by the user, not on technological concerns.
• 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)
www.softwarems.com
321 Main Street
Woodbridge, New Jersey 07095
Tel: 732-750-0020
Email: info@softwarems.com
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;