This Article 
 Bibliographic References 
 Add to: 
Software Productivity Measurement Using Multiple Size Measures
December 2004 (vol. 30 no. 12)
pp. 1023-1035
Emilia Mendes, IEEE Computer Society
Productivity measures based on a simple ratio of product size to project effort assume that size can be determined as a single measure. If there are many possible size measures in a data set and no obvious model for aggregating the measures into a single measure, we propose using the expression AdjustedSize/Effort to measure productivity. AdjustedSize is defined as the most appropriate regression-based effort estimation model, where all the size measures selected for inclusion in the estimation model have a regression parameter significantly different from zero (p < 0.05). This productivity measurement method ensures that each project has an expected productivity value of one. Values between zero and one indicate lower than expected productivity, values greater than one indicate higher than expected productivity. We discuss the assumptions underlying this productivity measurement method and present an example of its use for Web application projects. We also explain the relationship between effort prediction models and productivity models.

[1] A. Albrecht and J. Gaffney, “Software Function, Source Lines of Code and Development Effort Prediction: A Software Science Validation,” IEEE Trans. Software Eng., vol. 9, no. 6, 1983.
[2] M. Arnold and P. Pedross, “Software Size Measurement and Productivity Rating In a Large-Scale Software Development Department,” Proc. 20th Int'l Conf. Software Eng., pp. 490-493, Apr. 1998.
[3] B.W. Boehm, Software Engineering Economics. Prentice-Hall, 1981.
[4] S.R. Chidamber, D.P. Darcy, and C.F. Kemerer, “Managerial Use of Metrics for Object-Oriented Software: An Exploratory Analysis,” IEEE Trans. Software Eng., vol. 24, no. 8, pp. 629-639, Aug. 1998.
[5] S. Elbaum, D. Gable, and G. Rothermel, “Understanding and Measuring the Sources of Variation in the Prioritization of Regression Test Suites,” Proc. Seventh Int'l Software Metrics Symp., pp. 169-179, Apr. 2001.
[6] M.H. Halstead, Elements of Software Science. Elsevier, 1977.
[7] T.E. Hastings and A.S.M. Sajeev, “A Vector-Based Approach to Software Size Measurement and Effort Estimation,” IEEE Trans. Software Eng., vol. 27, no. 4, pp. 337-350, Apr. 2001.
[8] T.E. Hastings and A.S.M. Sajeev, “A Vector-Based Software Size Measurement,” Proc. Australian Software Eng. Conf. (ASWEC '97), pp. 7-15, 1997.
[9] B.A. Kitchenham, “Procedures for Performing Systematic Reviews,” Joint Technical Report Keele University TR/SE0104 and NICTA 0400011T.1, pp. 1-28, 2004.
[10] B.A. Kitchenham, “The Question of Scale Economies In Software— Why Cannot Researchers Agree?” Information and Software Technology, vol. 44, pp. 13-24, 2002.
[11] B.A. Kitchenham, “A Procedure for Analysing Unbalanced Datasets,” IEEE Trans. Software Eng., vol. 24, no. 4, pp. 278-301, Apr. 1998.
[12] B.A. Kitchenham, L.M. Pickard, S.G. Macdonell, and M.J. Shepperd, “What Accuracy Statistics Really Measure,” IEE Proc. -Software, vol. 148, no. 3, pp. 81-85, 2001.
[13] B.A. Kitchenham and E. Mendes, “A Comparison of Cross-Company and Within-Company Effort Estimation Models for Web Applications,” Proc. Empirical Assessment in Software Eng., pp. 47-56, May 2004.
[14] B.A. Kitchenham and E. Mendes, “Systematic Review of Software Productivity Measurement,” , 2004.
[15] B.A. Kitchenham, T. Dybå, and M. Jørgensen, “Evidence-Based Software Engineering,” Proc. Int'l Conf. Software Eng., pp. 273-281, May 2004.
[16] A. MacCormack, C. Kemerer, M. Cusumano, and B. Crandall, “Trade-Offs between Productivity and Quality in Selecting Software Development Practices,” IEEE Software, pp. 78-79, Sept./Oct. 2003.
[17] K.D. Maxwell, Applied Statistics for Software Managers. Software Quality Institute Series, Prentice-Hall, 2002.
[18] K.D. Maxwell and P. Forselius, “Benchmarking Software Development Productivity,” IEEE Software, vol. 17, no. 1, pp. 80-88, Jan./Feb. 2000.
[19] E. Mendes, N. Mosley, and S. Counsell, “Investigating Early Web Size Measures for Web Cost Estimation,” Proc. Int'l Conf. Empirical Assessment in Software Eng., pp. 1-22, 2003.
[20] S. Morasca and G. Russo, “An Empirical Study of Software Productivity,” Proc. 25th Ann. Int'l Computer Software and Applications Conf., pp. 317-322, Oct. 2001.
[21] S. Moser and O. Nierstrasz, “The Effect of Object-Oriented Frameworks on Developer Productivity,” Computer, vol. 29, no. 9, pp. 45-51, Sept. 1996.
[22] I. Myrtveit and E. Stensrud, “Benchmarking COTS Projects Using Data Envelopment Analysis,” Proc. Sixth Int'l Software Metrics Symp., pp. 269-278, Nov. 1999.
[23] D. Reifer, “Web-Development: Estimating Quick-Time-to-Market Software,” IEEE Software, vol. 17, no. 8, pp. 57-64, Nov./Dec. 2000.
[24] J. Rosenberg, “Some Misconceptions about Lines of Code,” Proc. Fourth Int'l Software Metrics Symp., pp. 137-142, Nov. 1997.
[25] W.R. Shadish, T.D. Cook, and D.T. Campbell, Experimental and Quasi-Experimental Designs for Generalized Causal Inference. Houghton Mifflin Company, 2002.
[26] E. Stensrud and I. Myrtveit, “Identifying High Performance ERP Projects,” IEEE Trans. Software Eng., vol. 29, no. 5, pp. 398-416, May 2003.
[27] S.C. Kumbhakar and C.A.K. Lovell, Stochastic Frontier Analysis. Cambridge Univ. Press, 2000.

Index Terms:
Software productivity measurement, software cost estimation.
Barbara Kitchenham, Emilia Mendes, "Software Productivity Measurement Using Multiple Size Measures," IEEE Transactions on Software Engineering, vol. 30, no. 12, pp. 1023-1035, Dec. 2004, doi:10.1109/TSE.2004.104
Usage of this product signifies your acceptance of the Terms of Use.