A pilot study of diversity in high impact bugs

Yutaro Kashiwa, Hayato Yoshiyuki, Yusuke Kukita, Masao Ohira

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

6 Citations (Scopus)

Abstract

Since increasing complexity and scale of modern software products imposes tight scheduling and resource allocations on software development projects, a project manager must carefully triage bugs to determine which bug should be necessarily fixed before shipping. Although in the field of Mining Software Repositories (MSR) there are many promising approaches to predicting, localizing, and triaging bugs, most of them do not consider impacts of each bug on users and developers but rather treat all bugs with equal weighting, excepting a few studies on high impact bugs including security, performance, blocking, and so forth. To make MSR techniques more actionable and effective in practice, we need deeper understandings of high impact bugs. In this paper we report our pilot study on high impact bugs, which classifies bugs reported to four open source projects into six types of high impact bugs.

Original languageEnglish
Title of host publicationProceedings - 30th International Conference on Software Maintenance and Evolution, ICSME 2014
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages536-540
Number of pages5
ISBN (Electronic)9780769553030
DOIs
Publication statusPublished - Dec 4 2014
Externally publishedYes
Event30th International Conference on Software Maintenance and Evolution, ICSME 2014 - Victoria, Canada
Duration: Sep 28 2014Oct 3 2014

Publication series

NameProceedings - 30th International Conference on Software Maintenance and Evolution, ICSME 2014

Conference

Conference30th International Conference on Software Maintenance and Evolution, ICSME 2014
CountryCanada
CityVictoria
Period9/28/1410/3/14

All Science Journal Classification (ASJC) codes

  • Software

Fingerprint Dive into the research topics of 'A pilot study of diversity in high impact bugs'. Together they form a unique fingerprint.

Cite this