Function Point Analysis

Why Estimate?


A software project estimate, predicts the size of a new project, or the amount of effort required to complete the project An estimate is a prediction based on probabilistic assessment

Factors of Wrong Estimation

  

Lack of formal process Person dependent estimation Inadequate or imprecise and changing requirements Project contract is determined by commercial or political interests There is a natural human tendency to underestimate
3

Sizing Measures
      

KLOC FP Classes Objects Screens Reports

Problems with KLOC as UoM

  

Higher level languages produce less LOC Better programming produce less LOC Actual LOCs are known too late to be used for estimation No consistent method to count LOC especially between languages

What is Function Point?

 

 

Is a structured technique to classifying components of a system Is a method to break systems into smaller components, so they can be better understood and analyzed Measures software by quantifying its functionality provided to the user based primarily on the logical design A standard method for measuring software development from the customer point of view Logical Functionality from a Sophisticated User view rather than a physical view
6

Brief History of FPA

 

 

Developed by Alan Albrecht at IBM in the late 1970s Grew out of an interest in the general problem of measuring productivity in systems development The Function Point was created as an alternative to estimating KLOC Function points exist at a more macro level than KLOC and rely on capturing information such as the number of input transaction type and the number of unique reports to be generated
7

Function Point Counting Process

Function point analysis follows specific steps for counting:  Identification of the subsystem boundaries


Identification of the data functions (internal logical files and external interface files) Identification of transactional functions (external inputs, external outputs and external inquiries) Calculation of the Unadjusted Function Point (UAF) Count Determination of the Value Adjustment Factor (VAF) using General System Characteristics (GSC) Calculation of the final Function Point Count
8

Components of Function Points



Data Function Points

 

Internal Logical Files (ILF) External Interface Files (EIF)

Transaction Function Points

  

External Input (EI) External Output (EO) External Inquiry (EQ)

9

Application Boundaries
Human Resource Application

Background Check (EIF)

New Emp Information (EI)

Emp. Info. (ILF)

Employee Record (EO)

User 1

Request and Display Emp. Info. (EQ) User 1

User 1

10

Definitions


Record Element Type (RET) - A RET is user recognizable sub-group of data elements within an ILF or an EIF. It is best to look at logical groupings of data to help identify them Data Element Type (DET) - A DET is an unique user recognizable, non-recursive fields File Type Referenced (FTR) - A FTR is a file type referenced by a transaction. An FTR must either be Internal Logical File or an External Interface File
11

12

Data Function Points

 

ILF Internal Logical Files EIF External Interface Files Two inputs required
 

RET Record Element Type DET Data Element Type

13

External Inputs

Data crosses from Outside to inside

Data may come from a data input screen or another application The data may be used to maintain one or more internal logical files. The graphic represents a simple EI that updates 2 ILF's (FTR's).

14

EI - External Input


  

It is an elementary process that processes data or control information that comes from outside the application boundary The primary intent of an EI is to maintain one or more ILFs and / or to alter the behavior of the system Each EI will maintain atleast one ILF Transactions are not be confused with file data


Transactions that cause the application files to change are counted as inputs, while files belonging to another application such as master files are not EIs.

15

EI Identification Rules


 

Each unique class of batch transaction is counted as 1 input type, even if many different classes come inside one file structure. These could be different record formats. Add, modify and Delete will be 3 inputs Dont count multiple occurrences of the same unique logical data item more than once, eg. Repeating rows on a screen Count data items not displayed but created as a result of input (error messages, confirmation messages, calculated fields etc) Dont count static information such as constants, screen prompts etc
16

External Outputs
Derived

data crosses from inside to outside

Data creates reports or output files sent to other applications. These reports and files are created from one or more internal logical files and external interface file. The graphic represents a simple EO with two FTRs.

17

EO External Output


It is an elementary process that sends data or control information outside the application boundary The primary intent of an EO is to present information to a user through processing logic other than, or in addition to, the retrieval of data or control information Derived data is the data that is processed beyond direct retrieval and editing of information from ILF or EIF
18

EO Identification Rules


    

The processing logic must contain atleast one mathematical formula or calculation or create derived data It may create report of output files to be sent to another application It uses atleast one ILF or EIF Each unique batch transaction type being sent to another application is counted as 1 type Each medium output is counted as 1 EO Multiple occurrences of the same unique logical data item are not be counted more than once (repeating rows) Static information or system generated information like report headings, data / time stamps, automatic page numbers are not counted
19

External Inquiries
elementary process with both input and output components that result in data retrieval from one or more internal logical files and external interface files. The input process does not update any Internal Logical Files, and the output side does not contain derived data. The graphic below represents an EQ with two ILF's and no derived data.
An

20

EQ External Inquiry


It is an elementary process that sends data or control information outside the application boundary The primary intent of an external inquiry is to present information to a user through the retrieval of data or control information from an ILF or EIF

