Mining Co-location Relationships among Bug Reports to Localize Fault-Prone Modules

Abstract

SUMMARYAutomated bug localization is an important issue in software engineering. In the last few decades, various proactive and reactive localization approaches have been proposed to predict the fault-prone software modules. However, most proactive or reactive approaches need source code information or software complexity metrics to perform localization. In this paper, we propose a reactive approach which considers only bug report information and historical revision logs. In our approach, the colocation relationships among bug reports are explored to improve the prediction accuracy of a state-of-the-art learning method. Studies on three open source projects reveal that the proposed scheme can consistently improve the prediction accuracy in all three software projects by nearly 11.6% on average.

Prioritizing code documentation effort: Can we do it simpler but better?

“…ODE documentations play an important role in software quality assurance [1][2][3][4][5][6][25][26][27][28][29][30]. High quality code documentation is helpful for program comprehension [31][32][33], test case generation [55][56][57][58][59], API Recommendation [62][63][64][65][66][67], fault localization [5,[68][69][70][71][72][73][74], bug detection [77][78][79], and program repair [84]. However, many studies [7][8][9][10] point out that, due to time and monetary pressures, developers are often unable to write documents for all modules in a project.…”

An Identification Method of Related Group of Threads for a Recent Bug Thread by Peak Characteristics of Similarities

“…The bug threads that have dependent relationships each other are organized as "group thread". Every time a recent bug is reported, developers find the group thread which the recent bug thread has dependent relationships with bug threads in, that is called "related group thread" to improve their discussion (Black, 2002;Chen et al, 2010). Because there are dozens of group thread, it is difficult for developers to find the related group thread (Zimmermann, 2009;Gall et al, 2003).…”