Elaine J. Weyuker
ABSTRACT
Although this is a talk about the design of predictive models to determine where faults are likely to be in the next release of a large software system, the primary focus of the talk is the process that was followed when doing this type of software engineering research. We follow the project from problem inception (cradle) to productization (grave), describing each of the intermediate stages to try to give a picture of why such research takes so long, and also why it is necessary to perform each of the steps.
- E.N. Adams. Optimizing Preventive Service of Software Products. IBM J. Res. Develop., Vol 28, No 1, Jan 1984, pp. 2--14.Google Scholar
Digital Library
- E. Arisholm and L.C. Briand. Predicting Fault-prone Components in a Java Legacy System. Proc. ACM/IEEE ISESE, Rio de Janeiro, 2006. Google ScholarDigital Library
- V.R. Basili and B.T. Perricone. Software Errors and Complexity: An Empirical Investigation. Communications of the ACM, Vol 27, No 1, Jan 1984, pp. 42--52. Google ScholarDigital Library
- R.M. Bell, T.J. Ostrand, and E.J. Weyuker. Looking for Bugs in All the Right Places. Proc. ACM/International Symposium on Software Testing and Analysis (ISSTA2006), Portland, Maine, July 2006, pp. 61--71. Google ScholarDigital Library
- S. R. Chidamber and C. F. Kemerer. A Metrics Suite for Object Oriented Design. IEEE Trans. on Software Engineering, vol 20 no 6, June 1994, pp.476--493. Google ScholarDigital Library
- G. Denaro and M. Pezze. An Empirical Evaluation of Fault-Proneness Models. Proc. International Conf on Software Engineering (ICSE2002), Miami, USA, May 2002. Google ScholarDigital Library
- S.G. Eick, T.L. Graves, A.F. Karr, J.S. Marron, A. Mockus. Does Code Decay? Assessing the Evidence from Change Management Data. IEEE Trans. on Software Engineering, Vol 27, No. 1, Jan 2001, pp. 1--12. Google ScholarDigital Library
- N.E. Fenton and N. Ohlsson. Quantitative Analysis of Faults and Failures in a Complex Software System. IEEE Trans. on Software Engineering, Vol 26, No 8, Aug 2000, pp. 797--814. Google ScholarDigital Library
- T.L. Graves, A.F. Karr, J.S. Marron, and H. Siy. Predicting Fault Incidence Using Software Change History. IEEE Trans. on Software Engineering, Vol 26, No. 7, July 2000, pp. 653--661. Google ScholarDigital Library
- L. Guo, Y. Ma, B. Cukic, H. Singh. Robust Prediction of Fault-Proneness by Random Forests. Proc. ISSRE 2004, Saint-Malo, France, Nov. 2004. Google ScholarDigital Library
- L. Hatton. Reexamining the Fault Density - Component Size Connection. IEEE Software, March/April 1997, pp. 89--97. Google ScholarDigital Library
- T.M. Khoshgoftaar, E.B. Allen, J. Deng. Using Regression Trees to Classify Fault-Prone Software Modules. IEEE Trans. on Reliability, Vol 51, No. 4, Dec 2002, pp. 455--462.Google ScholarCross Ref
- P. McCullagh and J.A. Nelder. Generalized Linear Models, Second Edition, Chapman and Hall, London, 1989.Google ScholarCross Ref
- K-H. Moller and D.J. Paulish. An Empirical Investigation of Software Fault Distribution. Proc. IEEE First International Software Metrics Symposium, Baltimore, Md., May 21-22, 1993, pp. 82--90.Google ScholarCross Ref
- J.C. Munson and T.M. Khoshgoftaar. The Detection of Fault-Prone Programs. IEEE Trans. on Software Engineering, Vol 18, No 5, May 1992, pp. 423--433. Google ScholarDigital Library
- T. Ostrand and E.J. Weyuker. The Distribution of Faults in a Large Industrial Software System. Proc. ACM/International Symposium on Software Testing and Analysis (ISSTA2002), Rome, Italy, July 2002, pp. 55--64. Google ScholarDigital Library
- T. Ostrand and E.J. Weyuker. How to Measure Success of Software Prediction Models. Proc. Fourth International Workshop on Software Quality Assurance, Dubrovnik, Croatia, Sept 2007. Google ScholarDigital Library
- T.J. Ostrand, E.J. Weyuker, and R.M. Bell. Where the Bugs Are. Proc. ACM/International Symposium on Software Testing and Analysis (ISSTA2004), Boston, MA, July 2004. Google ScholarDigital Library
- T.J. Ostrand, E.J. Weyuker, and R.M. Bell. Predicting the Location and Number of Faults in Large Software Systems. IEEE Trans. on Software Engineering, Vol 31, No 4, April 2005. Google ScholarDigital Library
- T.J. Ostrand, E.J. Weyuker, and R.M. Bell. Automating Algorithms for the Identification of Fault-Prone Files. Proc. ACM/International Symposium on Software Testing and Analysis (ISSTA2007), London, England, July 2007. Google ScholarDigital Library
- M. Pighin and A. Marzona. An Empirical Analysis of Fault Persistence Through Software Releases. Proc. IEEE/ACM ISESE 2003, pp. 206--212. Google ScholarDigital Library
- G. Succi, W. Pedrycz, M. Stefanovic, and J. Miller. Practical Assessment of the Models for Identification of Defect-prone Classes in Object-oriented Commercial Systems Using Design Metrics. Journal of Systems and Software, Vol 65, No 1, Jan 2003, pp. 1 -- 12. Google ScholarDigital Library
- SAS Institute Inc. SAS/STAT 9.1 User's Guide, SAS Institute, Cary, NC, 2004.Google Scholar
Index Terms
- Software engineering research: from cradle to grave
Recommendations
Where the bugs are
ISSTA '04: Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysisThe ability to predict which files in a large software system are most likely to contain the largest numbers of faults in the next release can be a very valuable asset. To accomplish this, a negative binomial regression model using information from ...
Automating algorithms for the identification of fault-prone files
ISSTA '07: Proceedings of the 2007 international symposium on Software testing and analysisThis research investigates ways of predicting which files would be most likely to contain large numbers of faults in the next release of a large industrial software system. Previous work involved making predictions using several different models ranging ...
Where the bugs are
The ability to predict which files in a large software system are most likely to contain the largest numbers of faults in the next release can be a very valuable asset. To accomplish this, a negative binomial regression model using information from ...
Comments