This Article 
 Bibliographic References 
 Add to: 
Function Points in the Estimation and Evaluation of the Software Process
January 1990 (vol. 16 no. 1)
pp. 64-71

The authors report the results of an empirical research project on the consistency and limitations of the number of function points as an a priori measure of system size rather than the traditional lines-of-code measure. They conclude that function points are a more consistent a priori measure of system size. The results also indicate that the function-point estimate of size is lower for analysts experienced both in software development and in function-point estimation.

[1] A. J. Albrecht, "Measuring application development productivity," inProc. Joint SHARE/GUIDE/IBM Application, Devlopment Symp., Oct. 1979, pp. 34-43.
[2] A. J. Albrecht and J. E. Gaffney, "Software function, source lines of code, and development effort prediction: A software science validation."IEEE Trans. Software Eng., vol. SE-9. pp. 639-648, Nov. 1983.
[3] B. W. Boehm,Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.
[4] R. G. Canning, "A programmer productivity controversy."EDP Analyser, vol. 24, no. 1, pp. 1-11, 1986.
[5] D. Case, "Productivity in the university--Scholarly work as information work."Proc. Ameri. Soc. Inform. Sci., vol. 20. pp. 2-3, 1983.
[6] S.D. Conte, H.E. Dunsmore, and V.Y. Shen,Software Engineering: Metrics and Models, Benjamin/Cummings, Menlo Park, Calif., 1986.
[7] IBM Corp.,Devlopment Center Productivity Measurement Guide," Middlesex, England 1984.
[8] D. R. Jeffery, "A software development productivity model for MIS environments,"J. Syst. Software, vol. 7, pp. 115-125, 1987.
[9] D. R. Jeffery, C. C. Loo, and G. C. Low, "The validity, reliability, and practically of function points as a measure of software size," Dep. Inform. Syst., Univ. New South Wales, Inform. Syst. Res. Rep. 33, 1988.
[10] T. C. Jones, "Measuring programming quality and productivity,"IBM Syst. J., vol. 17, no. 1, pp. 39-63, 1978.
[11] T. C. Jones,Programming Productivity. New York: McGraw-Hill, 1986.
[12] L. H. Putnam, "A general empirical solution to the macro software sizing and estimation problem."IEEE Trans. Software Eng., vol. SE-4. pp. 345-361, July 1978.
[13] R. E. Rice and J. Bair, "Conceptual role of new communication technology in organizational productivity,"Proc. Amer. Soc. Inform. Sci., vol. 20. pp. 4-8. 1983.
[14] E. E. Rudolph, "Productivity in computer application development." Dep. Management Studies, Univ. Auckland, Australia. 1983.
[15] "Quoting a software job--by simple arithmetic,"Computerworld, pp. 33-34, Aug. 1987.
[16] E. E. Rudolph and G. Simpson, "Evaluation of a fourth generation language," inProc. ACS&IFIP Joint Sym. Information Systems, Sydney. Australia, Apr. 1984, pp. 148-165.
[17] Software Productivity Research Inc.,SPQR/20 User's Guide, 1986.
[18] R. H. Thayer, A. B. Pyster, and R. C. Wood, "Major issues in software engineering project management."IEEE Trans. Software Eng., vol. SE-7, pp. 333-342, July 1981.
[19] C. E. Walston and C. P. Felix, A method of program measurement and estimation,"IBM Syst. J., vol. 16, no. 1. pp. 54-73, 1977.

Index Terms:
estimation; evaluation; consistency; limitations; function points; a priori measure; system size; software development; function-point estimation; software engineering.
G.C. Low, D.R. Jeffery, "Function Points in the Estimation and Evaluation of the Software Process," IEEE Transactions on Software Engineering, vol. 16, no. 1, pp. 64-71, Jan. 1990, doi:10.1109/32.44364
Usage of this product signifies your acceptance of the Terms of Use.