Practical 11
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.
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)
External interface files-- information held by other system that is used by the system being analysed.
Conclusion:
Thus we have studied function point metric used in Software cost estimation.