Article

Supporting bug investigation using history analysis

Author:

Francisco ServantAuthors Info & Claims

ASE '13: Proceedings of the 28th IEEE/ACM International Conference on Automated Software Engineering

Pages 754 - 757

https://doi.org/10.1109/ASE.2013.6693150

Published: 11 November 2013 Publication History

Publisher Site Get Access

Abstract

In my research, I propose an automated technique to support bug investigation by using a novel analysis of the history of the source code. During the bug-fixing process, developers spend a high amount of manual effort investigating the bug in order to answer a series of questions about it. My research will support developers in answering the following questions about a bug: Who is the most suitable developer to fix the bug?, Where is the bug located?, When was the bug inserted? and Why was the bug inserted?

References

[1]

R. Abreu, P. Zoeteweij, and A. van Gemund. On the Accuracy of Spectrum-based Fault Localization. In Testing: Academic and Industrial Conference Practice and Research Techniques, pages 89-98, 2007.

Digital Library

[2]

J. Anvik, L. Hiew, and G. C. Murphy. Who should fix this bug? In International Conference on Software Engineering, pages 361-370, 2006.

Digital Library

[3]

J. Anvik and G. C. Murphy. Reducing the Effort of Bug Report Triage: Recommenders for Development-Oriented Decisions. ACM Transactions on Software Engineering and Methodology, 20(3):10:1-10:35, 2011.

Digital Library

[4]

T. Ball and S. G. Eick. Software visualization in the large. Computer, 29(4):33-43, 1996.

Digital Library

[5]

D. Cubranic. Automatic Bug Triage using Text Categorization. In International Conference on Software Engineering & Knowledge Engineering, pages 92-97, 2004.

[6]

L. Erlikh. Leveraging Legacy System Dollars for E-Business. IT professional, 2(3):17-23, 2000.

Digital Library

[7]

D. J. Gilmore. Models of Debugging. Acta Psychologica, 78(1):151-172, 1991.

[8]

T. Gîrba, A. Kuhn, M. Seeberger, and S. Ducasse. How Developers Drive Software Evolution. In Workshop on Principles of Software Evolution, 2005.

Digital Library

[9]

L. Hattori, M. Lungu, and M. Lanza. Replaying past changes in multideveloper projects. In Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE), pages 13-22, 2010.

Digital Library

[10]

R. Holmes and A. Begel. Deep Intellisense: a Tool for Rehydrating Evaporated Information. In International Working Conference on Mining Software Repositories, pages 23-26, 2008.

Digital Library

[11]

J. A. Jones, M. J. Harrold, and J. Stasko. Visualization of Test Information to Assist Fault Localization. In International Conference on Software Engineering, pages 467-477, 2002.

Digital Library

[12]

A. J. Ko, R. DeLine, and G. Venolia. Information Needs in Collocated Software Development Teams. In International Conference on Software Engineering, pages 344-353, 2007.

Digital Library

[13]

T. D. LaToza and B. A. Myers. Hard-to-Answer Questions about Code. In Evaluation and Usability of Programming Languages and Tools, pages 8:1-8:6, 2010.

Digital Library

[14]

B. Liblit, M. Naik, A. X. Zheng, A. Aiken, and M. I. Jordan. Scalable Statistical Bug Isolation. In Programming Language Design and Implementation, PLDI '05, pages 15-26.

Digital Library

[15]

D. Matter, A. Kuhn, and O. Nierstrasz. Assigning Bug Reports using a Vocabulary-Based Expertise Model of Developers. Mining of Software Repositories, 2009.

Digital Library

[16]

F. Servant and J. A. Jones. History Slicing. In International Conference on Automated Software Engineering, pages 452-455, 2011.

Digital Library

[17]

F. Servant and J. A. Jones. History Slicing : Assisting Code-Evolution Tasks. In Foundations of Software Engineering, pages 43:1-43:11, 2012.

Digital Library

[18]

F. Servant and J. A. Jones. WhoseFault: Automatic Developer-to-Fault Assignment through Fault Localization. In International Conference on Software Engineering, 2012.

Digital Library

[19]

F. Servant and J. A. Jones. Chronos: Visualizing Slices of Source-Code History. In IEEE Working Conference on Software Visualization, 2013.

[20]

F. Servant, J. A. Jones, and A. Van Der Hoek. CASI: Preventing Indirect Conflicts through a Live Visualization. In Workshop on Cooperative and Human Aspects of Software Engineering, pages 39-46, 2010.

Digital Library

[21]

R. Shokripour, J. Anvik, Z. M. Kasirun, and S. Zamani. Why so Complicated? Simple Term Filtering and Weighting for Location-based Bug Report Assignment Recommendation. In Mining of Software Repositories, pages 2-11, 2013.

Digital Library

[22]

I. Vessey. Expertise in Debugging Computer Programs: A Process Analysis. International Journal of Man-Machine Studies, 23(5):459-494, 1985.

[23]

