RAPTOR: Release-Aware and Prioritized Bug-Fixing Task Assignment Optimization

Yutaro Kashiwa

Research output: Chapter in Book/Report/Conference proceedingConference contribution

2 Citations (Scopus)

Abstract

Over a decade, many bug assignment methods have been proposed in order to assist developers to read bug reports submitted daily and numerously, and to assign an appropriate developer. However, they tend to concentrate their assignments on a small number of particular developers. Applying the methods to the projects which have releases would reduce the number of bugs that developers can fix by the next release date because the time that developers can devote to bug-fixing is limited. In this study, we propose the release-aware bug-fixing task assignment method to mitigate the task concentration and increase the number of bugs that developers can fix by the next release date. This method employs mathematical programming to find the best combination at project level while the traditional methods find the best pair of a bug and a developer (at individual level).

Original languageEnglish
Title of host publicationProceedings - 2019 IEEE International Conference on Software Maintenance and Evolution, ICSME 2019
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages629-633
Number of pages5
ISBN (Electronic)9781728130941
DOIs
Publication statusPublished - Sept 2019
Externally publishedYes
Event2019 IEEE International Conference on Software Maintenance and Evolution, ICSME 2019 - Cleveland, United States
Duration: Sept 30 2019Oct 4 2019

Publication series

NameProceedings - 2019 IEEE International Conference on Software Maintenance and Evolution, ICSME 2019

Conference

Conference2019 IEEE International Conference on Software Maintenance and Evolution, ICSME 2019
Country/TerritoryUnited States
CityCleveland
Period9/30/1910/4/19

All Science Journal Classification (ASJC) codes

  • Software
  • Safety, Risk, Reliability and Quality

Fingerprint

Dive into the research topics of 'RAPTOR: Release-Aware and Prioritized Bug-Fixing Task Assignment Optimization'. Together they form a unique fingerprint.

Cite this