An Empirical Analysis of Software Changes on Statement Entity in Java Open Source Projects

Software projects keep changing all the time. Understanding the nature of the changes can help build higher quality projects. In this paper, the authors studied software changes on a new entity, statement. They found some types of statements are more likely to change than others. Furthermore, the authors studied software changes to fix bugs and also found some types of statements are more likely to change than others to fix bugs. These statements are more likely to cause bugs, which should be paid more attention to.

[1]  Dave Yeats,et al.  Morality and Pragmatism in Free Software and Open Source , 2009 .

[2]  Alexander Chatzigeorgiou,et al.  Predicting the probability of change in object-oriented systems , 2005, IEEE Transactions on Software Engineering.

[3]  Huan Wang,et al.  Predicting Co-Changed Software Entities in the Context of Software Evolution , 2009, 2009 International Conference on Information Engineering and Computer Science.

[4]  Xiaoyan Zhu,et al.  An empirical analysis of the FixCache algorithm , 2011, MSR '11.

[5]  Elhadi M. Shakshuki,et al.  Predicting Function Changes by Mining Revision History , 2010, 2010 Seventh International Conference on Information Technology: New Generations.

[6]  Harald C. Gall,et al.  Classifying Change Types for Qualifying Change Couplings , 2006, 14th IEEE International Conference on Program Comprehension (ICPC'06).

[7]  Ladan Tahvildari,et al.  Change Prediction in Object-Oriented Software Systems: A Probabilistic Approach , 2008, J. Softw..

[8]  Francesca da Rimini,et al.  Social Technologies and the Digital Commons , 2006 .

[9]  Sunghun Kim,et al.  Toward an understanding of bug fix patterns , 2009, Empirical Software Engineering.

[10]  Jonathan I. Maletic,et al.  Mining sequences of changed-files from version histories , 2006, MSR '06.

[11]  Hongyu Zhang.  An initial study of the growth of eclipse defects , 2008, MSR '08.

[12]  Andreas Zeller,et al.  Change Bursts as Defect Predictors , 2010, 2010 IEEE 21st International Symposium on Software Reliability Engineering.

[13]  G. Brent Hall,et al.  Using Open Source Software Components to Implement a Modular Web 2.0 Design for Map-Based Discussions , 2010, Int. J. Open Source Softw. Process..

[14]  Mahmoud O. Elish,et al.  A suite of metrics for quantifying historical changes to predict future change‐prone classes in object‐oriented software , 2013, J. Softw. Evol. Process..

[15]  Serge Demeyer,et al.  Studying software evolution information by visualizing the change history , 2004, 20th IEEE International Conference on Software Maintenance, 2004. Proceedings..

[16]  Yi Zhang,et al.  Classifying Software Changes: Clean or Buggy? , 2008, IEEE Transactions on Software Engineering.

[17]  Daniel M. Germán,et al.  An empirical study of fine-grained software modifications , 2004, 20th IEEE International Conference on Software Maintenance, 2004. Proceedings..

[18]  Oscar Nierstrasz,et al.  The Inevitable Stability of Software Change , 2007, 2007 IEEE International Conference on Software Maintenance.

[19]  Juan Fernández-Ramil,et al.  The evolution of Eclipse , 2008, 2008 IEEE International Conference on Software Maintenance.

[20]  Gail C. Murphy,et al.  Predicting source code changes by mining change history , 2004, IEEE Transactions on Software Engineering.

[21]  Sunghun Kim,et al.  Properties of Signature Change Patterns , 2006, 2006 22nd IEEE International Conference on Software Maintenance.