L. Voinea, A. Telea, and J. J. van Wijk. Cvsscan: Visualization of code evolution. In ACM Symposium on Software visualization, pages 47-56, 2005.

Digital Library

[24]

A. von Mayrhauser and A. M. Vans. Program Understanding Behavior during Debugging of Large Scale Software. In Workshop on Empirical Studies of Programmers, pages 157-179, 1997.

Digital Library

[25]

R. Wettel and M. Lanza. Visualizing software systems as cities. In International Workshop on Visualizing Software for Understanding and Analysis, pages 92-99, 2007.

Cited By

Jin XServant F(2023)HybridCISave: A Combined Build and Test Selection Approach in Continuous IntegrationACM Transactions on Software Engineering and Methodology10.1145/357603832:4(1-39)Online publication date: 26-May-2023
https://dl.acm.org/doi/10.1145/3576038
Al Safwan KElarnaoty MServant F(2022)Developers’ need for the rationale of code commitsJournal of Systems and Software10.1016/j.jss.2022.111320189:COnline publication date: 1-Jul-2022
https://dl.acm.org/doi/10.1016/j.jss.2022.111320
Jin XServant F(2021)What helped, and what did not?Proceedings of the 43rd International Conference on Software Engineering10.1109/ICSE43902.2021.00031(213-225)Online publication date: 22-May-2021
https://dl.acm.org/doi/10.1109/ICSE43902.2021.00031
Show More Cited By

Recommendations

Adaptive bug prediction by analyzing project history
Effective Bug Triage Based on Historical Bug-Fix Information
ISSRE '14: Proceedings of the 2014 IEEE 25th International Symposium on Software Reliability Engineering

For complex and popular software, project teams could receive a large number of bug reports. It is often tedious and costly to manually assign these bug reports to developers who have the expertise to fix the bugs. Many bug triage techniques have been ...
Detect Related Bugs from Source Code Using Bug Information
COMPSAC '10: Proceedings of the 2010 IEEE 34th Annual Computer Software and Applications Conference

Open source projects often maintain open bug repositories during development and maintenance, and the reporters often point out straightly or implicitly the reasons why bugs occur when they submit them. The comments about a bug are very valuable for ...

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences

ASE '13: Proceedings of the 28th IEEE/ACM International Conference on Automated Software Engineering

November 2013

765 pages

ISBN:9781479902156

General Chair:
Ewen Denney
SGT, NASA, Ames Research Center, Moffett Field
,
Program Chairs:
Tevfik Bultan
University of California, Santa Barbara
,
Andreas Zeller
Saarland University, Saarbrücken, Germany

Sponsors

NASA: National Aeronatics and Space Administration
SIGAI: ACM Special Interest Group on Artificial Intelligence
IEEE: IEEE Computer Society Technical Committee on Design Automation
SIGSOFT: ACM Special Interest Group on Software Engineering
Microsoft: Microsoft

Publisher

IEEE Press

Publication History

Published: 11 November 2013

Check for updates

Qualifiers

Article

Conference

ASE '13

Sponsor:

NASA
SIGAI
IEEE
SIGSOFT
Microsoft

ASE '13: Automated Software Engineering

November 11 - 15, 2013

CA, Silicon Valley, USA

Acceptance Rates

Overall Acceptance Rate 82 of 337 submissions, 24%

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

5
Total Citations
View Citations
26
Total Downloads

Downloads (Last 12 months)0
Downloads (Last 6 weeks)0

Reflects downloads up to 09 Nov 2024

Other Metrics

View Author Metrics

Citations

Cited By

Jin XServant F(2023)HybridCISave: A Combined Build and Test Selection Approach in Continuous IntegrationACM Transactions on Software Engineering and Methodology10.1145/357603832:4(1-39)Online publication date: 26-May-2023
https://dl.acm.org/doi/10.1145/3576038
Al Safwan KElarnaoty MServant F(2022)Developers’ need for the rationale of code commitsJournal of Systems and Software10.1016/j.jss.2022.111320189:COnline publication date: 1-Jul-2022
https://dl.acm.org/doi/10.1016/j.jss.2022.111320
Jin XServant F(2021)What helped, and what did not?Proceedings of the 43rd International Conference on Software Engineering10.1109/ICSE43902.2021.00031(213-225)Online publication date: 22-May-2021
https://dl.acm.org/doi/10.1109/ICSE43902.2021.00031
Bowes DPetrić JHall T(2020)BugVisProceedings of the 28th International Conference on Program Comprehension10.1145/3387904.3389299(436-440)Online publication date: 13-Jul-2020
https://dl.acm.org/doi/10.1145/3387904.3389299
Jin XServant FRothermel GBae D(2020)A cost-efficient approach to building in continuous integrationProceedings of the ACM/IEEE 42nd International Conference on Software Engineering10.1145/3377811.3380437(13-25)Online publication date: 27-Jun-2020
https://dl.acm.org/doi/10.1145/3377811.3380437

View Options

Get Access

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Media

Figures

Other

Tables

View Table of Contents