Software complexity measurement

ABSTRACT

Inappropriate use of software complexity measures can have large, damaging effects by rewarding poor programming practices and demoralizing good programmers. Software complexity measures must be critically evaluated to determine the ways in which they can best be used.

REFERENCES

• 1: Baker, A.L. The use of software science in evaluating modularity concepts. IEEE Trans. Sojfw. Eng. SE-S, 2 (Mar. 1979), 110-120.
• 2: Baker, A.L., and Zweben, S.H. A comparison of measures of control flow complexity. IEEE Trans. Softw. Eng. SE-6,6 (Nov. 1980). 506-512.
• 3: Basili, V.R. Qualitative software complexity models: A summary. In Tutorial on Models and Methods for Software Management and Engineering. IEEE Computer Society Press, Los Alamitos, Calif., 1980.
• 4: Basili, V.R., and Hutchens, D.H. An empirical study of a syntactic complexity family. IEEE Trans. Softw. Eng. SE-g, 6 (Nov. 1963), 664-672.
• 5: Basili, V.R., Selby, R.W., Jr., and Phillips, T. Metric analysis and data validation across Fortran projects. IEEE Trans. Softm. Eng. SE-g. 6 {Nov. 1983), 652-663.
• 6: Bill Curtis , Sylvia B. Sheppard , Phil Milliman, Third time charm: Stronger prediction of programmer performance by software complexity metrics, Proceedings of the 4th international conference on Software engineering, p.356-360, September 17-19, 1979, Munich, Germany
• 7: Curtis, B., Sheppard, S.B., Milliman, P.. Borst, M.A.. and Love, T. Measuring the psychological complexity of software maintenance tasks with the Halstead and McCabe metrics. IEEE Trans. Softw. Eng. SE-5, I (Jan. 1979), 45-50.
• 8: Dunsmore, H.E., and Gannon, J.D. Analysis of the effects of programming factors on programming effort. I. Syst. Softw. I, 2 (Feb. 1980), 141-153.
• 9: W M. Evangelist, Software complexity metric sensitivity to program structuring rules, Journal of Systems and Software, v.3 n.3, p.231-243, September 1983 [doi>10.1016/0164-1212(83)90037-7]
• 10: Gordon, R.D. Measuring improvements in program clarity. IEEE Trans. Softm. Eng. SE-5, 2 (Mar. 1979), 79-90.
• 11: Maurice H. Halstead, Elements of Software Science (Operating and programming systems series), Elsevier Science Inc., New York, NY, 1977
• 12: Sallie Henry , Dennis Kafura , Kathy Harris, On the relationships among three software metrics, Proceedings of the 1981 ACM workshop/symposium on Measurement and evaluation of software quality, p.81-88, January 1981
• 13: Henry, S., and Kafura, D. The evaluation of software systems' structure using quantitative software metrics. Sofk Pmt. Exper. 14, 6 Uune 1984). 561-573.
• 14: McCabe, T.H. A complexity measure. ZEEE Trans. Soffw. Eng. SE-Z, 6 (Dec.1976). 308-320.
• 15: B. A. Sheil, The Psychological Study of Programming, ACM Computing Surveys (CSUR), v.13 n.1, p.101-120, March 1981 [doi>10.1145/356835.356840]
• 16: Sheppard, S.B., Milliman, P., and Curtis. B. Experimental evaluatjon of on-line program construction. GE Tech. Rep. TR-79-388100-6, General Electric, Dec. 1979.
• 17: Soloway, E., and Ehrlich, K. Empirical studies of programming knowledge. IEEE Trans. Sojfw. Eng. SE-IO, 5 (Sept. 1984). 595408.

INDEX TERMS

Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.8 Metrics
          Subjects: Complexity measures
  D.m MISCELLANEOUS
      Subjects: Software psychology**

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS

General Terms:
Design, Experimentation, Human Factors, Management, Measurement