Function Point Languages Table

Version 3.0 April 2005

© Copyright 2005 by Quantitative Software Management, Inc. All Rights Reserved.

The table below contains Function Point Language Gearing Factors from 2597 completed function point projects in the QSM database.  The projects span 289 languages from a total of 645 languages represented in the database.  Because mixed-language projects are not a reliable source of gearing factors, this table is based upon single-language projects only. Version 3.0 features the languages where we have the most recent, high-quality data.

The table will be updated and expanded as additional project data becomes available. As an additional resource, the David Consulting Group has graciously allowed QSM to include their data in this table.

Environmental factors can result in significant variation in the number of source statements per function point.  For this reason, QSM recommends that organizations collect both code counts and final function point counts for completed software projects and use this data for estimates.  Where there is no completed project data available for estimation, we provide the following gearing factor information (where sufficient project data exists):

• the average
• the median
• the range (low - high)

We hope this information will allow estimators to assess the amount of variation, the central tendency, and any skew to the distribution of gearing factors for each language.

Click Here for additional information on gearing factors and recommendations on using this table.

Click to Request gearing factors for languages not found in the table.

** Indicates languages which were present before but have been adjusted due to new information

More Information on Using Gearing Factors

What is a gearing factor? The gearing factor is simply the average number of Source Lines of Code (SLOC) per function point in the completed project.  It is calculated by dividing the final code count for a completed project by the final function point count. SLOC counts are logical, not physical line counts.

What if the language I am using is not in the table?  If you do not see the language you need in the table, you may substitute a gearing factor from a comparable language.  The uncertainty range for the estimated gearing factor may be increased to allow for any additional risk introduced by using a substitute.  You may also contact QSM to see if revised information is available.

Should I use the average or the median?  In a perfectly symmetrical distribution of gearing factors, the average and the median will be identical or very close.  The average is obtained by summing the gearing factors and then dividing by the number of gearing factors included in that sum. Although its purpose is to measure "central tendency", the average can be pulled up or down by extreme data values (or outliers).  The median, on the other hand, is simply the data point that lies in the center of an ordered list of gearing factors.  One half of the data points will lie above (and one half below) the median.  When the data set is skewed (biased either toward the high or low end by extreme data values), the median may be a more accurate indicator of the central tendency.

How should I use the range?  The range simply shows lowest and highest gearing factors for each language.  The range can be used, with the average and median, to choose a "most likely" gearing factor for estimation.  The range can be useful as a starting point for choosing an uncertainty range around your "most likely" estimate of the gearing factor.