21

EQ Identification Rules
    

An EQ is made up of input and output It requests immediate retrieval of data and does not result in any updates of ILF EQ may use one or more ILF / EIF An EQ can not have calculated or derived data No ILF is maintained in the process

22

Unadjusted FP


After the components have been classified as one of the five major components (EIs, EOs, EQs, ILFs or EIFs), a ranking of low, average or high is assigned. For transactions (EIs, EOs, EQs) the ranking is based upon the number of files updated or referenced (FTRs) and the number of data element types (DETs). For both ILFs and EIFs files the ranking is based upon record element types (RETs) and data element types (DETs). A record element type is a user recognizable subgroup of data elements within an ILF or EIF. A data element type is a unique user recognizable, nonrecursive, field.
23

Unadjusted FP ..


Each of the following tables assists in the ranking process (the numerical rating is in parentheses). For example, an EI that references or updates 2 File Types Referenced (FTRs) and has 7 data elements would be assigned a ranking of average and associated rating of 4. Where FTRs are the combined number of Internal Logical Files (ILFs) referenced or updated and External Interface Files referenced.

24

Unadjusted FP ..

25

Unadjusted FP ..

26

Unadjusted FP .


Like all components, EQs are rated and scored. Basically, an EQ is rated (Low, Average or High) like an EO, but assigned a value like and EI. The rating is based upon the total number of unique (combined unique input and out sides) data elements (DETs) and the file types referenced (FTRs) (combined unique input and output sides). If the same FTR is used on both the input and output side, then it is counted only one time. If the same DET is used on both the input and output side, then it is only counted one time. For both ILFs and EIFs the number of record element types and the number of data elements types are used to determine a ranking of low, average or high. A Record Element Type is a user recognizable subgroup of data elements within an ILF or EIF. A Data Element Type (DET) is a unique user recognizable, nonrecursive field on an ILF or EIF.
27

Unadjusted FP .

28

Unadjusted FP .


The counts for each level of complexity for each type of component can be entered into a table such as the following one. Each count is multiplied by the numerical rating shown to determine the rated value. The rated values on each row are summed across the table, giving a total value for each type of component. These totals are then summed across the table, giving a total value for each type of component. These totals are then summoned down to arrive at the Total Number of Unadjusted Function Points.
29

Unadjusted FP .

30

VAF


