This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Debugging Effort Estimation Using Software Metricsv
February 1990 (vol. 16 no. 2)
pp. 223-231

Measurements of 23 style characteristics, and the program metrics LOC, V(g), VARS, and PARS were collected from student Cobol programs by a program analyzer. These measurements, together with debugging time (syntax and logic) data, were analyzed using several statistical procedures of SAS (statistical analysis system), including linear, quadratic, and multiple regressions. Some of the characteristics shown to correlate significantly with debug time are GOTO usage, structuring of the IF-ELSE construct, level 88 item usage, paragraph invocation pattern, and data name length. Among the observed characteristic measures which are associated with lowest debug times are: 17% blank lines in the data division, 12% blank lines in the procedure division, and 13-character-long data items. A debugging effort estimator, DEST, was developed to estimate debug times.

[1] M. M. Al-Jarrah and I. S. Torsun, "An empirical analysis of Cobol programs,"Software Practice and Experience, vol. 9, pp. 341-359, 1979.
[2] R. E. Berry and B. A. E. Meekings, "A style analysis of C programs,"Commun. ACM, vol. 28, no. 1, pp. 80-88, Jan. 1985.
[3] V. Côté, P. Bourque, S. Oligny, and N. Rivard, "Software metrics: An overview of recent results,"J. Syst. Software, vol. 8, no. 2, pp. 121-131, Mar. 1988.
[4] H. E. Dunsmore, "The effect of comments, mnemonic names, and modularity: Some university experiment results," inProc. Symp. Emp. Found. Inform. Software Sci., Atlanta, GA, Oct. 1984.
[5] E. W. Dijkstra, "Go to statements considered harmful,"Commun. ACM, vol. 11, no. 3, pp. 147-148, Mar. 1968.
[6] W. Harrison and C. Cook, "A note on the Berry-Meekings style metric,"Commun. ACM, vol. 29, no. 2, pp. 123-125, Feb. 1986.
[7] B. S. Kernighan and P. J. Plaugher, "Programming style: Examples and counterexamples,"ACM Comput. Surveys, vol. 6, no. 4, pp. 303-319, 1974.
[8] B. A. E. Meekings, "Style analysis of Pascal programs,"SIGPLAN Notices, vol. 18, no. 9, pp. 45-54, Sept. 1983.
[9] R.J. Miara et al., "Program Indentation and Comprehensibility,"Comm. ACM, Nov. 1983, pp. 861-867.
[10] G. J. Myers,Composite Structured Design. New York: Van Nostrand Reinhold, 1978.
[11] K.A. Redish and W.F. Smith, "Program Style Analysis: A Natural By-Product of Program Compilation,"Comm. ACM, Feb. 1986, pp. 126-133.
[12] M.J. Rees, "Automatic Assessment Aids for Pascal Programs,"ACM SIGPlan Notices, Oct. 1982, pp. 33-42.

Index Terms:
debugging effort estimation; quadratic regressions; linear regressions; software metrics; style characteristics; LOC; V(g); VARS; PARS; Cobol programs; program analyzer; statistical procedures; SAS; statistical analysis system; multiple regressions; GOTO usage; IF-ELSE construct; level 88 item usage; paragraph invocation pattern; data name length; debug times; DEST; program debugging; program testing; statistical analysis.
Citation:
N. Gorla, A.C. Benander, B.A. Benander, "Debugging Effort Estimation Using Software Metricsv," IEEE Transactions on Software Engineering, vol. 16, no. 2, pp. 223-231, Feb. 1990, doi:10.1109/32.44385
Usage of this product signifies your acceptance of the Terms of Use.