0% found this document useful (0 votes)
47 views

Function Points

The document discusses function points, a metric for measuring software size. Function points are derived from counts of inputs, outputs, inquiries, files and complexity factors. A formula is provided to calculate the unadjusted function points value based on component counts and complexity weights. An example calculation is also shown.

Uploaded by

Prateek Sharma
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
47 views

Function Points

The document discusses function points, a metric for measuring software size. Function points are derived from counts of inputs, outputs, inquiries, files and complexity factors. A formula is provided to calculate the unadjusted function points value based on component counts and complexity weights. An example calculation is also shown.

Uploaded by

Prateek Sharma
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

FUNCTION POINTS

Function oriented metrics were first proposed by Albrecht [ALB79], who suggested a measure called the function point. Function points are derived using an empirical relationship based on countable [direct] measures of softwares information domain and assessments of software complexity. Formula FP=count total*[0.65+ (0.01* Fi)] Value Adjustment Factor (VAF) Calculation : 0 = No influence 1 = Incidental 2 = Moderate 3 = Average 4 = Significant 5 = Essential Fi F1 General system Characteristics Data communications Adjustment factor How many communication facilities are there to aid in the transfer or exchange of information with the application How are distributed data and processing functions handled? Did the user require response time or throughput? How heavily used is the current hardware platform where the application will be executed? How frequently is 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 online transaction? Does the application have extensive logical or mathematical processing? Was the application developed to meet Value 2

F2 F3 F4

Distributed data Processing Performance Heavily used Configuration

2 3 2

F5 F6 F7 F8 F9 F10

Transaction rate On line data entry End user efficiency On line update Complex processing Reusability

3 0 1 0 3 4

F11 F12 F13

Installation ease Operational ease Multiple sites

F14

Facilitate change

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 install at multiple sites for multiple organizations? Was the application specifically designed, developed and supported to facilitate change? TOTAL

3 3 0

3 29

Unadjusted function point calculation Type of components External inputs External outputs External inquiries External logical files External interface files Total Complexity of components 5*3 4*4 3*3 1*7 3*5 Value 15 16 9 7 15 62

Formula FP = count total*[0.65+ (0.01*Fi)] = 62*[0.65+ (0.01*29)] = 58.28

You might also like