The value adjustment factor (VAF) is based on 14 general system characteristics (GSC's) that rate the general functionality of the application being counted. Each characteristic has associated descriptions that help determine the degrees of influence of the characteristics. The degrees of influence range on a scale of zero to five, from no influence to strong influence. The IFPUG Counting Practices Manual provides detailed evaluation criteria for each of the GSC'S, the table below is intended to provide an overview of each GSC.
31

GSC General System Characteristics



 

There are 14 General System Characteristics (GSCs) that rate the general functionality of the application being counted Each characteristic has associated description that help determine the degree of influence of the characteristics The Degrees of Influence range on a scale of Zero to Five, from no influence to strong influence. The Ratings are:  0 - Not Present, or No Influence  1 - Incidental Influence  2 - Moderate Influence  3 - Average Influence  4 - Significant Influence  5 - Strong Influence Throughout
32

The 14 GSCs 1 thru 8

       

Data communication Distributed data processing Performance Heavily used configuration Transaction rate Online data entry End user efficiency Online update
33

GSC Brief Description

Data communications How many communication facilities are there to aid in the transfer or exchange of information with the application or system? How are distributed data and processing functions handled? Was response time or throughput required by the user? How heavily used is the current hardware platform where the application will be executed? How frequently are transactions executed daily, weekly, monthly, etc.? What percentage of the information is entered OnLine? Was the application designed for end-user efficiency? How many ILFs are updated by On-Line transaction? 34

Distributed data processing Performance Heavily used configuration Transaction rate On-Line data entry End-user efficiency On-Line update

GSC Brief Description

Complex processing Reusability Installation ease Operational ease Multiple sites Does the application have extensive logical or mathematical processing? Was the application developed to meet one or many users needs? How difficult is conversion and installation? How effective and/or automated are start-up, back-up, and recovery procedures? Was the application specifically designed, developed, and supported to be installed at multiple sites for multiple organizations? Was the application specifically designed, developed, and supported to facilitate change?
35

Facilitate change

Calculating Adjusted Function Points



FPC = UFP * VAF

 

Where VAF = [ ( GSC * 0.01) + 0.65] Where

   

FPC Adjusted function point count UFP Unadjusted function points VAF Value adjustment factor GSC Sum total of ratings of all 14 GSCs
36

Estimating Efforts based on Size Estimation



Convert FPC into PDs based on productivity of the technology under consideration Productivity = Size / Efforts Efforts = Size / PRoductivity

37

Mapping Efforts to Schedule

      

Analysis High Level Design Low Level Design Coding Unit Testing Integration & System Testing Project Management

15% 15% 10% 35% 11% 10% 4%

38

Thank You

39

DET Data Element Type



A DET is a unique attribute or a field It has information that is dynamic and not static

40

DET Counting Rules



Count a DET for each unique user recognizable, non-repeating field maintained in the ILF or retrieved from the 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 the ILF / EIF Count each DET for each piece of data required by the user establish relationship with another ILF / EIF
41

RET Record Element Type



A RET is a user recognizable subgroup of data elements within the ILF or EIF Counting Rules


Count a RET for each optional or mandatory subgroup of the ILF / EIF If there are no subgroups, count the ILF or EIF as a RET

42

ILF Internal Logical Files



It is a user identifiable group of logically related data or control information maintained within an application boundary The primary intent of an ILF is to hold data maintained through one or more elementary processes of the application being counted

43

ILF Identification Rules



Group of Data or control information is logical, user identifiable, and fulfils specific user requirements Data is maintained within the application boundary Data is modified via an elementary process (One or more EIs) Has not been counted as an EIF for the application Each ILF is counted only once in the application

44

ILF - Ruling
RET 01 DET 1 19 DET 20 50 DET 51 + LOW LOW AVG

25

LOW

AVG

HIGH

6+

AVG

HIGH

HIGH

45

EIF External Interface File



A user identifiable group of logically related data that resides entirely outside the applications boundary and is not maintained by the application An EIF is an ILF for another application

46

EIF Identification Rules



Group of data or Control information is a logical, user identifiable, and fulfils specific user requirements Group of data is referenced by, and external to, the application being counted Group of data has not been counted as an ILF by the application Each EIF is counted only once in the application
47

EIF - Rating
RET 01 DET 1 19 DET 20 50 DET 51 + LOW LOW AVG

25

LOW

AVG

HIGH

6+

AVG

HIGH

HIGH

48

Things to remember


Stand alone systems will not have an EIF Same file cannot be an ILF and EIF in the same application Same file can be EIF for multiple applications Same file can be ILF for multiple applications, if all these applications are updating the file
49

ILF and EIF



 

Do not count system files, like sort files, index files etc Consider an un-normalized view of the file Any ILF/EIF may become multiple tables after normalization Every EIF must be an ILF in atleast one other application

50

Transaction Function Points



Transaction function points are contributed by

  

External Inputs (EI) External Outputs (EO) External Inquiries (EQ) FTR File Type Referenced DET Data Element Type

Two inputs required

 

51

FTR File Type Referenced



FTR is a file type referenced by a transaction FTR must also be an ILF or EIF Counting Rules
 

Count a FTR for each ILF maintained Count only one FTR for each ILF maintained and read in the transaction
52

EI - Rating
FTR DET 1 - 4 DET 5 - 15 DET 16 +

0-1

LOW

LOW

AVG

LOW

AVG

HIGH

3+

AVG

HIGH

HIGH

53

EO Rating
FTR DET 1 4 DET 5 19 DET 20 +

01

LOW

LOW

AVG

23

LOW

AVG

HIGH

4+

AVG

HIGH

HIGH

54

EQ Rating
FTR DET 1 4 DET 5 19 DET 20 +

01

LOW

LOW

AVG

23

LOW

AVG

HIGH

4+

AVG

HIGH

HIGH

55

Calculating Unadjusted Function Points

Element EI EO EQ ILF EIF Low __ x 3 __ x 4 __ x 3 __ x 7 __ x 5 Average __ x 4 __ x 5 __ x 4 __ x 10 __ x 7 High __ x 6 __ x 7 __ x 6 __ x 15 __ x 10 Total

Unadjusted Function Points (UFP)

56

Recap


Count data function points (data at rest)

 

ILF - Internal Logical Files EIF External Interface Files

Count transaction function points (data on move)

  

EI External Inputs EO External Outputs EQ External Inquiries

57

The 14 GSCs 9 thru 14

     

Complex processing Reusability Installation ease Operational ease Multiple sites Facilitate change

58

Quick FPA


Carried out at a very early stages of project



May be at the time of proposal preparation stage Lack of time Lack of information Difference between High and Low is not much, hence Average is used for calculation Use a judgment call for overall complexity

Carried out because

 

Assumptions


59

Quick FPA - Calculation

   

Identify and count EIs, EOs, EQs, ILFs and EIFs Do not count RETs, DETs and FTRs Classify all functions as average To calculate unadjusted function points, use the coefficients
    

EI 4 EO 5 EQ 4 ILF 10 EIF 7

 

VAF = 0.65 to 1.35 FPC = UFC * VAF

60

Quick FPA - Accuracy



With al information Quick FPA gives a result which is + / - 10 % of detailed FPA It is INEFFECTIVE if used by persons who do not have expertise in detailed FPA

61

Questions ???