Journal Article10.1145/1082983.1083147
When do changes induce fixes
Jacek Śliwerski,Thomas Zimmermann,Andreas Zeller +2 more
- 17 May 2005
- Vol. 30, Iss: 4, pp 1-5
TL;DR: In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.
read more
Abstract: As a software system evolves, programmers make changes that sometimes cause problems. We analyze CVS archives for fix-inducing changes---changes that lead to problems, indicated by fixes. We show how to automatically locate fix-inducing changes by linking a version archive (such as CVS) to a bug database (such as BUGZILLA). In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Empirical Study of Software Quality Evolution in Open Source Projects Using Agile Practices
Alessandro Murgia,Giulio Concas,Sandro Pinna,Roberto Tonelli,Ivana Turnu +4 more
TL;DR: This study analyzes the quality evolution of two open-source Java projects, Eclipse and Netbeans, using agile practices, focusing on defect absence and its relation to software metrics, such as Chidamber and Kemerer suite, and bug count over time.
Performance of Defect Prediction in Rapidly Evolving Software
Davide G. Cavezza,Roberto Pietrantuono,Stefano Russo +2 more
TL;DR: This study evaluates the performance of defect prediction in rapidly evolving software, proposing a continuous refinement approach to adapt models to changing code, and demonstrates its effectiveness in a high-commit-frequency context using the Eclipse JDT software.
When Deep Learning Meets Information Retrieval-based Bug Localization: A Survey
Feifei Niu,Chuanyi Li,Kui Liu,Xin Xia,David Lo +4 more
A Deep Ensemble Learning Method for Effort-Aware Just-In-Time Defect Prediction
TL;DR: An ensemble classifier is devised, which fuses the output of three individual classifiers to build an efficient state-of-the-art prediction model and a highly competent reinforcement learning technique is proposed to avoid false alarms in real time predictions.
Feature sets in just-in-time defect prediction: an empirical evaluation
P. Bludau,Alexander Pretschner +1 more
- 28 Sep 2022
TL;DR: In this paper , the authors evaluate existing features on six open-source projects and propose two new features sets, not yet discussed in literature, and combine all feature sets, leading to the best performing models when compared to state-of-the-art approaches.
References
Populating a Release History Database from version control and bug tracking systems
Michael Fischer,Martin Pinzger,Harald C. Gall +2 more
- 22 Sep 2003
TL;DR: An approach is introduced for populating a release history database that combines version data with bug tracking data and adds missing data not covered by version control systems such as merge points to obtain meaningful views showing the evolution of a software project.
Identifying reasons for software changes using historic databases
TL;DR: From this study several suggestions are arrived at on how to make version control data useful in diagnosing the state of a software project, without significantly increasing the overhead for the developer using the change management system.
529
Hipikat: recommending pertinent software development artifacts
Davor Cubranic,Gail C. Murphy +1 more
- 03 May 2003
TL;DR: The Hipikat tool is described, a tool that forms an implicit group memory from the information stored in a project's archives, and that recommends artifacts from the archives that are relevant to a task that a newcomer is trying to perform.
Toward understanding the rhetoric of small source code changes
TL;DR: This study reveals that there is less than 4 percent probability that a one-line change introduces a fault in the code, and that the phenomena of change differs for additions, deletions, and modifications as well as for the number of lines affected.
Analyzing and relating bug report data for feature tracking
Michael Fischer,Martin Pinzger,Harald C. Gall +2 more
- 13 Nov 2003
TL;DR: This paper analyzes the proximity of software features based on modification and problem report data that capture the system's evolutionhistory to uncover hidden relationships between features via problem report analysis and presents them in easy-to-evaluate visual form.
Related Papers (5)
Nachiappan Nagappan,Thomas Ball +1 more
- 15 May 2005
Thomas Zimmermann,Rahul Premraj,Andreas Zeller +2 more
- 20 May 2007
Ahmed E. Hassan
- 16 May 2009
Nachiappan Nagappan,Thomas Ball,Andreas Zeller +2 more
- 28 May 2006