×

Horizontal dispersion of software functional size with IFPUG and COSMIC units. (English) Zbl 1187.68160

Summary: Software development companies today are widely using software functional size measurement (FSM) as the main variable to assess the effort and time needed to perform a new software project. In the recent years, this has led to a grown interest in improving the way the measures are taken.
In such sense, one of the main aspects that could have impact on measurements and that has not been enough studied is the error introduced by the measurer of the software application, through the subjectivity that can be introduced in the interpretation of the unit application rules. Such error could be evident in a measurement dispersion, defined in this paper in two possible ways: (a) Horizontal Dispersion, where the error could be introduced by the fact that two or more different people counted the same application at the same moment in the project development; and (b) Vertical Dispersion, where the error could be introduced by same measurer that count the same application at different times during the development.
Since its definition by Albrecht in 1979 and its subsequent change of name in 1986, IFPUG function points have been the functional software measurement unit mostly applied, despite the definition and standardization of other variants such as NESMA, Mk-II, or more recently FiSMA. However in recent years a new method has been introduced called COSMIC that has been defined as a 2nd-generation FSM method, attracting the interest of the international software measurement community.
The aim of this research is to draw some preliminary conclusions from statistical analysis of the software functional size data in which the horizontal dispersion degree could have been introduced in measurements taken into account IFPUG and COSMIC methods.

MSC:

68N99 Theory of software
Full Text: DOI

References:

[1] Albrecht AJ. Measuring application development productivity. In: Proceedings of joint SHARE, GUIDE, and IBM application development symposium; 1979. p. 83 – 92.
[2] Albrecht, A. J.; Gaffney, J. E.: Software function, source lines of code, and development effort prediction: a software science validation, IEEE trans soft eng 9, No. 6, 639-647 (1983)
[3] IFPUG. Function point counting practices manual, release 4.2.1. International Function Point User Group; 2004. ISBN: 0-963-1742-9-0.
[4] Gencel, C.; Demirors, O.: Functional size measurement revisited, ACM trans soft eng method (TOSEM) 17, No. 3 (2008)
[5] Abran, A.; Robillard, P.: Function points: a study of their measurement process and scale transformations, J syst soft 25, 171-184 (1994)
[6] ISO/IEC 20926:2003. Software engineering – IFPUG 4.1 unadjusted functional size measurement method. Counting practices manual. Genève: International Organization for Standardization; 2003.
[7] ISO/IEC 24750:2005. Software engineering – NESMA functional size measurement method, version 2.1. Definitions and counting guidelines for the application of function point analysis. Genève: International Organization for Standardization; 2005.
[8] ISO/IEC 20968:2002. Software engineering – Mk-II function point analysis. Counting practices manual. Genève: International Organization for Standardization, ISO; 2002.
[9] ISO/IEC 19761:2003. Software engineering – COSMIC-FFP. A functional size measurement method. Genève: International Organization for Standardization; 2003.
[10] ISO/IEC 29881:2008. Information technology – software and systems engineering – FISMA v1.1 functional size measurement method. Genève: International Organization for Standardization; 2008.
[11] NESMA. Function point analysis for software enhancement – version 1.0. Netherlands Software Metrics Association; 2001. <http://www.nesma.org>.
[12] Symons, C.: Function point analysis: difficulties and improvements, IEEE trans soft eng 14, No. 1, 2-11 (1988)
[13] COSMIC. COSMIC measurement manual 3.0.1. Common Software Measurement International Consortium; May 2009.
[14] ISBSG. Repository data – release 8. International Software Benchmarking Standards Group; 2005. <http://www.isbsg.org/>.
[15] ISBSG. Repository data – release 11. International Software Benchmarking Standards Group; 2009. <http://www.isbsg.org/>.
[16] IEEE Std 830-1998. In: IEEE recommended practice for software requirements specifications. Institute of Electrical and Electronics Engineers; 1998.
[17] Fetcke T. The warehouse software portfolio. A case study in functional size measurement. Technical report no. 1999 – 20, Département d’informatique, Université du Quebec à Montréal, Canada. <http://www.fetcke.de/papers/Fetcke1999b.pdf>.
[18] Ho VT, Abran A, Fetcke T. A comparative study case of COSMIC-FFP, full function point and IFPUG methods. Département d’informatique, Université du Québec à Montréal, Canada. <www.lrgl.uqam.ca/publications/pdf/599.pdf>.
[19] Desharnais JM, Abran A, Cuadrado-Gallego JJ. Convertibility of function points to COSMIC: identification and analysis of functional outliers. In: Proceedings of the 17th international workshop on software measurement, Shaker-Verlag, Palma de Mallorca, Illes Balears, España, November 5 – 8, 2007. p. 130 – 46. <http://www.gelog.etsmtl.ca/publications/pdf/1035.pdf>.
[20] Abran A, Desharnais J-M, Azziz F. Measurement convertibility: from function points to COSMIC-FFP. In: Proceedings of the 15th international workshop on software measurement, Shaker-Verlag, Montréal, Canada, September 12 – 14, 2005. p. 227 – 40. <http://www.gelog.etsmtl.ca/publications/pdf/906.pdf>.
[21] Vogelezang F, Lesterhuis A. Applicability of COSMIC full function points in an administrative environment: experiences of an early adopter. In: Proceedings of the 13th international workshop on software measurement, Shaker-Verlag, Montréal, Canada, September 22 – 25, 2003. p. 232 – 43.
This reference list is based on information provided by the publisher or from digital mathematics libraries. Its items are heuristically matched to zbMATH identifiers and may contain data conversion errors. In some cases that data have been complemented/enhanced by data from zbMATH Open. This attempts to reflect the references listed in the original paper as accurately as possible without claiming completeness or a perfect matching.