Software Measurement: A Necessary Scientific Basis

IEEE Transactions on Software Engineering

Volumn 20, Issue 3, 1994, Pages 199-206

  Fenton, Norman ^a  

^a Centre for Software Reliability   (United Kingdom)

Author keywords

complexity; empirical studies; measurement theory; metrics; Software measurement; validation

Indexed keywords

MEASUREMENT THEORY; SOFTWARE ENGINEERING;

EMPIRICAL STUDIES; METRICS; SOFTWARE MEASUREMENT;

COMPUTER SOFTWARE;

EID: 0028393055     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/32.268921     Document Type: Article

References (47)

1. E. Adams, “Optimizing preventive service of software products.” IBM Res. J.,vol.28, no. 1, pp. 2-14 1984.
2. A. J. Albrecht, “Measuring application development productivity,” in IBM Applic. Dev. Joint SHARE/GUIDE Symp., Monterey, CA, 1979, pp. 83–92.
3. J. Aczel, F. S. Roberts, and Z. Rosenbaum, “On scientific laws without dimensional constants,” J. Math. Anal. Applicat., vol. 119, no. 389–416, 1986.
4. A. Baker, J. Bieman, N. E. Fenton, D. Gustafson, A. Melton, and R. W. Whitty, “A philosophy for software measurement,” J. Syst. Software, vol. 12, pp. 277–281, July 1990.
5. S. Brocklehurst, P. Y. Chan, B. Littlewood, and J. Snell, “Recalibrating software reliability models,” IEEE Trans. Software Eng., vol. 16, no. 4, pp. 458–470, Apr. 1990.
6. B. Boehm, Software Engineering Economics. Englewood Cliffs, NJ: Prentice Hall, 1981.
7. V. Basili and D. Rombach, “The tame project: Towards improvement-orientated software environments,” IEEE Trans. Software Eng., vol. 14, no. 6, pp. 758–773, June 1988.
8. R. E. Courtney and D. A. Gustafson, “Shotgun correlations in software measures.” IEE Software Eng. J., vol. 8, no. 1, pp. 5–13, 1993.
9. J. C. Chemiavsky and C. H. Smith, “On weyuker's axioms for software complexity measures,” IEEE Trans. Software Eng., vol. 17, no. 6, pp. 636-638, June 1991.
10. R.A. DeMillo and R. J. Lipton. “Software project forecasting,” in Software Metrics, A. J. Perlis, F. G. Sayward, and M. Shaw, Eds. Cambridge, MA: MIT Press, 1981, pp. 77–89.
11. N. E. Fenton, Software Metrics: A Rigorous Approach. London: Chapman & Hall, 1991.
12. N. E. Fenton, “When a software measure is not a measure,” IEE Software Eng. t., vol. 7, no. 5, pp. 357–362, May 1992.
13. L. Finkelstein, “A-review of the fundamental concepts of measurement,” Measurement, vol. 2, no. 1, pp. 25–34, 1984.
14. N. E. Fenton and B. A. Kitchenham, “Validating software measures,” J. Software Testing, Verification & Reliability, vol. 1, no. 2, pp. 27–42, 1991.
15. N. E. Fenton and A. Melton, “Deriving structurally based software measures,” J. Syst., Software vol. 12, pp. 177–187, July 1990.
16. J.-C. Falmagne and L. Narens, “Scales and meaningfulness of quantita-tive laws.” Synthese, vol. 55, pp. 287–325, 1983.
17. P.J. Fleming and J.J. Wallace, “How not to lie with statistics,” Commun. ACM, vol. 29, pp. 218–221, 1986.
18. M. H. Halstead, Elements of Software Science. Amsterdam: Elsevier North Holland, 1975.
19. J. Inglis, “Standard software quality metrics,” AT&T Tech. J., vol. 65, no. 2, pp. 113–118, Feb. 1985.
20. D. R. Jeffery, G. C. Low, and M. Barnes, “A comparison of function point counting techniques,” IEEE Trans. Software Eng., vol. 19, no. 5, pp. 529–532, Mar. 1993.
21. Z. Jelinski and P. B. Moranda, “Software reliability research,” in Statistical Computer Performance Evaluation, W. Freiberger, Ed. New York: Academic Press, 1972, pp. 465–484.
22. B. A. Kitchenham and B. de Neumann, “Cost modelling and estimation,” in Software Reliability Handbook, P. Rook, Ed. New York: Elsevier Applied Science, 1990, pp. 333–376.
23. D. Kafura and S. Henry, “Software quality metrics based on intercon-nectivity,” J. Syst. & Software, vol. 2, pp. 121–131, 1981.
24. B. A. Kitchenham and K. Kansala,”correlations among function points,” in IEEE Software Metrics Symp., Baltimore, MD, 1993, pp. 11–15.
25. D. H. Krantz, R. D. Luce, P. Suppes, and A. Tversky, Foundations of Measurement, vol. 1. New York: Academic Press, 1971.
26. B. A. Kitchenham and N. R. Taylor, “Software project development cost estimation,” J. Syst. Software, vol. 5, pp. 67–278, 1985.
27. H. E. Kyburg, Theory and Measurement. Cambridge: Cambridge Univ. Press, 1984.
28. H. F. Li and W. K. Cheung, “An empirical study of software metrics,” IEEE Trans. Software Eng., vol. 13, no. 6, June 1987.
29. B. Littlewood, “Forecasting software reliability,” in Software Reliability, Modelling and Identification, S. Bittanti, Ed. (Lecture Notes in Computer Science, vol. 341). New York: Springer-Verlag, 1988, pp. 141–209.
30. T. J. McCabe, “A complexity measure.” IEEE Trans. Software Eng., vol. SE-2, no. 4, pp. 308–320, Apr. 1976.
31. A. C. Melton, D. A. Gustafson, J. M. Bieman, and A. A. Baker, “Mathe-matical perspective of software measures research,” IEE Software Eng. J.,vol. 5, no. 5, pp. 246–254, 1990.
32. J. C. Munson and Khoshgoftaar, “The detection of fault prone modules,” IEEE Trans. Software Eng., vol. 18, no. 5, pp, 423-433, May 1992.
33. M. Neil, “Multivariate assessment of software products,” J. Software Testing Verification and Reliability, to appear 1992.
34. R. E. Prather and S. G. Giulieri, “Decomposition of flowchart schemata.” Comput. J. vol. 24, no. 3, pp. 258–262, 1981.
35. R. S. Pressman, Software Engineering: A Practitioner's Approach., 2nd ed. New York: McGraw-Hill Int., 1987.
36. F. S. Roberts, Measurement Theory with Applications to Decision Making, Utility, and the Social Sciences. Reading, MA: Addison Wesley, l979.
37. F. S. Roberts, “Applications of the theory of meaningfulness to psychology,” J. Math. Psychol., vol. 29, pp. 311–332, 1985.
38. N. F. Schneidewind, “Methodology for validating software metrics,” IEEE Trans. Software Eng., vol. 18, no. 5, pp. 410–422, May 1992.
39. J. E. Smith, “Characterizing computer performance with a single num-ber,” Commun. ACM, vol. 31, pp. 1202–1206, 1988.
40. P. H. Sydenham, Ed., Handbook of Measurement Science, vol. 1. New York: J. Wiley, 1982
41. P. H. Sydenham, Ed., Handbook of Measurement Science, vol. 1. New York: J. Wiley, 1982. [41] C. R. Symons, “Function point analysis: Difficulties and improvements,” IEEE Trans. Software Eng., vol. 14, no. 1, pp. 2–11, Jan. 1988.
42. D. A. Troy and S. H. Zweben, “Measuring the quality of structured design,” J. Syst. Software, vol. 2, pp. 113–120, 1981.
43. J. Tian and M. V. Zelkowitz, “A formal program complexity model and its applications,” J. Syst. Software. vol. 17, pp. 253–266, 1992.
44. S. N. Woodfield, H. E. Dunsmore, and V. Y. Shen, “The effects of modularisation and comments on program comprehension,” in Proc. 5th Int. Conf. Software Eng., 1979, pp. 213–223.
45. E. J. Weyuker, “Evaluating software complexity measures,” IEEE Trans. Software Eng., vol. 14, no. 9, pp. 1357–1365, Sept. 1988.
46. H. Zuse, Software Complexity: Measures and Methods. Amsterdam: De Gruyter, 1990.
47. H. Zuse, “Support of experimentation by measurement theory,” in Experimental Software Engineering Issues (Lecture Notes in Computer Science, vol. 706), H. D. Rombach, V. R. Basili, and R. W. Selby, Eds. New York: Springer-Verlag, 1993, pp. 137–140.