Function Point Training January 2006

January 2006

Agenda
Objectives Describe the 5 Function Point Types Counting Rules Steps to follow for each elementary process F.P. Example & Excel Spreadsheet Business Logic Process to follow Questions and Comments

January 2006

Objectives
Explain what is required for FP counting
Explain the Process to follow Explain how to complete the FP Spreadsheet

January 2006

FP Overview
Functionality as viewed from the users perspective
Screen add/change/delete File Input External Input

5 function types
External Interface Files Table-External

Application Being Considered

External Output or External Inquiry

Internal Logical File

Other Applications Table-Internal File Output (master files)

Screen display
Report

January 2006

Description of Data Function Types

Internal Logical File - ILF (Table-Internal or master files) Logical grouping of data maintained by the application being counted (e.g., employee file)

The primary intent is to hold data maintained through one or more elementary processes of the application

January 2006

Description of Data Function Types

External Interface File - EIF (Table-External) Logical group of data referenced but not maintained by the application being counted (e.g., Global Postal Code table) The primary intent is to hold data referenced through one or more elementary processes of the application

January 2006

FP Data Count
For Internal Logic Files and External Interface Files (ILF/EIF) (db2 tables and master files)

Record Element Type (RET) Name of the table (master file) Employee Number of logical files 1

Data Element Type (DET) Number of fields 20

January 2006

Function Point Terms

Record Element Type - RET (number of logical files)

User recognizable subgroup of data elements within a logical file

Data Element Type DET (Number of Fields) Unique, user recognizable, non-repeated field (on input/output file, report and DB)

January 2006

Description of Transaction Function types

External Input - EI (Screen add/chg/del & Input file)
An elementary process that processes data or control information that comes from outside the application The primary intent is to maintain one or more ILFs and/or alter the behavior of the system Processed control information may or may not maintain an ILF

(see rules)

January 2006

Description of Transaction Function types

External Output - EO (File Output, Report & Screen View)
An elementary process that sends data or control information outside the application boundary The primary intent is to present information to a user through processing logic

The processing logic must contain al least one mathematical formula or calculation
(see rules)
January 2006 10

Description of Transaction Function types

External Inquiry - EQ (File Output, Report & Screen View)
An elementary process that sends data or control information outside the application boundary The primary intent is to present information to a user through the retrieval of data or control

The processing logic contains no mathematical formulas or calculations

(see rules)
January 2006 11

Functions & Primary Intent

Summary of functions performed by EIs, EOs, and EQs

Transaction Function Type Functions

Alter the behavior of the system Maintain one or more ILF Present information to the user

EI
PI PI F

EO
F F PI

EQ
N/A N/A PI

PI F N/A
January 2006

the primary intent of the transaction type a function of the transaction function type, but is not the primary intent and is sometimes present the function is not allowed by the transaction function type
12

FP Data Count
For External Input/External Output/External Inquiry (EI,EO,EQ) (file inputs/file outputs/screens/reports)

File Type Referenced (FTR) Name of the file/screen/report

Report X

Data Element Type (DET) Number of fields on the input (or output)
30

Number of tables (master files) accessed or updated

2

January 2006

13

Function Point Terms

File Type Referenced FTR (Number of Tables/files)

A logical file (db2 table or master file) read or maintained by a transaction, output file or report

Data Element Type DET (Number of Fields) Unique, user recognizable, non-repeated field (on input/output file, report and DB)

January 2006

14

Example of DET calculation - Report

Unique, user recognizable, non-repeated field (on input/output file and report)
# fields 1&2 3 to 7

Example (report): Customer name: M Worsley customer number: 12345 Order item # Item Description Price Quantity Cost 1234 Paper clips 0.10 100 $10.00 2345 Pencil 0.20 100 $20.00 Total: $30.00

FTR Number of tables 2

DET / number of fields 8 (output contains calculated field)

Customers order & items price)

January 2006

15

Example of DET calculation - Screen

# fields
Add X Change Delete Customer First Name: Martha Last Name: Worsley Address: XXXXXXXXXXX City: xxxxxxxxxxxxxxxxxxxxx Postal Code: xxxxxxxxxx Phone number: xxx-xxx-xxxx Error Message: xxxxxxxxxxxx
1 2&3 4 5

6
7 8

FTR DET Number of tables / number of fields 2 8 (customers information & error message)

January 2006

16

F.P. Complexity
Internal Logical File (ILF) & External Interface File (EIF) (Table-Internal & Table-External - db2 tables & master files)

RET # of tables/files

DET # fields 1 to 19

DET # fields 19 to 50 Low

DET # fields >50 Average

Low

2 to 5
6 or more

Low
Average

Average
High

High
High

Low= 7 FP

Average= 10 FP

High= 15 FP

January 2006

17

F.P. Complexity
External Input (EI) (screen add/change/delete and input file) FTR DET DET DET

# of tables/files read/updated

# fields
1 to 4

