Scribd
Upload
69 views

SPM Function Point

Functional point analysis (FPA) is a metric used to estimate the size of a software by quantifying various factors of the software. It measures the functionality of the software based on the number of inputs, outputs, inquiries, files and interfaces. The benefits of FPA include better project estimation, scope management and making informed decisions. FPA helps describe a project's complexity and timelines independently of the technology used.

Uploaded by

RYUK -
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
69 views

SPM Function Point

Functional point analysis (FPA) is a metric used to estimate the size of a software by quantifying various factors of the software. It measures the functionality of the software based on the number of inputs, outputs, inquiries, files and interfaces. The benefits of FPA include better project estimation, scope management and making informed decisions. FPA helps describe a project's complexity and timelines independently of the technology used.

Uploaded by

RYUK -
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 21

SOFTWARE

PROJECT
MANAGEMENT
Course Co-ordinator : DOLLY DAS
Designation: Assistant Professor , SCSET,
BU
Cubicle No. : M310
PROJECT MANAGEMENT - Module
1
Function Point Calculation (FPC)
Developed by Allan J. Albrecht in 1979 at IBM
Dimensionless number in function points
A relative measure of function value delivered to
customer.
Objectives of FPA:
Encourage Approximation: Estimation of the work, time and materials needed
to develop a software project.

To assist with project management: Monitor and manage software development


projects, and to evaluate productivity, monitor progress, and make well-informed
decisions about resource allocation and project timeframes

Comparative analysis: Ability to assess how their software projects measure up


to industry standards or best practices in terms of size and complexity.

Improve Your Cost-Benefit Analysis: Assess the value provided by the program
in respect to its size and complexity, for cost-benefit analysis.

Comply with Business Objectives: It assists in coordinating software


development activities with an organization’s business objectives.
Types of FPA
Transactional Functional Type
• External Input (EI): EI processes data or control
information that comes from outside the application’s
boundary. The EI is an elementary process.
• External Output (EO): EO is an elementary process that
generates data or control information sent outside the
application’s boundary.
• External Inquiries (EQ): EQ is an elementary process
made up of an input-output combination that results in data
retrieval.
Types of FPA
Data Functional Type
• Internal Logical File (ILF): A user-identifiable group of
logically related data or control information maintained
within the boundary of the application.
• External Interface File (EIF): A group of users
recognizable logically related data allusion to the software
but maintained within the boundary of another software.
Benefits of Functional Point Analysis
Technological Independence: Computes functional size independent of the
underlying technology or programming language , and a metric to compare projects

Better Accurate Project Estimation: Improve project estimation accuracy by


measuring user interactions and functional needs, and estimate the time, effort and
resources required for development.

Improved Interaction: Improve communication gap between business analysts,


developers, and project managers and other stakeholders.
Benefits of Functional Point Analysis
•Making Well-Informed Decisions: FPA assists in making well-
informed decisions at stages such as resource allocation, project
prioritization, and technology selection.
•Early Recognition of Changes in Scope: Better scope change
management is made possible by the measurement of functional
requirements, and to evaluate additions and their effect on the
project’s overall size.
Characteristics of Functional Point
Analysis
Functional Point helps in describing system complexity and also
shows project timelines. It is majorly used for business systems
like Measurement
information systems.
Parameters Examples

Number of External Inputs (EI) Input screen and tables

Number of External Output (EO) Output screens and reports

Number of external inquiries (EQ) Prompts and interrupts

Number of internal files (ILF) Databases and directories

Number of external interfaces (EIF) Shared databases and shared routines


Weights of 5 Functional Point Attributes
Measurement
Low Average High
Parameter
Number of external
3 4 6
inputs (EI)
Number of external
4 5 7
outputs (EO)
Number of external
3 4 6
inquiries (EQ)
Number of internal files
7 10 15
(ILF)
Number of External
5 7 10
Interfaces (EIF)
Functional Complexities helps in finding corresponding weights, and
Unadjusted Functional point (UFp) of the Subsystem. Consider the
complexity as average for all cases. Below-mentioned is the way how
to compute FP.
Measurement Count Weighing Factor
Total_Count Simple Average Low Average High
Number of external 4 6
32 32*4=128 3
inputs (EI)
Number of external 5 7
60 60*5=300 4
outputs (EO)
Number of external 4 6
24 24*4=96 3
inquiries (EQ)
Number of internal 10 15
8 8*10=80 7
files (ILF)
Number of external 7 10
2 2*7=14 5
interfaces (EIF)
Algorithms used
Computation of Functional
From the above tables, FP Point is calculated with the
following formula
FP = Count-Total * [0.65 + 0.01 * ⅀(fi)]
= Count * CAF
Here, the count-total is taken from the chart.
CAF = [0.65 + 0.01 * ⅀(fi)]
1.⅀(fi) = sum of all 14 questions and it also shows the
complexity factor – CAF.
2.CAF varies from 0.65 to 1.35 and ⅀(fi) ranges from 0 to 70.
3.When ⅀(fi) = 0, CAF = 0.65 and when ⅀(fi) = 70, CAF = 0.65
+ (0.01*70) = 0.65 + 0.7 = 1.35
User Inputs EI: Password, Panic
Button, Activate/Deactivate = 3

User Outputs EO : Messages and


Sensor Status = 2

User Inquiries EI = Zone inquiry,


sensor inquiry = 2

Internal Logical File ILF = System


Configuration Data = 1

External Interface File EIF = Test


sensor, zone setting,
Activate/deactivate, and alarm
alert = 4

Data Flow Diagram (DFD) of SafeHome User Interaction Function


1 FP = 60 Lines of Code (LOC)
12 FPs are produced for each person-
month effort

Provides project manager with input and


planning information, based on
requirements rather than preliminary
estimates.

FP helps in estimating the LOC required


to develop the project, probability errors,
effort required, development time etc.
PROJECT ESTIMATION

You might also like