Design complexity measurement and testing

ABSTRACT

System designers can quantify the complexity of a software design by using a trio of finely tuned design metrics.

REFERENCES

• 1: W. Richards Adrion , Martha A. Branstad , John C. Cherniavsky, Validation, Verification, and Testing of Computer Software, ACM Computing Surveys (CSUR), v.14 n.2, p.159-192, June 1982 [doi>10.1145/356876.356879]
• 2: Albrecht. A.J. Function points help managers assess applications. Computerworld (Aug. 26, 1985), SR20-SR21.
• 3: Butler, C.W., Hodil, E.D., and Richardson, G.L. Knowledge-based systems in the commercial environment. IBM Syst. J. 25, 2 {1986), 47.
• 4: Butler, C.W., Hodil, E.D., and Richardson, G.L. Applying expert systems technology to software maintenance. In Proceedings of the 1987 Conference on Software Maintenance (May 1987).
• 5: D L Carver, Criteria for estimating module complexity, Journal of Systems Management, v.37 n.8, p.18-23, Aug. 1986
• 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. Predicting performance on software maintenance tasks with the Halstead and McCabe metrics. IEEE Trans. Soflw. Eng., 5 (1979}, 95-104.
• 8: T. DeMarco, Controlling Software Projects: Management, Measurement, and Estimates, Prentice Hall PTR, Upper Saddle River, NJ, 1986
• 9: Steve Drummond, Measuring applications development performance, Datamation, v.31 n.4, p.102-108, Feb. 15, 1985
• 10: Elshoff, }.L. The PEEK Measurement Program. Res. Pub. GMR-4208, General Motors Research Labs, Warren, Mich. (Nov. 15, 1982}, 18.
• 11: Elshoff, }.L. Characteristic program complexity measures. Res. Pub. GMR-4446. General Motors Research Labs, Warren, Mich. (Dec. 5, 1983), 2.
• 12: Ann Fitzsimmons , Tom Love, A Review and Evaluation of Software Science, ACM Computing Surveys (CSUR), v.10 n.1, p.3-18, March 1978 [doi>10.1145/356715.356717]
• 13: Maurice H. Halstead, Elements of Software Science (Operating and programming systems series), Elsevier Science Inc., New York, NY, 1977
• 14: 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
• 15: Brian W. Kernighan , P. J. Plauger, The Elements of Programming Style, McGraw-Hill, Inc., New York, NY, 1982
• 16: McCabe, T.J. A complexity measure. IEEE Trans. Soflw. Eng. SE-2, 4 (Dec. 1976), 308.
• 17: Glenford J. Myers, An extension to the cyclomatic measure of program complexity, ACM SIGPLAN Notices, v.12 n.10, p.61-64, October 1977 [doi>10.1145/954627.954633]
• 18: Petschenik, N.H. Practical priorities in system testing. IEEE Trans. Soflw. Eng. (Sept. 1985), 18-23.
• 19: Sheppard, S.B., and Kruesi, E. The effects of the symbology and spatial arrangement of software specifications in a coding task. Tech. Rep. TR-81-388200-3. General Electric Company, Arlington, VA, 1981.
• 20: "Structured Testing: A Software Testing Methodology Using the Cycjomatic Complexity Metric," National Bureau of Standards Special Publication No. 500-99, December 1982.
• 21: Walsh. T.J. Software reliability study using a complexity measure. In Proceedings of the National Computer Conference. New York: AFIPS, 1979.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.8 Metrics
          Subjects: Complexity measures

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

General Terms:
Algorithms, Design, Measurement

Keywords:
Complexity classes, complexity measures, software development, software quality assurance, systems analysis and design, systems development, test generation, testing, trees