# fields
5 to 15 Low Average High

# fields
>15 Average High High

1 2 3 or more

Low Low Average

Low= 3 FP

Average= 4 FP

High= 6 FP

January 2006

18

F.P. Complexity
External Output (EO) & External Inquiry (EQ) (File Output/Report/Screen View) FTR DET DET DET

# of tables/files read

# fields
1 to 5

# fields
6 to 19 Low Average High

# fields
>19 Average High High

1 2 to 3 4 or more

Low Low Average

Low= 4 FP

Average= 5 FP

High= 7 FP

(Can use >19 for # fields) (must indicate calculated fields = Yes or No in column 10 or J)
January 2006 19

Counting Rules
Elementary Process Counting Rules: The process is the smallest unit of activity that is meaningful to the user The process is self-containing and leaves the business of the application in a consistent state

January 2006

20

6 Types of Rules
Rules to determine Elementary Process Rules for EI (External Input) Rules for EO (External Output) Rules for EQ (External Inquiry) Rules for FTR (db2 tables, master files) Rules for DET (# fields)

(see rules file)

January 2006

21

Steps to follow for each elementary process

Step 1 Identify the elementary process Step 2 Determine the Primary Intent (EI/EO/EQ) (see page 11) Step 3 Validate against the counting rules (EI/EO/EQ) Step 4 Count the FTR (db2 tables/master files) Step 5 Count the DET (number of fields) Step 6 Enter information on FP spreadsheet

January 2006

22

FP Excel Spreadsheet
RET / FTR FP Type Function Type (12 or L) Table - Internal Table - External (FSI) Number of Tables read or updated (16 or P) 1 1 DET Number of Fields read or updated (18 or R) 10 20

ILF EIF

EI
EI EI EQ

Screen - Add
Screen - Change Screen - Delete Screen - View

2
2 2 3

10
15 10 20

EI
EO or EQ EO or EQ
January 2006

File - Input
File - Output Report

2
5 5

10
10 10
23

F.P. Example 1
Requirement: 1. Load city file received from application A into our application (file input)

2. Produce a list of cities loaded (report)

3. Send list of cities to application B (file output).

Change Type (11 or K)

Function Type (12 or L)

Does it contain calculated fields (13 or M)

Number of Tables read or updated (16 or P)

1 1

Number of Fields read or updated (18 or R)

2 2 2 2
24

new new new new

January 2006

Table - Internal File - Input Report File - Output N N

1 1

F.P. Example 2
Requirement:

User wants the capability to: a)add a new city code (screen add)

b)change the description for the city (screen change) c)delete a city (screen delete) e)view all cities in the application (screen view).

January 2006

25

F.P. Example 2
Change Type (11 or K) Function Type (12 or L) Does it contain calculated fields (13 or M) Number of Tables read or updated (16 or P) Number of Fields read or updated (18 or R)

new

Screen add

new new
new

Screen change Screen delete

Screen view

1 1
1

4 4
2

January 2006

26

F.P. Excel Spreadsheet

View FP Excel Spreadsheet

January 2006

27

New columns on the FP spreadsheet

Column I (9) FP validated by: Initial or name of the AM resource that validated the FP information This person will be the contact for the FP analyst when more information is required
Column J (10) Business Logic Change (Y/N): Identifies either the change is due to a business logic change that was requested by the user or that it was not.

January 2006

28

What is a Business Logic Change?

A request from the customer that would: Change a calculation Change the validation Change the selection criteria Change the length of a field Resort or rearrange data on a report or file etc
If its a request from the customer, most likely its a business logic change

January 2006

29

What is NOT a Business Logic Change?

Correct programming logic error (unless requested by customer) Improve performance (unless requested by customer) Produce a Sizing only Produce documentation of application Testing only etc

January 2006

30

Business Logic Change

Question: What to enter on the FP spreadsheet? All functions that you have to test (verify)
Note: a)The count for columns O & P (number of tables/master files used before the change and after the change) will be the same. b)The count for columns Q & R (number of fields before the change and after the change) will be the same. c)In the remarks column (S or 19) enter Logic change with a description of the change.
January 2006 31

F.P. PROCESS
Practitioner

After completion of SR/TR, completes the Excel Spreadsheet (If only the logic was changed then enter Logic change in Remarks with a description of the change) Sends Excel Spreadsheet to Team Leader/Coordinator (or copies it to the shared drive)
See document Function Point Counting Process Guide for Maintenance (SR/TR).

January 2006

32

F.P. PROCESS
Team Leader/Coordinator

Collects Excel Spreadsheet Validates the FP information or assigns it to someone from the team to validate it (enters name in column I) Merges information by RFS/TR number Add information about RFS/TR (e.g. actual effort days) Completes column J Business Logic change (yes or no) Sends FP Spreadsheet to F.P. Analyst (5th working day)

See document Function Point Counting Process Guide for Maintenance (SR/TR).

January 2006

33

Questions and Comments

January 2006

34