Quantitative Analysis of Development Defects to Guide Testing: A Case Study

Software Quality Journal

Volumn 9, Issue 3, 2001, Pages 195-214

  Andrews, Anneliese ^a,b,c,d,e,f   Stringfellow, Catherine ^a,b,f,g,h,i  

^a Department of Computer Science   (United States)

^b Veterinary Dentistry and Oral Surgery   (United States)

^c Colorado Advanced Software Institute ^*  (United States)

^d DUKE UNIVERSITY   (United States)

^e UNIVERSITY OF KARLSRUHE   (Germany)

^f IEEE   (United States)

^g CAMERON UNIVERSITY   (United States)

^h OHIO STATE UNIVERSITY   (United States)

ⁱ NEW MEXICO HIGHLANDS UNIVERSITY   (United States)

Author keywords

Defect analysis; Fault proneness; Software test effectiveness

Indexed keywords

DEFECTS;

DEFECT ANALYSIS; DEVELOPMENT DEFECTS; FAULT-PRONENESS; MEDICAL RECORD SYSTEMS; QUALITY IMPROVEMENT; SOFTWARE COMPONENT; SOFTWARE PRODUCTS; TEST EFFECTIVENESS;

SOFTWARE TESTING;

EID: 1542783523     PISSN: 09639314     EISSN: 15731367     Source Type: Journal    
DOI: 10.1023/A:1013353520454     Document Type: Article

References (17)

1. Ash, D., Alderete, J., Oman, P.W., and Lowther, B. 1994. "Using software models to track code health," Proc. Int. Conf. Software Maintenance, Victoria, BC, Canada, September, pp. 154-160.
2. Biyani, S. and Santhanam, P. 1998. "Exploring defect data from development and customer usage on software modules over multiple releases," Proc. Ninth Int. Symp. Software Reliability Engineering, Paderborn, Germany, November, pp. 316-320.
3. Eick, S., Loader, C., Long, M., Votta, L., and Vander Wiel, S. 1992. "Estimating software fault content before coding," Proc. 14th Int. Conf. Software Engineering, Melbourne, Australia, pp. 59-65.
4. Fenton, N. and Ohlsson, N. 2000. "Quantitative analysis of faults and failures in a complex software system," IEEE Transactions on Software Engineering 26(8): 797-814.
5. Frankl, P., Hamlet, R., Littlewood, B., and Strigini, L. 1998. "Evaluating testing methods by delivered reliability," IEEE Transactions on Software Engineering 24(8): 586-601.
6. Khoshgoftaar, T.M. and Szabo, R.M. 1994. "Improving code churn predictions during the system test and maintenance phases," Proc. Int. Conf. Software Maintenance, Victoria, BC, Canada, September, pp. 58-66.
7. Khoshgoftaar, T.M. and Allen, E.B. 1998. "Predicting the order of fault-prone modules in legacy software," Proc. Ninth Int. Symp. Software Reliability Engineering, Paderborn, Germany, November, pp. 344-353.
8. Musa, J., Iannino, A., and Okumoto, K. 1987. Software Reliability: Measurement, Prediction, Application, New York, NY: McGraw-Hill.
9. Musa, J. 1998. "Applying failure data to guide decisions," Software Reliability Engineering, New York, NY: McGraw-Hill.
10. Ohlsson, N., Helander, M., and Wohlin, C. 1996. "Quality improvement by identification of fault-prone modules using software design metrics," Proc. Int. Conf. Software Quality, Ottowa, Canada, pp. 1-13.
11. Ohlsson, M. and Wohlin, C. 1996. "Identification of green, yellow and red legacy components," Proc. Int. Conf. Software Maintenance, Bethesda, Washington, DC, pp. 6-15.
12. Ohlsson, M., von Mayrhauser, A., McGuire, B., and Wohlin, C. 1999. "Code decay analysis of legacy software through successive releases," Proc. IEEE Aerospace Conf., Section 7.401.
13. Sahinoglu, M. and Alkhalidi, A.K. 1997. "A compound poisson LSD stopping rule for software reliability," Proc. 5th World Meeting of ISBA, Satellite Meeting to ISI-97, Istanbul.
14. Schneidewind, N.F. 1997. "Software metrics model for quality control," Proc. Int. Symp. Software Metrics, Albuquerque, New Mexico, pp. 127-136.
15. von Mayrhauser, A., Wang, J., Ohlsson, M., and Wohlin, C. 1999. "Deriving a fault architecture from defect history," Proc. Int. Symp. Software Reliability Engineering, Boca Raton, FL, pp. 129-146.
16. Wohlin, C. and Runeson, P. 1998. "Defect content estimations from review data," Proc. Int. Conf. Software Engineering, Kyoto, Japan, pp. 400-409.
17. Wohlin, C. and Runeson, P. 1995. "An experimental evaluation of capture-recapture in software inspections," Journal of Software Testing, Verification and Reliability 5(4): 213-232.