Software Engineering (22413)

Experiment No 11

Evaluate size of the project using Function point metric for the assigned project.

I Practical Significance

Function points are one of the most widely used measures of software size. The basis of
function points is that the "functionality” of the system that is; what the system performs, is the
measure of the system size. In function points, the system functionally is calculated in terms of the
number of function it implements, the number of inputs, the number of output etc.

II Relevant Program Outcomes

All POs are listed.

III Relevant Course Outcomes

Calculate the size of the project using Function point metric for the assigned project.

IV Practical Learning Outcomes

Detailed descriptions of all aspects of the project to be understand.

V Practical Skills
Deeper understanding of various measures is used in project size estimation.

VI Minimum Theoretical Background

The initial design criteria for function points were to provide a mechanism that both software
developers and users could utilize to define functional requirements. It was determined that the best
way to gain an understanding of the users' needs was to approach their problem from the perspective of
how they view the results an automated system produces. Therefore, one of the primary goals of
Function Point Analysis is to evaluate a system's capabilities from a user's point of view. To achieve this
goal, the analysis is based upon the various ways users interact with computerized systems. From a
user's perspective a system assists them in doing their job by providing five basic functions.
Two of these address the data requirements of an end user and are referred to as Data Functions.
The remaining three addresses the user's need to access data and are referred to as Transactional
Functions.

The Five Components of Function Points

Data Functions

 Internal Logical Files

 External Interface Files

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

Transactional Functions

 External Inputs
 External Outputs
 External Inquiries

Internal Logical Files - The first data function allows users to utilize data they are responsible for
maintaining. For example, a pilot may enter navigational data through a display in the cockpit prior to
departure. The data is stored in a file for use and can be modified during the mission. Therefore the pilot
is responsible for maintaining the file that contains the navigational information. Logical groupings of
data in a system, maintained by an end user, are referred to as Internal Logical Files (ILF).

External Interface Files - The second Data Function a system provides an end user is also related to
logical groupings of data. In this case the user is not responsible for maintaining the data. The data
resides in another system and is maintained by another user or system. The user of the system being
counted requires this data for reference purposes only. For example, it may be necessary for a pilot to
reference position data from a satellite or ground-based facility during flight. The pilot does not have the
responsibility for updating data at these sites but must reference it during the flight. Groupings of data
from another system that are used only for reference purposes are defined as External Interface Files
(EIF).

The remaining functions address the user's capability to access the data contained in ILFs and EIFs. This
capability includes maintaining, inquiring and outputting of data. These are referred to as Transactional
Functions.

External Input - The first Transactional Function allows a user to maintain Internal Logical Files (ILFs)
through the ability to add, change and delete the data. For example, a pilot can add, change and delete
navigational information prior to and during the mission.

In this case the pilot is utilizing a transaction referred to as an External Input (EI). An External Input gives
the user the capability to maintain the data in ILF's through adding, changing and deleting its contents.

External Output - The next Transactional Function gives the user the ability to produce outputs. For
example a pilot has the ability to separately display ground speed, true air speed and calibrated air
speed. The results displayed are derived using data that is maintained and data that is referenced. In
function point terminology the resulting display is called an External Output (EO).

External Inquiries - The final capability provided to users through a computerized system addresses the
requirement to select and display specific data from files. To accomplish this a user inputs selection
information that is used to retrieve data that meets the specific criteria. In this situation there is no
manipulation of the data. It is a direct retrieval of information contained on the files. For example if a
pilot displays terrain clearance data that was previously set, the resulting output is the direct retrieval of
stored information. These transactions are referred to as External Inquiries (EQ).

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

FPs of an application is found out by counting the number and types of functions used in the
applications. Various functions used in an application can be put under five types as shown in Table.

Types of FP Attributes

VII Resources required

Sr No Instrument Specification Quantity Remarks

Any Desktop PC
1 Computer System with attached 10 No. Whichever is available
HardDisk

