A qualitative study on debugging under an enterprise IDE

Zayour, Iyad; Hamdar, Ali

doi:10.1016/j.infsof.2015.10.010

Cited by 10 publications

(8 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In possession of such data, it will still be possible to apply machine learning techniques to obtain patterns that may suggest potential failures in the production of software according to the psychophysiological standard of each developer, en-abling the creation of intelligent and adaptable IDEs to the user, in addition to tactical resources for prioritizing refactoring in software units. S04 Crk and Kluthe [11] S05 Dur [ [79]…”

Section: Discussionmentioning

confidence: 99%

Usage of Psychophysiological Data as an Improvement in the Context of Software Engineering: A Systematic Mapping Study

Vieira

Farias

2020

XVI Brazilian Symposium on Information Systems

View full text Add to dashboard Cite

In recent years, many studies have applied wearable devices to capture psychophysiological data from software developers. However, the current literature lacks investigations that classify the studies and point out gaps to be explored. This article, therefore, seeks to present a comprehensive overview of the literature by classifying and creating a systematic map of the works. Besides, it seeks to pinpoint research gaps, challenges, and trends. Based on widely known guidelines, a systematic mapping of the literature was designed and run to answer eight research questions. After applying a careful filtering process, we selected 27 representative studies from a sample of 2,084 potentially relevant works retrieved from seven digital libraries. The main results are: a classification scheme of the published studies was produced; there is no predominance of the devices used to capture psychophysiological data; over 50% of the studies have explored indicators related to mental states and neural activity; and 80% have analyzed composite data to understand the cognitive load and in the context of understanding debugging programs and strategies. Our findings can benefit researchers and students by creating a systematic map of the literature, being a starting point for future research.

show abstract

Section: Discussionmentioning

confidence: 99%

Usage of Psychophysiological Data as an Improvement in the Context of Software Engineering: A Systematic Mapping Study

Vieira

Farias

2020

XVI Brazilian Symposium on Information Systems

View full text Add to dashboard Cite

show abstract

“…Developers use a variety of debugging strategies. Developers often follow a simple hypothesis testing strategy [15,27], speculating about the cause of a defect based on their experience with similar defects [1,6] and clues they gather about the program behavior, state, or output [21,23]. Developers then test their hypotheses by editing their code [2,28] or inspecting the program's behavior and state [15,21].…”

Section: Related Workmentioning

confidence: 99%

An Exploratory Study of Debugging Episodes

Alaboudi,

LaToza

2021

Preprint

View full text Add to dashboard Cite

Many studies have long investigated how developers debug, shaping our understanding of debugging and helping motivate the creation of more effective tools. However, less is known about the typical progression of debugging in real world settings. In this study, we focus on characterizing debugging episodes from the moment at which developers first encounter a defect to the moment at which it is resolved. We investigate the typical duration and frequency of debugging episodes and the typical activities which occur. We observed developers by watching professional developers at work in live-streamed programming sessions. Using this data source, we curated 15 sessions in which 11 professional developers worked for 30 hours. We then systematically coded the debugging episodes and activities that occurred within these videos, yielding a dataset of 2137 debugging activities and 1407 programming activities. We found that debugging was frequent, even in programming work, occurring once every eight minutes. Debugging episodes vary greatly in time, with most being less than a few minutes and a few as more than 100 minutes. However, most debugging time is spent in long debugging episodes. We found no single activity that dominated debugging time, and long debugging episodes often involved many diverse activities. Finally, we found that,in terms of the activities developers did, programming and debugging were remarkably similar, particularly in the frequency of editing and browsing code.

show abstract

“…Zayour [20] studied the difficulties faced by developers when debugging in IDEs and reported that the features of the IDE affect the times spent by developers on debugging activities.…”

Section: Related Workmentioning

confidence: 99%

“…Interactive debugging consists of using a tool, i.e., a debugger to detect, locate, and correct a fault in a program. It is a process also known as program animation, stepping, or following execution [20]. Developers often refer to this process simply as debugging, because several IDEs provide debuggers to support debugging.…”

Section: Debugging and Interactive Debuggingmentioning

confidence: 99%

Swarm debugging: The collective intelligence on interactive debugging

Petrillo

Guéhéneuc

Pimenta

et al. 2019

Journal of Systems and Software

View full text Add to dashboard Cite

One of the most important tasks in software maintenance is debugging. To start an interactive debugging session, developers usually set breakpoints in an integrated development environment and navigate through different paths in their debuggers. We started our work by asking what debugging information is useful to share among developers and study two pieces of information: breakpoints (and their locations) and sessions (debugging paths).To answer our question, we introduce the Swarm Debugging concept to frame the sharing of debugging information, the Swarm Debugging Infrastructure (SDI) with which practitioners and researchers can collect and share data about developers' interactive debugging sessions, and the Swarm Debugging Global View (GV) to display debugging paths. Using the SDI, we conducted a large study with professional developers to understand how developers set breakpoints. Using the GV, we also analyzed professional developers in two studies and collected data about their debugging sessions. Our observations and the answers to our research questions suggest that sharing and visualizing debugging data can support debugging activities.

show abstract

A qualitative study on debugging under an enterprise IDE

Cited by 10 publications

References 11 publications

Usage of Psychophysiological Data as an Improvement in the Context of Software Engineering: A Systematic Mapping Study

Usage of Psychophysiological Data as an Improvement in the Context of Software Engineering: A Systematic Mapping Study

An Exploratory Study of Debugging Episodes

Swarm debugging: The collective intelligence on interactive debugging

Contact Info

Product

Resources

About