Dual analysis for recommending developers to resolve bugs. Issue 3 (3rd March 2015)

• Record Type: Journal Article
• Authors: Xia, Xin; Lo, David; Wang, Xinyu; Zhou, Bo
• Is Part Of: Journal of software. Volume 27:Issue 3(2015:Mar.)
• Page Start: 195
• Page End: 220
• Publication Date: 2015-03-03
• Subjects: developer recommendation -- multi‐label learning -- topic model -- composite; Software engineering -- Periodicals; Computer software -- Development -- Periodicals; Software maintenance -- Periodicals; 005.1
• DOI: 10.1002/smr.1706
• Languages: English
• ISSNs: 2047-7473

Abstract

Abstract: Bug resolution refers to the activity that developers perform to diagnose, fix, test, and document bugs during software development and maintenance. Given a bug report, we would like to recommend the set of bug resolvers that could potentially contribute their knowledge to fix it. We refer to this problem as developer recommendation for bug resolution . In this paper, we propose a new and accurate method named DevRec for the developer recommendation problem. DevRec is a composite method that performs two kinds of analysis: bug reports based analysis (BR‐Based analysis) and developer based analysis (D‐Based analysis). We evaluate our solution on five large bug report datasets including GNU Compiler Collection, OpenOffice, Mozilla, Netbeans, and Eclipse containing a total of 107, 875 bug reports. We show that DevRec could achieve recall@5 and recall@10 scores of 0.4826–0.7989, and 0.6063–0.8924, respectively. The results show that DevRec on average improves recall@5 and recall@10 scores of Bugzie by 57.55% and 39.39%, outperforms DREX by 165.38% and 89.36%, and outperforms NonTraining by 212.39% and 168.01%, respectively. Moreover, we evaluate the stableness of DevRec with different parameters, and the results show that the performance of DevRec is stable for a wide range of parameters. Copyright © 2015 John Wiley & Sons, Ltd. Abstract : We propose a new and accurate method named DevRec for the developer recommendation problem, which performs both bug report‐based analysis and developer‐based analysis. Experiment results show DevRec outperforms Bugzie, DREX, and NonTraining by a substantial margin. We evaluate DevRec on different sets of parameters, and the results show DevRec is robust on different parameters, which means developers do not need to spend much effort and time to configure our tool.