Abstract
As the scale and complexity of software products increase, software maintenance on bug resolution has become a challenging work. In the process of software implementation, developers often use bug reports, source code and change history to help solve bugs. However, hundreds of bug reports are being submitted every day. It is time-consuming and effortless for developers to review all the bug reports. To facilitate the assignment of bug reports, existing developer recommendation systems typically recommend the developer who has the fullest potential. However, bug reports are highly varied; time that the developers may spend fixing them is also important. To address the problem of developer recommendation, we propose a developer recommendation system with awareness of accuracy and cost (DRAC). This recommendation system is based on modern portfolio theory by striking a balance between accuracy and cost (time). We evaluate our approach with experiments on data collected from Bugzilla 1 . Keywords—Recommendation System; Portfolio Theory; Bug Triage; Accuracy and Cost
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
