Coping with an open bug repository
eclipse '05 Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange
Proceedings of the 28th international conference on Software engineering
An Adaptation of the Vector-Space Model for Ontology-Based Information Retrieval
IEEE Transactions on Knowledge and Data Engineering
A study on automatically extracted keywords in text categorization
ACL-44 Proceedings of the 21st International Conference on Computational Linguistics and the 44th annual meeting of the Association for Computational Linguistics
Assigning bug reports using a vocabulary-based expertise model of developers
MSR '09 Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
Improving bug triage with bug tossing graphs
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Proceedings of the 8th Working Conference on Mining Software Repositories
ReLink: recovering links between bugs and changes
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
DREX: Developer Recommendation with K-Nearest-Neighbor Search and Expertise Ranking
APSEC '11 Proceedings of the 2011 18th Asia-Pacific Software Engineering Conference
Proceedings of the 34th International Conference on Software Engineering
Developer prioritization in bug repositories
Proceedings of the 34th International Conference on Software Engineering
How to Recommend Appropriate Developers for Bug Fixing?
COMPSAC '12 Proceedings of the 2012 IEEE 36th Annual Computer Software and Applications Conference
| Hi-index | 0.00 |
With a great number of software applications that have been developed, software maintenance has become an important and challenging task, particularly due to the increasing scale of software projects. Even if developers can create and update bug reports in bug repositories to support software maintenance, a large software project receives a large number of bug reports each day. For reducing the workload of developers, many researchers and software engineers have begun recommending appropriate developers to fix bugs. This process is called bug triage and is a hot research topic for software maintenance. In this paper, we propose a hybrid bug triage algorithm, combining a probability model and an experience model to rank all candidate developers for fixing a new bug. For this study, we adopted the smoothed Unigram Model (UM) instead of the traditional Vector Space Model (VSM) to search similar bug reports. In the probability model, we used a social network to analyze the probability of fixing a new bug for a candidate developer. We first proposed to add a new feature (the number of re-opened bugs) in order to get the fixing probability. In the experience model, we considered the number of fixed bugs and fixing cost for each candidate developer as the estimate factor. In addition, we introduced a new concept, activity factor, to better model developers' experience. We performed the experiments on two large-scale, open source projects. The results show that our method can effectively recommend the best developer for fixing bugs.