Function Point Analysis - Examples

Pranay Srivastava
Feb 2008

Example 1 - User Requirement

Analysis of user security requirements showed a need
for audit data:
 Allow or deny user access to each screen in the
application.
 Change a user's access to each screen.
 Report on any screen security added or changed using :
 Identification of user who is adding or changing security
information
 User and screen security that was added or changed
 User and screen security before and after a change was made
 Date and time the add or change occurred.
 Capture audit data to monitor and report daily security
activity. This requirement was determined when a design
was implemented to satisfy the user's screen security
requirements.
Example 1 – Data Flow Diagram

Data Count Example

Example 1 – ILF Screen Security Audit

Is the data-set self contained? No

Is the data-set logical? Yes
Is the data-set user identifiable? Yes
Is the data-set maintained by the Yes
current application?

Data is integral part of screen security

Not Counted as an ILF

Example 1 – ILF Screen Security

Is the data-set self contained? Yes

Is the data-set logical? Yes
Is the data-set user identifiable? Yes
Is the data-set maintained by the Yes
current application?

Counted as an ILF
Example 1 – ILF Employee Security

Is the data-set self contained? Yes

Is the data-set logical? Yes
Is the data-set user identifiable? Yes
Is the data-set maintained by the Yes
current application?

Counted as an ILF

Transaction Count Example

 Example 2 – EI Add screen security

Is the data coming from outside the Yes

application?
Is atleast one ILF maintained (except Yes. Screen
for control information)? security
Is the processing logic is unique? Yes
Are the data elements unique? Yes
Are the ILFs/EIFs referenced unique? Yes

Counted as an EI

Example 2 – EI Change screen security

Is the data coming from outside the Yes

application?
Is atleast one ILF maintained (except Yes. Screen
for control information)? security
Is the processing logic is unique? Yes
Are the data elements unique? Yes
Are the ILFs/EIFs referenced unique? Yes

Isn’t the processing logic same as Add?

Aren’t the data set same as Add?

Counted as an EI
Example 2 – EQ Report security changes

Is the data going out from inside the Yes

application?
Is the processing logic is unique? Yes
Are the data set elements unique? Yes
Is the ILFs/EIFs referenced unique? Yes
Is the data retrieved from ILF/EIF? Yes

Does it create derived data? No

Does it maintain an ILF? No
Does it alter the systems behavior? No

Counted as an EQ

Example 2 – EI Add Employee security

Is the data coming from outside the Yes

application?
Is atleast one ILF maintained (except Employee
for control information)? security
Is the processing logic is unique? Yes
Are the data elements unique? Yes
Are the ILFs/EIFs referenced unique? Yes

Counted as an EI
Example 2 – EI Change Employee security

Is the data coming from outside the Yes

application?
Is atleast one ILF maintained (except Employee
for control information)? security
Is the processing logic is unique? Yes
Are the data elements unique? Yes
Are the ILFs/EIFs referenced unique? Yes

Counted as an EI

Example 1 - Summary

ILF
 Screen security
 Employee security

EI
 Add screen security
 Change screen security
 Add employee security
 Change employee security

EQ
 Report security changes.