Function Point Analysis Function Point Analysis -- ExamplesExamplesPranay Srivastava Pranay Srivastava

Feb 2008Feb 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

Data is integral part of screen security

� Not Counted as an ILF

Is the data-set self contained?

Is the data-set maintained by the current application?

Is the data-set user identifiable?

Is the data-set logical?

Yes

Yes

Yes

No

Example 1 – ILF Screen Security

� Counted as an ILF

Is the data-set self contained?

Is the data-set maintained by the current application?

Is the data-set user identifiable?

Is the data-set logical?

Yes

Yes

Yes

Yes

Example 1 – ILF Employee Security

� Counted as an ILF

Is the data-set self contained?

Is the data-set maintained by the current application?

Is the data-set user identifiable?

Is the data-set logical?

Yes

Yes

Yes

Yes

Transaction Count Example

Example 2 – EI Add screen security

� Counted as an EI

Are the ILFs/EIFs referenced unique?

Are the data elements unique?

Is the processing logic is unique?

Is atleast one ILF maintained (except for control information)?

Is the data coming from outside the application?

Yes

Yes

Yes

Yes. Screen security

Yes

Example 2 – EI Change screen security

� Isn’t the processing logic same as Add?

� Aren’t the data set same as Add?

� Counted as an EI

Are the ILFs/EIFs referenced unique?

Are the data elements unique?

Is the processing logic is unique?

Is atleast one ILF maintained (except for control information)?

Is the data coming from outside the application?

Yes

Yes

Yes

Yes. Screen security

Yes

Example 2 – EQ Report security changes

� Counted as an EQ

Does it alter the systems behavior?

Does it maintain an ILF?

Does it create derived data?

Is the data retrieved from ILF/EIF?

Is the ILFs/EIFs referenced unique?

Are the data set elements unique?

Is the processing logic is unique?

Is the data going out from inside the application?

No

No

No

Yes

Yes

Yes

Yes

Yes

Example 2 – EI Add Employee security

� Counted as an EI

Are the ILFs/EIFs referenced unique?

Are the data elements unique?

Is the processing logic is unique?

Is atleast one ILF maintained (except for control information)?

Is the data coming from outside the application?

Yes

Yes

Yes

Employee security

Yes

Example 2 – EI Change Employee security

� Counted as an EI

Are the ILFs/EIFs referenced unique?

Are the data elements unique?

Is the processing logic is unique?

Is atleast one ILF maintained (except for control information)?

Is the data coming from outside the application?

Yes

Yes

Yes

Employee security

Yes

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.