Advertisement

Abstract

Bug reports in widely used defect tracking systems contains standard and mandatory fields like product name, component name, version number and operating system. Such fields provide important information required by developers during bug fixing. Previous research shows that bug reporters often assign incorrect values for such fields which cause problems and delays in bug fixing. We conduct an empirical study on the issue of incorrect component assignments or component reassignments in bug reports. We perform a case study on open-source Eclipse and Mozilla projects and report results on various aspects such as the percentage of reassignments, distribution across number of assignments until closure of a bug and time difference between creation and reassignment event. We perform a series of experiments using a machine learning framework for two prediction tasks: categorizing a given bug report into a pre-defined list of components and predicting whether a given bug report will be reassigned. Experimental results demonstrate correlation between terms present in bug reports (textual documents) and components which can be used as linguistic indicators for the task of component prediction. We study component reassignment graphs and reassignment probabilities and investigate their usefulness for the task of component reassignment prediction.

Keywords

Mining Software Repositories (MSR) Empirical Software Engineering and Measurements (ESEM) Automated Software Engineering (ASE) 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Bettenburg, N., Just, S., Schröter, A., Weiss, C., Premraj, R., Zimmermann, T.: What makes a good bug report? In: International Symposium on Foundations of software Engineering, SIGSOFT 2008/FSE-16, pp. 308–318. ACM, New York (2008)CrossRefGoogle Scholar
  2. 2.
    Bettenburg, N., Just, S., Schröter, A., Weiss, C., Premraj, R., Zimmermann, T.: Quality of bug reports in eclipse. In: OOPSLA Workshop on Eclipse Technology eXchange. ACM Press, New York (2007)Google Scholar
  3. 3.
    Bettenburg, N., Premraj, R., Zimmermann, T., Kim, S.: Extracting structural information from bug reports. In: Working Conference on Mining Software Repositories, MSR 2008, pp. 27–30. ACM, New York (2008)CrossRefGoogle Scholar
  4. 4.
    Bhattacharya, P., Neamtiu, I.: Fine-grained incremental learning and multi-feature tossing graphs to improve bug triaging. In: Inter. Conference on Software Maintenance, ICSM 2010, pp. 1–10. IEEE Computer Society, Washington, DC (2010)CrossRefGoogle Scholar
  5. 5.
    Breu, S., Premraj, R., Sillito, J., Zimmermann, T.: Frequently asked questions in bug reports. Technical Report 2009-924-03, University of Calgary (March 2009)Google Scholar
  6. 6.
    Carpenter, B., Baldwin, B.: Natural Language Processing with LingPipe 4, draft edition. LingPipe Publishing, New York (2011)Google Scholar
  7. 7.
    Chen, L., Wang, X., Liu, C.: An approach to improving bug assignment with bug tossing graphs and bug similarities. JSW Journal of Software 6(3), 421–427 (2011)MathSciNetGoogle Scholar
  8. 8.
    Guo, P.J., Zimmermann, T., Nagappan, N., Murphy, B.: ”not my bug!” and other reasons for software bug report reassignments. In: Computer Supported Cooperative Work, CSCW 2011, pp. 395–404. ACM, New York (2011)Google Scholar
  9. 9.
    Guo, P.J., Zimmermann, T., Nagappan, N., Murphy, B.: ”Not My Bug!” and Other Reasons for Software Bug Report Reassignments. In: ACM Conference on Computer Supported Cooperative Work (2011)Google Scholar
  10. 10.
    Hooimeijer, P., Weimer, W.: Modeling bug report quality. In: IEEE/ACM International Conference on Automated Software Engineering, ASE 2007, pp. 34–43. ACM, New York (2007)CrossRefGoogle Scholar
  11. 11.
    Jeong, G., Kim, S., Zimmermann, T.: Improving bug triage with bug tossing graphs. In: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2009, pp. 111–120. ACM, New York (2009)CrossRefGoogle Scholar
  12. 12.
    Zimmermann, T., Premraj, R., Bettenburg, N., Just, S., Schröter, A., Weiss, C.: What makes a good bug report? IEEE Transactions on Software Engineering 36(5), 618–643 (2010)CrossRefGoogle Scholar
  13. 13.
    Zimmermann, T., Premraj, R., Sillito, J., Breu, S.: Improving bug tracking systems. In: Companion to the 31th International Conference on Software Engineering (May 2009)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Ashish Sureka
    • 1
  1. 1.Indraprastha Institute of Information Technology (IIIT-D)New DelhiIndia

Personalised recommendations