Debug concern navigator

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

Abstract

Programmers tend to spend a lot of time debugging code. They check the erroneous phenomena, navigate the code, search the past bug fixes, and modify the code. If a sequence of these debug activities can be automated, programmers can use their time for more creatives task. To address this problem, this paper purposes dcNavi (Debug Concern Navigator), a concern-oriented recommendation sys-tem for debugging. The dcNavi provides appropriate hints to programmers according to their debug concerns such as "how to handle this exception" and "how to use this API". We propose the notion of DCG (Debug Concern Graph), an extension of the Concern Graphs. A DCG appends a set of debugging information such as past bug fixes and test results to a concern graph. Debug hints are provided in the form of code snippets showing the sample code modification before and after a bug fix.

Original languageEnglish
Title of host publicationSEKE 2011 - Proceedings of the 23rd International Conference on Software Engineering and Knowledge Engineering
Pages197-202
Number of pages6
Publication statusPublished - 2011
EventSEKE 2011 - Proceedings of the 23rd International Conference on Software Engineering and Knowledge Engineering - Miami, FL, United States
Duration: Jul 7 2011Jul 9 2011

Other

OtherSEKE 2011 - Proceedings of the 23rd International Conference on Software Engineering and Knowledge Engineering
CountryUnited States
CityMiami, FL
Period7/7/117/9/11

All Science Journal Classification (ASJC) codes

  • Software

Fingerprint Dive into the research topics of 'Debug concern navigator'. Together they form a unique fingerprint.

Cite this