|
Published Articles >> Table of Contents >> Abstract
April 1998 (Vol. 31, No. 4)
pp. 66-72
Using Process History to Predict Software Quality
Taghi M. Khoshgoftaar
Edward B. Allen
Robert Halstead
Gary P. Trio
Ronald M. Flass
Full Article Text:
   
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/2.666844
Send link to a friend
| Abstract |
|
Mission-critical systems must use reliable software. However, assuring software reliability often entails costly and time-consuming development processes. Software quality models can mitigate these costs by predicting module reliability early on, which lets developers focus improvement efforts on modules that require the most attention. Many software quality models use only product metrics such as lines of code or McCabe cyclomatic complexity. This product focus assumes that all modules have a similar process history. For systems that evolve, this assumption is not valid. Modules with similar product measurements may have different quality because of different development histories. For example, a reused module with many changes is likely to have more faults than a similar module with few changes. The authors have developed a quality model based solely on process-history variables. Their study posits that a module’s history prior to integration can help predict the likelihood of fault discovery during integration and test. Such module reliability predictions can be used to focus review, integration, and testing resources on high-risk areas of a system. They report their findings in a case study involving the Joint Surveillance Target Attack Radar System, an embedded, real-time military system developed by Northrop Grumman for the US Air Force in support of the US Army.
|
 References
|
[1] T.M. Khoshgoftaar, R.M. Szabo, and T.G. Woodcock, "An Empirical Study of Program Quality During Testing and Maintenance," Software Quality J., Sept. 1994, pp. 137-151.
[2] W.W. Agresti and W.M. Evanco, "Projecting Software Defects from Analyzing Ada Designs," IEEE Trans. Software Eng., Nov. 1992, pp. 988-997.
[3] R.W. Selby, "Empirically Based Analysis of Failures in Software Systems," IEEE Trans. Reliability, Oct. 1990, pp. 444-454.
[4] T.M. Khoshgoftaar et al., "Early Quality Prediction: A Case Study in Telecommunications," IEEE Software, Jan. 1996, pp. 65-71.
[5] T.M. Khoshgoftaar et al., "Detection of Fault-Prone Software Modules During a Spiral Life Cycle," Proc. Int'l Conf. Software Maintenance, IEEE CS Press, Los Alamitos, Calif., 1996, pp. 69-76.
[6] V.R. Basili, L.C. Briand, and W. Melo, "A Validation of Object-Oriented Design Metrics as Quality Indicators," IEEE Trans. Software Eng., Oct. 1996, pp. 751-761.
[7] D.W. Hosmer Jr. and S. Lemeshow, Applied Logistic Regression, John Wiley&Sons, New York, 1989.
[8] T.M. Khoshgoftaar and E.B. Allen, "The Impact of Costs of Misclassification on Software Quality Modeling," Proc. Fourth Int'l Software Metrics Symp., IEEE CS Press, Los Alamitos, Calif., 1997, pp. 54-62.
[9] B. Boehm, "A Spiral Model of Software Development and Enhancement," Computer, May 1988, pp. 61-72.
[10] D.L. Lanning and T.M. Khoshgoftaar, "The Impact of Software Enhancement on Software Reliability," IEEE Trans. Reliability, Dec. 1995, pp. 677-682.
|
 Additional Information
|
Citation:
Taghi M. Khoshgoftaar, Edward B. Allen, Robert Halstead, Gary P. Trio, Ronald M. Flass,
"Using Process History to Predict Software Quality,"
Computer,
vol. 31,
no. 4,
pp. 66-72,
Apr.,
1998
|
|
RSS Feed