0% found this document useful (0 votes)
8 views4 pages

Practical 11

This document discusses using the function point metric to evaluate the size of a software project. It describes the function point metric process, which involves counting types of functions, calculating unadjusted function points, determining a total degree of influence, computing a value adjustment factor, and calculating the final function point count.

Uploaded by

geet.more15
Copyright
© © All Rights Reserved
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)
8 views4 pages

Practical 11

This document discusses using the function point metric to evaluate the size of a software project. It describes the function point metric process, which involves counting types of functions, calculating unadjusted function points, determining a total degree of influence, computing a value adjustment factor, and calculating the final function point count.

Uploaded by

geet.more15
Copyright
© © All Rights Reserved
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/ 4

Practical 11

Title: Evaluate the size of project using function point metric for assigned project.

Theory:
The FP metric can be used effectively asa means for measuring the functionality
delivered by a system. Using historical data the FP metric can be used to
1. estimate cost or effort required to design, code and test software.
2. Predict the number of errors that will be encountered during testing.
3. forecast the number of components and/ aur the number of protected source lines in implemented
system.

FP's are derived using an empirical relationship based on countable measures of software information
domain quantitative assessments of software complexity.

The Matric examine the requirements model with the intent of predicting size of resultant system.
Size is sometimes an indicator of design complexity and is almost always an indicator of increased
coding, integration and testing effort.
To illustrate the use of FP metric in this context, we consider a simple analysis model representation,
illustrated in figure. Referring to the figure a DFD for a function within the Safe home software is
represented.
Test sensors
Sensors
Password
U Zone Enquiry
Safe Home User
Sensor Enquiry Messages User
S Panic Button
Interaction
Function
Activat/Deactivate

E Activate/Deactivate
Alarm Alert
Monitoring
And
Response

R Password, Sensors..
Sub-System

System Configuration
Data

The function manages user interaction accepting a user password to activate or deactivate the system
and allows inquiries on the status of security zones and various security sensors. the function displays
a series of prompting messages and sends appropriate control signals to various components of
security system. The DFD is evaluated to determine a Set of key information domain measures
required for computation of FP metric.
three external inputs password, panic button and activate/ deactivate are shown in the figure along
with two external enquiries.-zone enquiry and sensor enquiry.
1 ILF( system configuration file) is shown. Two external outputs( messages and sensor status) and 4
ELF's( test sensor, zone setting, activate/ deactivate and alarm alert) are also present. This data, along
with appropriate complexity are shown in the figure below.

The count total shown in figure must be adjusted using equation


FP= count total X (0.65+ 0.01X £(Fi))
for the Purpose of this example we assume that £(fi) is 46<[ a moderately complex product]
Thus FP= 50 x [0.65 + a(0.01 X 46)]=56

Information DomainValue Count Weighing Factors


Simple Average Complex
External Inputs(EI’s) 3 X3 4 6
External Outputs(EO’s) 2 X4 5 7
External Inquiries(EQ’s) 2 X3 4 6
Internal Logic Files(ELF’s) 1 X7 10 15
External interface files 4 X5 7 10
Count Total= 50

Procedure:
Function point analysis -
The number and type of functions supported by the software are utilised to find FPC ( function point
count).
The steps in FP analysis are:
1. Count the number of functions of each proposed type
2. Compute the unadjusted function point
3. Find total degree of influence(TDI)
4. Compute value adjustment factor (VAF)
5. Find the function point count(FPC)

The explanation of above points are given below:


1. Count the number of functions of each proposed type –
find the number of functions belonging to the following types:
External INPUTS- information entering the system
External output -- information leaving the system

External enquiries -- request for instant access to system


Internal logical files -- information held within the system

External interface files-- information held by other system that is used by the system being analysed.

2. Computer the an adjusted function points (UFP) :


Categorize each of the 5 function types as simple, average or complex based on their complexity.
Multiply count of each function type with its weighing factor and find weighted sum.
The weighing factors for each type based on their complexity are as follows:
Functional unit weighing factors

Functional units Weighing Factors


Simple Average Complex
External Inputs(EI’s) 3 4 6
External Outputs(EO’s) 4 5 7
External Inquiries(EQ’s) 3 4 6
Internal Logic Files(ELF’s) 7 10 15
External interface files 5 7 10

3. Find total Degree of Influence --


Use the 14 general characteristics of a system to find total degree of influenceTDI of each of them.
The sum of all 14 degrees of influences will give the TDI.
The range of TDI is 0 to 70

The 14 general characteristics are:


1. Data communication
2. Distributed data processing
3. Performance
4. Heavily used configuration
5. Transaction rate
6 online data entry
7. End user efficiency
8. Online update
9. Complex processing
10. Reusability
11 installation ease
12 operational ease
13 multiple site
14 facilitate change

4) compute value adjustment factor VAF


VAF = (TDI * 0.01) + 0.65

5) find the function point count(FPC)


FPC = UFP * VAF

Conclusion:
Thus we have studied function point metric used in Software cost estimation.

You might also like