Func�on Point Metrics

Func�on Point (FP) Metrics is a standardized method for measuring the func�onal size of so�ware
applica�ons. Developed by Allan Albrecht at IBM in the late 1970s, Func�on Point Analysis (FPA)
quan�fies the func�onality provided to the user based on the requirements, independent of the
technology used for implementa�on. It is widely used for es�ma�ng project size, effort, and cost, as
well as for benchmarking and produc�vity measurement.

Key Components of Func�on Point Metrics

Func�on Points are calculated based on two main categories:

1. Func�onal User Requirements

2. Complexity Adjustment Factors (CAF)

1. Func�onal User Requirements

These represent the features and func�ons the so�ware provides to the user. They are further
divided into five components:

1. External Inputs (EI)

2. External Outputs (EO)

3. External Inquiries (EQ)

4. Internal Logical Files (ILF)

5. External Interface Files (EIF)

Each component is assessed based on its complexity—Low, Average, or High—which is determined

by specific criteria such as the number of data elements and file types referenced.

a. External Inputs (EI)

• Defini�on: User interac�ons where data is entered or modified in the system.

• Examples: Forms, data entry screens, import processes.

b. External Outputs (EO)

• Defini�on: Outputs generated by the system to the user.

• Examples: Reports, messages, data exports.

c. External Inquiries (EQ)

• Defini�on: Interac�ve queries that retrieve data without modifying it.

• Examples: Search opera�ons, order status inquiries.

d. Internal Logical Files (ILF)

• Defini�on: Logical groupings of data maintained within the system.

• Examples: Customer Database, Product Database.

e. External Interface Files (EIF)

 • Defini�on: Logical groupings of data used by the system but maintained externally.

• Examples: External Payment Service Data, Shared Databases.

2. Complexity Adjustment Factors (CAF)

CAF adjusts the unadjusted func�on point count based on 14 general system characteris�cs, such as
data communica�on, performance, security, and more. Each characteris�c is rated on a scale
(typically 0 to 5), and the total adjustment affects the final func�on point count.

Calcula�ng Func�on Points: Step-by-Step Example

Let's walk through an example to illustrate how Func�on Points are calculated.

Scenario:
You are tasked with es�ma�ng the size of a simple web-based order processing system.

Step 1: Iden�fy and Count Func�onal Components

Suppose the system has the following:

• External Inputs (EI): 5

o Order Entry

o Customer Registra�on

o Product Addi�on

o Order Modifica�on

o Payment Processing

• External Outputs (EO): 4

o Order Confirma�on

o Invoice Genera�on

o Sales Report

o Shipment No�fica�on

• External Inquiries (EQ): 3

o Order Status Inquiry

o Product Search

o Customer Lookup

• Internal Logical Files (ILF): 2

o Customer Database

o Product Database

• External Interface Files (EIF): 1

o External Payment Service Data

Step 2: Determine Complexity of Each Component

Assume the following complexity ra�ngs based on criteria such as the number of data elements and
file references:

• External Inputs (EI):

o 3 Low Complexity

o 2 Average Complexity

• External Outputs (EO):

o 2 Low Complexity

o 2 High Complexity

• External Inquiries (EQ):

o 1 Low Complexity

o 2 Average Complexity

• Internal Logical Files (ILF):

o 2 Average Complexity

• External Interface Files (EIF):

o 1 Low Complexity

Step 4: Calculate Unadjusted Func�on Points (UFP)

Mul�ply the count of each component by its assigned FP based on complexity:

• External Inputs (EI):

o 3 Low × 3 FP = 9 FP

o 2 Average × 4 FP = 8 FP

o Total EI = 17 FP

• External Outputs (EO):

o 2 Low × 4 FP = 8 FP

o 2 High × 7 FP = 14 FP
 o Total EO = 22 FP

• External Inquiries (EQ):

o 1 Low × 3 FP = 3 FP

o 2 Average × 4 FP = 8 FP

o Total EQ = 11 FP

• Internal Logical Files (ILF):

o 2 Average × 10 FP = 20 FP

o Total ILF = 20 FP

• External Interface Files (EIF):

o 1 Low × 5 FP = 5 FP

o Total EIF = 5 FP

• Unadjusted Func�on Points (UFP):

o 17 (EI) + 22 (EO) + 11 (EQ) + 20 (ILF) + 5 (EIF) = 75 FP

Func�on Points (FP)

• What They Measure: Func�on Points quan�fy the func�onal size of a so�ware applica�on
based on the func�onality provided to the user. This includes user interac�ons, data
processing, and data storage.

• Purpose: FP is used to es�mate the effort, �me, and cost required to develop or maintain a
so�ware system. It provides a high-level measure of so�ware func�onality independent of
the technology used.

Lines of Code (LOC)

• What They Measure: Lines of Code count the number of lines in the source code of a
so�ware applica�on. This includes all executable statements, declara�ons, and some�mes
comments and blank lines, depending on the coun�ng method.
• Purpose: LOC is o�en used as a metric for measuring the size, complexity, and produc�vity of
a so�ware project. It can also be used to es�mate maintenance efforts and assess code
quality.