Abstract
Most bug assignment approaches utilize text classification and information retrieval techniques. These approaches use the textual contents of bug reports to build recommendation models. The textual contents of bug reports are usually of high dimension and noisy source of information. These approaches suffer from low accuracy and high computational needs. In this paper, we investigate whether using categorical fields of bug reports, such as component to which the bug belongs, are appropriate to represent bug reports instead of textual description. We build a classification model by utilizing the categorical features, as a representation, for the bug report. The experimental evaluation is conducted using three projects namely NetBeans, Freedesktop, and Firefox. We compared this approach with two machine learning based bug assignment approaches. The evaluation shows that using the textual contents of bug reports is important. In addition, it shows that the categorical features can improve the classification accuracy.
Highlights
Software maintenance is crucial in software evolution which aims to modify a software product after delivery to fix defects or to improve other attributes
We investigate whether using categorical fields is appropriate to represent bug reports instead of textual description
In order to investigate the effect of using meta-data features other than the textual content of bug report on the classification accuracy, we compare the approach that utilizes the categorical features only with two different approaches
Summary
Software maintenance is crucial in software evolution which aims to modify a software product after delivery to fix defects or to improve other attributes. It represents one of the most expensive and time-consuming phases in the whole development process. BTS allows both developers and users to submit defects, suggest enhancements, and comment on bug reports These bug reports are utilized to guide software maintenance activities in order to produce more robust systems. The assignee field represents the person in charge of resolving the bug It contains the ID of the user who was made responsible for providing a solution for a particular bug report.
Sign-in/Register to view highlights & summary 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 callMore From: International Journal of Software Engineering & Applications
Disclaimer: 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.
