F UNCTION POINT EVALUATION
C ounting Function Items
IFPUG CPM Version 5. 2
this application; which is dependent upon the user's exterior business perspective of the software.
вЂў The boundary is decided based on the user's stage of
perspective. The focus is on what the user can understand and
вЂў The border between related applications is dependent on
separate organization functions because seen by the user, not really on
вЂў For development projects, the original boundary must conform to the boundaries already established to get the application or perhaps applications getting modified.
My spouse and i nternal Rational File (ILF)
321 Main Streets
Woodbridge, New Jersey 07095
Email: [email protected] com
U producir View
A user is anyone that specifies Functional Consumer
Requirements and any person or thing that communicates or interacts with the software at any time.
A user view presents a formal information of the wearer's
business needs in the user's vocabulary. Developers translate the user information into technology language to supply a solution. An event point rely is completed using the info in a terminology that is popular among both
user(s) and designers.
A user look at is a description of the organization functions; is
approved by the consumer; can be used to depend function details; can vary in physical kind (e. g., catalog of transactions, proposals, requirements doc, external specifications, detailed
specs, user handbook)
User Well-known is a defined requirement for processes and/or sets of data which have been agreed upon, and understood by both
the user and the application developers.
C ounting Boundary
The application border defines what is external towards the
application; is the conceptual software between " internalвЂќ app and " externalвЂќ consumer world; provides a " membraneвЂќ through which info passes in to and out from the application; encloses the rational data preserved by the app; assists in identifying reasonable data referenced by, certainly not maintained within,
An internal reasonable file (ILF) is a customer identifiable selection of logically related data or control information maintained within the boundary in the application. The principal intent of your ILF is usually to hold data maintained through one or more elementary
processes from the application staying counted.
Inner Logical Data files Identification Rules
вЂў The group of data or control information is a logical and user recognizable.
вЂў The group of data is maintained through an primary
process within the application border being counted.
ILF & EIF Info Element (DET) Type Recognition Rules
вЂў Count a DET for each unique end user recognizable, nonrepeated field preserved in or retrieved through the ILF or perhaps EIF through the execution of the elementary method.
вЂў When two applications maintain and reference the same ILF/EIF, although each maintains/references separate DETs,
count the particular DETs being utilized by every single application to size
вЂў Count a DET for every piece of data required by the user to determine a romantic relationship with another ILF or EIF.
ILF & EIF Record Factor Type (RET) Identification Regulation
вЂў Count number an RET for each optional or mandatory subgroup of
the ILF; OR
вЂў If you will discover no subgroups, count the ILF as you RET.
Data Component Types
you вЂ“ nineteen
20 - 50
E xternal Software File (EIF)
An external user interface file (EIF) is a end user identifiable band of logically related data or perhaps control info referenced by the application, but maintained in the boundary of another
program. The primary intent of an EIF is to hold data
referenced through a number of elementary procedures within
the boundary of the application measured. This means a great EIF
counted for a credit application must be within an ILF within