0% found this document useful (0 votes)
334 views31 pages

Function Point and Cocomo Model

The document discusses function point analysis, a technique developed by Alan Albrecht in the 1970s to measure the size of software projects. It describes the five functional units used in function point analysis - external inputs, external outputs, external inquiries, internal logical files, and external interface files. Each functional unit is assigned a weighting factor based on its complexity. The functional units and their counts are used to calculate the unadjusted function point count. Fourteen general complexity factors are also assessed and combined with the unadjusted count to determine the final function point value. Function points can then be used to measure software productivity, quality, cost, and documentation needs. An example calculation is provided.

Uploaded by

Parinyas Singh
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)
334 views31 pages

Function Point and Cocomo Model

The document discusses function point analysis, a technique developed by Alan Albrecht in the 1970s to measure the size of software projects. It describes the five functional units used in function point analysis - external inputs, external outputs, external inquiries, internal logical files, and external interface files. Each functional unit is assigned a weighting factor based on its complexity. The functional units and their counts are used to calculate the unadjusted function point count. Fourteen general complexity factors are also assessed and combined with the unadjusted count to determine the final function point value. Function points can then be used to measure software productivity, quality, cost, and documentation needs. An example calculation is provided.

Uploaded by

Parinyas Singh
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/ 31

Function Point

Function Count

Alan Albrecht while working for IBM, recognized the problem in size measurement in the 1970s, and developed a technique (which he called Function Point Analysis), which appeared to be a solution to the size measurement problem.

2.Function Count(Cont.)
The principle of Albrechts function point analysis (FPA) is that a system is decomposed into functional units.
Inputs system : information entering the

Outputs
Enquiries

:
:

information leaving the system


requests for instant access to information

Internal logical files


External interface files system system being analyzed.

:
:

information held within the system


information held by other that is used by the
2

2.Function Count(Cont.)
The FPA functional units are shown in figure given below:
Use r

Inquiries

Inputs Use r Output s

ILF

Other application EIF s ILF: Internal logical files EIF: External interfaces

Syste m

Fig. 3: FPAs functional units System


3

2.Function Count(Cont.)
The five functional units are divided in two categories: (i) Data function types
Internal Logical Files (ILF): A user identifiable group of logical related data or control information maintained within the system. External Interface files (EIF): A user identifiable group of logically related data or control information referenced by the system, but maintained within another system. This means that EIF counted for one system, may be an ILF in another system.
4

Software Project Planning


(ii) Transactional function types
External Input (EI): An EI processes data or control information that comes from outside the system. The EI is an elementary process, which is the smallest unit of activity that is meaningful to the end user in the business. External Output (EO): An EO is an elementary process that generate data or control information to be sent outside the system. External Inquiry (EQ): An EQ is an elementary process that is made up to an input-output combination that results in data retrieval.
5

Software Project Planning


Counting function points
Functional Units External Inputs (EI) External Output (EO) External Inquiries (EQ) Internal logical files (ILF) External Interface files (EIF)

Weighting factors Low Average High 3 4 6 4 5 7 3 4 6 7 10 15 5 7 10

Table 1 : Functional units with weighting factors


6

Software Project Planning


Table 2: UFP calculation table
Functional Units External Inputs (EIs) External Outputs (EOs) External Inquiries (EQs)
Count Complexity Low x 3 Average x 4 High x 6 Low x 4 Average x 5 High x 7 Complexity Totals = = = = = = = = = = = = = = =

Functional Unit Totals

Low x 3 Average x 4 High x 6


Low x 7 Average x 10 High x 15 Low x 5 Average x 7 High x 10

External logical Files (ILFs) External Interface Files (EIFs)

Total Unadjusted Function Point Count


7

Software Project Planning


Table 3 : Computing function points.
Rate each factor on a scale of 0 1 to 5. 0 2 3

4 Significant

No Average Incidental Moderat Influence e Number of factors considered ( Fi ) 1. Does the system require reliable backup and recovery ? 2. Is data communication required ?

Essential

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 ? files updated on line ? 8. Are the master 9. Is 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 ?
8

IFPUG Complexity

Software Project Planning


Functions points may compute the following important metrics: Productivity = FP / persons-months Quality = Defects / FP

Cost
Documentation

=
=

Rupees / FP
Pages of documentation per FP

These metrics are controversial and are not universally acceptable. There are standards issued by the International Functions Point User Group (IFPUG, covering the Albrecht method) and the United Kingdom Function Point User Group (UFPGU, covering the MK11 method). An ISO standard for function point method is also being developed.
10

Software Project Planning


Example: 4.1
Consider a project with the following functional units:
Number of user inputs = 50

Number of user outputs


Number of user enquiries Number of user files Number of external interfaces

= 40
= 35 = 06 = 04

Assume all complexity adjustment factors and weighting factors are average. Compute the function points for the

project.
11

12

FP
Solution We know
5 3

UFP Z ij wij
i 1 J 1

UFP = 50 x 4 + 40 x 5 + 35 x 4 + 6 x 10 + 4 x 7 = 200 + 200 + 140 + 60 + 28 = 628 CAF = (0.65 + 0.01 Fi) = (0.65 + 0.01 (14 x 3)) = 0.65 + 0.42 = 1.07 FP = UFP x CAF = 628 x 1.07 = 672

Calculate FP

Table given

You might also like