Frequently Asked Questions in Bug Reports

dc.contributor.authorBreu, Silviaeng
dc.contributor.authorPremraj, Rahuleng
dc.contributor.authorSillito, Jonathaneng
dc.contributor.authorZimmermann, Thomaseng
dc.date.accessioned2009-03-23T16:05:29Z
dc.date.available2009-03-23T16:05:29Z
dc.date.issued2009-03-23T16:05:29Z
dc.description.abstractBug tracking systems play a central role in software development since they allow users and developers to submit and discuss bugs and new features. To better understand information and communication needs in bug tracking, we analysed what questions are asked in bug reports. We sampled 600 bug reports from the MOZILLA and ECLIPSE projects and located 947 questions in the reports. Next, we used an open card sort and identified eight categories of questions, which can further be broken down into forty groups. We show the value of this catalogue of frequently asked questions with a large quantitative and qualitative study on when questions are asked and how they are answered. A consequence of our results is that constant user involvement is crucial for successful bug reports and that better tools are needed to support this.eng
dc.description.refereedNoeng
dc.identifier.department2009-924-03eng
dc.identifier.doihttp://dx.doi.org/10.11575/PRISM/31259
dc.identifier.urihttp://hdl.handle.net/1880/47006
dc.language.isoengeng
dc.publisher.corporateUniversity of Calgaryeng
dc.publisher.facultyScienceeng
dc.subjectSoftware Engineeringeng
dc.subjectHuman Factorseng
dc.subjectManagementeng
dc.subjectMeasurementeng
dc.subject.otherTesting and debugging, distribution, maintenance and enhancementeng
dc.titleFrequently Asked Questions in Bug Reportseng
dc.typetechnical reporteng
thesis.degree.disciplineComputer Scienceeng
Files
Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
2009-924-03.pdf
Size:
1.03 MB
Format:
Adobe Portable Document Format
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.86 KB
Format:
Item-specific license agreed upon to submission
Description: