Debugging Activity Blueprint
Document type :
Communication dans un congrès avec actes
Permalink :
Title :
Debugging Activity Blueprint
Author(s) :
Bourcier, Valentin [Auteur]
Centre de Recherche en Informatique, Signal et Automatique de Lille - UMR 9189 [CRIStAL]
Reflective Evolution of Ever-running Software Systems [EVREF]
Bergel, Alexandre [Auteur]
RelationalAI [Bern]
Etien, Anne [Auteur]
Centre de Recherche en Informatique, Signal et Automatique de Lille - UMR 9189 [CRIStAL]
Reflective Evolution of Ever-running Software Systems [EVREF]
Costiou, Steven [Auteur]
Centre de Recherche en Informatique, Signal et Automatique de Lille - UMR 9189 [CRIStAL]
Reflective Evolution of Ever-running Software Systems [EVREF]
Centre de Recherche en Informatique, Signal et Automatique de Lille - UMR 9189 [CRIStAL]
Reflective Evolution of Ever-running Software Systems [EVREF]
Bergel, Alexandre [Auteur]
RelationalAI [Bern]
Etien, Anne [Auteur]
Centre de Recherche en Informatique, Signal et Automatique de Lille - UMR 9189 [CRIStAL]
Reflective Evolution of Ever-running Software Systems [EVREF]
Costiou, Steven [Auteur]
Centre de Recherche en Informatique, Signal et Automatique de Lille - UMR 9189 [CRIStAL]
Reflective Evolution of Ever-running Software Systems [EVREF]
Conference title :
The twelfth IEEE Working Conference on Software Visualization (VISSOFT 2024)
City :
Flagstaff (Arizona)
Country :
Etats-Unis d'Amérique
Start date of the conference :
2024-10-06
Journal title :
Pharo
English keyword(s) :
Debugging
Debugging behavior
IDE
visualization
polymetric views
Debugging behavior
IDE
visualization
polymetric views
HAL domain(s) :
Informatique [cs]/Génie logiciel [cs.SE]
English abstract : [en]
Empirically analyzing debugging activity is notoriously difficult. In particular, aggregating data (obtained from either observation or event logging) to verify hypotheses on developers' behavior is known to be challenging. ...
Show more >Empirically analyzing debugging activity is notoriously difficult. In particular, aggregating data (obtained from either observation or event logging) to verify hypotheses on developers' behavior is known to be challenging. Overall, the difficulty of studying debugging activities contributes to the need for more empirical evidence on how practitioners use debuggers.We propose debugging activity blueprint as a visual tool to analyze and navigate through all the events recorded in a programming environment. Our blueprint is a polymetric view representing the interaction between debuggers and other programming tools. Our blueprint highlights the flow of a debugging activity across the tools an IDE offers. An exploratory use case over three participants and two debugging tasks indicates that our blueprint supports a fine-grained analysis of complex debugging scenarios.Show less >
Show more >Empirically analyzing debugging activity is notoriously difficult. In particular, aggregating data (obtained from either observation or event logging) to verify hypotheses on developers' behavior is known to be challenging. Overall, the difficulty of studying debugging activities contributes to the need for more empirical evidence on how practitioners use debuggers.We propose debugging activity blueprint as a visual tool to analyze and navigate through all the events recorded in a programming environment. Our blueprint is a polymetric view representing the interaction between debuggers and other programming tools. Our blueprint highlights the flow of a debugging activity across the tools an IDE offers. An exploratory use case over three participants and two debugging tasks indicates that our blueprint supports a fine-grained analysis of complex debugging scenarios.Show less >
Language :
Anglais
Peer reviewed article :
Oui
Audience :
Internationale
Popular science :
Non
ANR Project :
Collections :
Source :
Submission date :
2024-09-18T02:21:44Z
Files
- document
- Open access
- Access the document
- debugging-activity-blueprint.pdf
- Open access
- Access the document