Scribd
Upload
4K views6 pages

Function-Oriented Metrics

Function point analysis is a method of estimating the size of a software by quantifying its functionality based on the number of inputs, outputs, inquiries, interfaces, and files. It was first proposed by Albrecht, who suggested counting these factors and using them in an empirical formula along with complexity adjustment values to calculate the function points of a software. The function points can then be used to determine various quality and productivity metrics of a project such as errors per function point or function points developed per person-month.

Uploaded by

ashu0090
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 PPT, PDF, TXT or read online on Scribd
4K views6 pages

Function-Oriented Metrics

Function point analysis is a method of estimating the size of a software by quantifying its functionality based on the number of inputs, outputs, inquiries, interfaces, and files. It was first proposed by Albrecht, who suggested counting these factors and using them in an empirical formula along with complexity adjustment values to calculate the function points of a software. The function points can then be used to determine various quality and productivity metrics of a project such as errors per function point or function points developed per person-month.

Uploaded by

ashu0090
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 PPT, PDF, TXT or read online on Scribd
You are on page 1/ 6

Function-Oriented Metrics

‘functionality’ cannot be measured directly, it must


be derived indirectly using other direct measures.
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 software's information domain and
assessments of software complexity.
Function Point Table
Explanation of these points
Number of user inputs. Each user input that provides distinct application oriented
data to the software is counted. Inputs should be distinguished from
inquiries, which are counted separately.
Number of user outputs. Each user output that provides application oriented
information to the user is counted. In this context output refers to reports,
screens, error messages, etc. Individual data items within a report
are not counted separately.
Number of user inquiries. An inquiry is defined as an on-line input that
results in the generation of some immediate software response in the form of
an on-line output. Each distinct inquiry is counted.
Number of files. Each logical master file (i.e., a logical grouping of data that
may be one part of a large database or a separate file) is counted.
Number of external interfaces. All machine readable interfaces (e.g., data
files on storage media) that are used to transmit information to another system
are counted.
Compute Function Point
To compute function points (FP), the following
relationship is used:
FP = count total [0.65 + 0.01 Σ(Fi)]

The Fi (i = 1 to 14) are "complexity adjustment


values" based on responses to the following
questions:-
Questions for system complexity
1. Does the system require reliable backup and recovery?
2. Are data communications required?
3. Are there distributed processing functions?
4. Is performance critical?
5. Will the system run in an existing, heavily utilized operational
environment?
6. Does the system require on-line data entry?
7. Does the on-line data entry require the input transaction to be built
over multiple screens or operations?
8. Are the master files updated on-line?
9. Are the inputs, outputs, files, or inquiries complex?
10. Is the internal processing complex?
11. Is the code designed to be reusable?
12. Are conversion and installation included in the design?
13. Is the system designed for multiple installations in different
organizations?
14. Is the application designed to facilitate change and ease of use by
the user?
Each of these questions is answered using a scale that range
from 0 (not important or applicable) to 5 (absolutely
essential). The constant values in Equation (4-1) and the
weighting factors that are applied to information domain
counts are determine empirically.
They are used to determine the quality and productivity of
project:-
• Errors per FP.
• Defects per FP.
• $ per FP.
• Pages of documentation per FP.
• FP per person-month.

You might also like