Transitioning Fault Prediction Models to a New Environment

We describe the application and evaluation of fault prediction algorithms to a project developed by a Swedish company that transitioned from waterfall to agile development methods. The project used two different version control systems and a separate bug tracking system during its lifetime. The algorithms were originally designed for use on systems implemented with a traditional waterfall process at American companies that maintained their project records in an integrated database system that combined bug recording and version control. We compare the performance of the original prediction model on the American systems to the results obtained in the Swedish environment in both its pre-agile and agile stages. We also consider the impact of additional variables in the model.

[1]  Tracy Hall,et al.  Researcher Bias: The Use of Machine Learning in Software Defect Prediction , 2014, IEEE Transactions on Software Engineering.

[2]  Elaine J. Weyuker,et al.  Predicting the location and number of faults in large software systems , 2005, IEEE Transactions on Software Engineering.

[3]  Barbara Kitchenham,et al.  What's up with software metrics? - A preliminary mapping study , 2010, J. Syst. Softw..

[4]  Michele Lanza,et al.  Evaluating defect prediction approaches: a benchmark and an extensive comparison , 2011, Empirical Software Engineering.

[5]  Ruchika Malhotra,et al.  A systematic review of machine learning techniques for software fault prediction , 2015, Appl. Soft Comput..

[6]  Harald C. Gall,et al.  Using Socio-Technical Networks to Predict Failures , 2009 .

[7]  Audris Mockus,et al.  Predicting risk of software changes , 2000, Bell Labs Technical Journal.

[8]  Daniel Sundmark,et al.  Can we do useful industrial software engineering research in the shadow of lean and agile? , 2013, 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI).

[9]  Ayse Basar Bener,et al.  A systematic literature review on the applications of Bayesian networks to predict software quality , 2015, Software Quality Journal.

[10]  Harald C. Gall,et al.  Cross-project Defect Prediction , 2009 .

[11]  Tracy Hall,et al.  A Systematic Literature Review on Fault Prediction Performance in Software Engineering , 2012, IEEE Transactions on Software Engineering.

[12]  Elaine J. Weyuker,et al.  Do too many cooks spoil the broth? Using the number of developers to enhance defect prediction models , 2008, Empirical Software Engineering.

[13]  Elaine J. Weyuker,et al.  Does measuring code change improve fault prediction? , 2011, Promise '11.

[14]  Patrik Berander,et al.  From Traditional to Streamline Development — opportunities and challenges , 2008 .

[15]  N. Nagappan,et al.  Use of relative code churn measures to predict system defect density , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[16]  Victor R. Basili,et al.  The influence of organizational structure on software quality , 2008, 2008 ACM/IEEE 30th International Conference on Software Engineering.

[17]  Lionel C. Briand,et al.  A systematic and comprehensive investigation of methods to build and evaluate fault prediction models , 2010, J. Syst. Softw..

[18]  RadjenovićDanijel,et al.  Software fault prediction metrics , 2013 .

[19]  Patrik Berander,et al.  From Traditional to Streamline Development - opportunities and challenges , 2008, Softw. Process. Improv. Pract..

[20]  Harald C. Gall,et al.  Cross-project defect prediction: a large scale experiment on data vs. domain vs. process , 2009, ESEC/SIGSOFT FSE.

[21]  Elaine J. Weyuker,et al.  The limited impact of individual developer data on software defect prediction , 2011, Empirical Software Engineering.

[22]  Ye Yang,et al.  An investigation on the feasibility of cross-project defect prediction , 2012, Automated Software Engineering.