teSting eStimation 149
Function Point Analysis was developed first by Allan J. Albrecht in the
mid-1970s. It was an attempt to overcome difficulties associated with lines of
code as a measure of software size, and to assist in developing a mechanism to
predict efforts associated with software development. The method was first
published in 1979, then later in 1983. In 1984 Albrecht refined the method
and since 1986, when the International Function Point User Group (IFPUG)
was set up, several versions of the Function Point Counting Practices Manual
have come out.
Note: The best way to understand any complicated system is to break the system
down into smaller subsystems and try to understand those smaller sub-systems
first. In a function point you break complicated systems into smaller systems
and estimate those smaller pieces, then total up all the subsystem estimates to
come up with a final estimate.
Basics of Function Points
The Following are some terms used in FPA: [Function Point analysis].
(B) can you explain an application Boundary?
Application Boundary
The first step in FPA is to define the boundary. There are two types of major
boundaries:
Internal Application Boundary
External Application Boundary
We will give the features of external application boundaries and the
internal application boundaries will be obvious.
The external application boundary can be identified using the following
litmus test:
Does it have or will it have any other interface to maintain
its data, which was not developed by you?. Example: Your
n
n
n
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.