An Automated Bug Triage Approach: A Concept Profile and Social Network Based Developer Recommendation
Generally speaking, the larger-scale open source development projects support both developers and users to report bugs in an open bug repository. Each report that appears in this repository must be triaged for fixing it. However, with huge amount of bugs are reported every day, the workload of developers is so high. In addition, most of bug reports were not assigned to correct developers for fixing so that these bugs need to be re-assigned to another developer. If the number of re-assignments to developers is large, the bug fixing time is increased. So "who are appropriate developers for fixing bug?" is an important question for bug triage. In this paper, we propose an automated developer recommendation approach for bug triage. The major contribution of our paper is to build the concept profile(CP) for extracting the bug concepts with topic terms from the documents produced by related bug reports, and we find the important developers with the high probability of fixing the given bug by using social network(SN). As a result, we get a ranked list of appropriate developers for bug fixing according to their expertise and fixing cost. The evaluation results show that our approach outperforms other developer recommendation methods.
Keywordsbug triage concept profile social network fixing cost reassignment developer recommendation
Unable to display preview. Download preview PDF.
- 2.Jalbert, N., Weimer, W.: Automated Duplicate Detection for Bug Tracking System. In: International Conference on Dependable System & Networks, pp. 52–61 (2008)Google Scholar
- 3.Matter, D., Kuhn, A., Nierstrasz, O.: Assigning Bug Reports Using a Vocabulary-based Expertise Model of Developers. In: 6th IEEE International Working Conference on Mining Software Repositories, pp. 131–140 (2009)Google Scholar
- 4.Jeong, G., Kim, S., Zimmermann, T.: Improving Bug Triage with Bug Tossing Graphs. In: 7th Joint Meeting of the European Software Engineering Conference and the ACM Symposium on the Foundations of Software Engineering, pp. 111–120 (2009)Google Scholar
- 5.Chen, I.X., Yang, C.Z., Lu, T.K., Jaygarl, H.: Implicit Social Network Model for Predicting and Tracking the Location of Faults. In: Annual IEEE International Computer Software and Applications Conference, pp. 136–143 (2008)Google Scholar
- 6.Anvik, J., Hiew, L., Murphy, G.C.: Who Should Fix This bug? In: 28th International Conference on Software Engineering, pp. 361–370 (2006)Google Scholar
- 7.Wu, W., Zhang, W., Yang, Y., Wang, Q.: DREX: Developer Recommendation with K-Nearest-Neighbor Search and Expertise Ranking. In: 18th Asia-Pacific Software Engineering Conference, pp. 389–396 (2011) Google Scholar
- 8.Park, J., Lee, M., Kim, J., Hwang, S., Kim, S.: CosTRIAGE: A Cost-Aware Triage Algorithm for Bug Reporting Systems. In: 25th AAAI Conference on Artificial Intelligence, pp. 139–144 (2011)Google Scholar
- 11.Wang, X., Zhang, L., Xie, T., Anvik, J., Sun, J.: An Approach to Detecting Duplicate Bug Reports Using Natural Language and Execution Information. In: 30th International Conference on Software Engineering, pp. 461–470 (2008)Google Scholar
- 12.Wu, R., Zhang, H., Kim, S., Cheung, S.C.: Relink: Recovering Links between Bugs and Changes. In: Joint Meeting of the European Software Engineering Conference and the ACM Symposium on the Foundations of Software Engineering, pp. 15–25 (2011)Google Scholar