Triaging incoming change requests: bug or commit history, or code authorship?
Date
2013-05-08Author
Hossen, Md Kamal
Advisor
Kagdi, Huzefa HatimbhaiMetadata
Show full item recordCitation
Hossen, Md Kamal. 2013. Triaging Incoming Change Requests: Bug or Commit History, or Code Authorship?. -- In Proceedings: 9th Annual Symposium: Graduate Research and Scholarly Projects. Wichita, KS: Wichita State University, p.22-23
Abstract
Combining information retrieval and source code authorship information as a novel approach to recommend expert developers to assist with software change request is presented. This approach is based on the presence of code authorship information in source code files and does not require software repository mining or training for past bugs/issues.
Our approach is compared with two other representative approaches 1) using machine learning on past bug reports and 2) based on commit logs, over three open source systems ArgoUML, Jedit and MuCommander. Without the need of any historical change information our approach provides recommendation accuracies equivalent or better than the two compared approaches.
Description
Paper presented to the 9th Annual Symposium on Graduate Research and Scholarly Projects (GRASP) held at the Marcus Welcome Center, Wichita State University, May 8, 2013.
Research completed at the Department of Electrical Engineering and Computer Science, College of Engineering