http://groups.umd.umich.edu/cis/course.des/cis375/projects/fp99/main.html use for Function

Point Calculator.

VIII Procedure

In Function Point Analysis method, the number and type of functions supported by the software
are utilized to find FPC(function point count). The steps in function point analysis are:

1. Count the number of functions of each proposed type.

2. Compute the Unadjusted Function Points(UFP).
3. Find Total Degree of Influence(TDI).
4. Compute Value Adjustment Factor(VAF).
5. Find the Function Point Count(FPC).

IX Precautions

1. Change the requirement carefully.

2. Save changes if required under the guidance of teacher.

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

X Description

The functional complexities are multiplied with the corresponding weights against each function and the
values are added up to determine the UFP (Unadjusted Function Point) of the subsystem.

Fig: Computing FPs

The weighing factor will be simple, average or complex for a measurement parameter type.

The Function Point (FP) is thus calculated with the following formula

FP = Count-total * [0.65 + 0.01 * S(Fi ) ]

where Count-total is obtained from the above Table.

and

S(Fi ) is the sum of all 14 questionnaires and show the complexity adjustment value/ factor-CAF (where i
ranges from 1 to 14). Usually, a student is provided with the value of S (Fi ).

Also note that S (Fi ) ranges from 0 to 70,

i.e., 0 <= S (Fi) <=70.

Based on the FP measure of software many other metrics can be computed:

(a) Cost per function = cost/ productivity

(b) Cost=$/FP.

(c) Quality=Number of Faults/FP

(d) Documentation=Pages of documentation/FP

(e) Productivity = FP/PM (effort is measured in person-months).

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

XI Practical related Questions

1. Compute the function point value for a project with the following information domain
characteristics:
(1) No. of user inputs = 32
(2) No. of user outputs = 60
(3) No. of user inquiries = 24
(4) No. of files = 8
(5) No. of external interfaces = 2
Assume all complexity adjustment values are average (Fi for average case = 3). Assume
that 14 algorithms have been counted.

Ans. Note: here,

Fi for average case = 3. So sum of all Fi (i ¨ 1 to 14) = 14 * 3 = 42.

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

2. Compute the function point, productivity, documentation, cost per function for the following data:

(1) Number of user inputs = 24

(2) Number of user outputs = 46

(3) Number of inquiries = 8

(4) Number of files = 4

(5) Number of external interfaces = 2

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

(6) Effort = 36.9 p-m

(7) Technical documents = 265 pages

(8) User documents = 122 pages

(9) Cost = $7744/ month

Various processing complexity factors are: 4, 1, 0, 3, 3, 5, 4, 4, 3, 3, 2, 2, 4, 5.

Ans:

(Note: sum of all Fi (i ¨ 1 to 14) = 4 + 1 + 0 + 3 + 5 + 4 + 4 + 3 + 3 + 2 + 2 + 4 + 5 = 43 )

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

3. Compute the function point value for a project with the following information domain
characteristics:

(1) No. of user inputs = 30

(2) No. of user outputs = 20

(3) No. of user inquiries = 08

(4) No. of files = 7

(5) No. of external interfaces = 6

Assume all complexity adjustment values are moderate and 14 algorithms have been counted.

Ans: (Note: Fi for moderate case = 2. So sum of all Fi (i ¨ 1 to 14) = 14 * 2 = 28)

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

4. Consider a project with the following functional units :

 Number of user inputs = 50

 Number of user outputs = 40

 Number of user enquiries = 35

 Number of user files = 06

 Number of external interfaces = 04

Assuming all complexity adjustment factors and weighing factors as average, Determine adjusted
function points assuming complexity adjustment value is 32.

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

List Of Student Team Members:

1. …………………………………………………………………………………………………
2. …………………………………………………………………………………………………
3. …………………………………………………………………………………………………
Marks Obtained Signature Of
Teacher
Process Product Total (25)
Related(15) Related(10)

Marathwada Mitra Mandal’s Polytechnic,Thergaon.