Академический Документы
Профессиональный Документы
Культура Документы
aspx
SAM|NET
»»» technology + aesthetics «««
<< An nescis, mi fili, quantilla prudentia mundus regatur ? | Home | Microsoft Innovation Days >>
The ability to accurately estimate the time/cost taken for a project to come to its successful conclusion has been a
serious problem for software engineers. The use of repeatable, clearly defined and well understood software
development process has in recent years shown itself to be the most effective method of gaining useful historical
data that can be used for statistical estimation. In particular, the act of sampling more frequently, coupled with the
loosening of constraints between parts of a project, has allowed more accurate estimation and more rapid
development times.
Parametric Estimating
Wideband Delphi
Cocomo
SLIM
SEER-SEM Parametric Estimation of Effort, Schedule, Cost, Risk (based on Brooks Law)
Function Point Analysis
Proxy Based Estimation (PROBE) (from the Personal Software Process)
The Planning Game (from Extreme Programming)
Program Evaluation and Review Technique (PERT)
Analysis Effort method
News NOTE: Brooks' law was stated by Fred Brooks in his 1975 book The Mythical Man-Month as "Adding
manpower to a late software project makes it later." Likewise, Brooks memorably stated "The bearing of a child
takes nine months, no matter how many women are assigned."
My Compa ny
The value to be gained from utilizing a functional sizing technique, such as Function Points, is primarily in the
capability to accurately estimate a project early in the development process.
In words of Wikipedia
Function Point Analysis (FPA) is an ISO recognized method to measure the functional size of an information
system. The functional size reflects the amount of functionality that is relevant to and recognized by the user in
the business. It is independent of the technology used to implement the system.
The unit of measurement is "function points". So, FPA expresses the functional size of an information system in a
number of function points (for example: the size of a system is 314 fp's).
1 of 6 15/04/2011 14:03
Estimation Techniques : Function Point Analysis (FPA) http://geekswithblogs.net/Prabhats/archive/2007/03/01/107632.aspx
Productivity:
The definition of productivity is the output-input ratio within a time period with due consideration for quality.
The formula indicates that productivity can be improved by (1) by increasing outputs with the same inputs, (2) by
decreasing inputs but maintaining the same outputs, or (3) by increasing outputs and decreasing inputs change the
ratio favorably.
Productivity implies effectiveness and efficiency in individual and organizational performance. Effectiveness is
the achievement of objectives. Efficiency is the achievement of the ends with least amount of resources.
Software productivity is defined as hours/function points or function points/hours. This is the average cost to
develop software or the unit cost of software. One thing to keep in mind is the unit cost of software is not fixed
with size. What industry data shows is the unit cost of software goes up with size.
Average cost is the total cost of producing a particular quantity of output divided by that quantity. In this case to
Total Cost/Function Points. Marginal cost is the change in total cost attributable to a one-unit change in output.
There are a variety of reasons why marginal costs for software increase as size increases. The following is a list of
some of the reasons
Function Points are the output of the software development process. Function points are the unit of software. It is
very important to understand that Function Points remain constant regardless who develops the software or what
language the software is developed in. Unit costs need to be examined very closely. To calculate average unit cost
all items (units) are combined and divided by the total cost. On the other hand, to accurately estimate the cost of
an application each component cost needs to be estimated.
To complete a function point count knowledge of function point rules and application documentation is needed.
2 of 6 15/04/2011 14:03
Estimation Techniques : Function Point Analysis (FPA) http://geekswithblogs.net/Prabhats/archive/2007/03/01/107632.aspx
Access to an application expert can improve the quality of the count. Once the application boundary has been
established, FPA can be broken into three major parts
Rating of transactions is dependent on both information contained in the transactions and the number of files
referenced, it is recommended that transactions are counted first. At the same time a tally should be kept of all
FTR’s (file types referenced) that the transactions reference. Every FTR must have at least one or more
transactions. Each transaction must be an elementary process. An elementary process is the smallest unit of
activity that is meaningful to the end user in the business. It must be self-contained and leave the business in
consistent state
The function point method was originaly developed by Bij Albrecht. A function point is a rough estimate of a unit
of delivered functionality of a software project. Function points (FP) measure size in terms of the amount of
functionality in a system. Function points are computed by first calculating an unadjusted function point count
(UFC). Counts are made for the following categories
Once this data has been collected, a complexity rating is associated with each count according to Table
Each count is multiplied by its corresponding complexity weight and the results are summed to provide the
UFC. The adjusted function point count (FP) is calculated by multiplying the UFC by a technical
complexity factor (TCF) also referred to as Value Adjustment Factor (VAF). Components of the TCF are
listed in Table 2
3 of 6 15/04/2011 14:03
Estimation Techniques : Function Point Analysis (FPA) http://geekswithblogs.net/Prabhats/archive/2007/03/01/107632.aspx
Each component is rated from 0 to 5, where 0 means the component has no influence on the system and 5
means the component is essential (Pressman, 1997). The VAF can then be calculated as:
The factor varies from 0.65 (if each Fi is set to 0) to 1.35 (if each Fi is set to 5) (Fenton, 1997). The final
function point calculation is:
4 of 6 15/04/2011 14:03
Estimation Techniques : Function Point Analysis (FPA) http://geekswithblogs.net/Prabhats/archive/2007/03/01/107632.aspx
REFERENCES:
http://www.fprecorder.com/
http://www.codeproject.com/gen/design/Softwarecosting.asp
http://www.softdevtools.com/modules/weblinks/viewcat.php?cid=39
http://www.softwaremetrics.com/Function%20Point%20Training%20Booklet%20New.pdf
http://sern.ucalgary.ca/courses/seng/621/W98/johnsonk/cost.htm#Function%20Points
http://msdn2.microsoft.com/en-us/library/bb245774.aspx
http://www.methodsandtools.com/mt/download.php
http://www.softwaremetrics.com/freemanual.htm
http://www.ijcim.th.org/past_editions/v13n1/IJCIM-V131-pp3.pdf
http://www.codeproject.com/gen/design/usecasep.asp
http://www.codeproject.com/gen/design/cocomo2.asp
http://www.codeproject.com/gen/design/estimate-manhour-software.asp
http://www.codeproject.com/gen/design/Estimation.asp
Feedback
No comments posted yet.
Title:
re: Estimation Techniques : Function Point Analysis (FPA)
Name:
Website:
Comment:
5 of 6 15/04/2011 14:03
Estimation Techniques : Function Point Analysis (FPA) http://geekswithblogs.net/Prabhats/archive/2007/03/01/107632.aspx
Post
6 of 6 15/04/2011 14:03