Dynamic Query-Based Debugging of Object-Oriented Programs
Automated Software Engineering
Designing the whyline: a debugging interface for asking questions about program behavior
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Cost effective dynamic program slicing
Proceedings of the ACM SIGPLAN 2004 conference on Programming language design and implementation
Six Learning Barriers in End-User Programming Systems
VLHCC '04 Proceedings of the 2004 IEEE Symposium on Visual Languages - Human Centric Computing
Proceedings of the 27th international conference on Software engineering
Locating causes of program failures
Proceedings of the 27th international conference on Software engineering
Maintaining mental models: a study of developer work habits
Proceedings of the 28th international conference on Software engineering
A framework and methodology for studying the causes of software errors in programming systems
Journal of Visual Languages and Computing
| Hi-index | 0.00 |
One reason debugging is the most time-consuming part of software development is because developers struggle to map their questions about a program's behavior onto debugging tools' limited support for analyzing code. Interrogative debugging is a new debugging paradigm that allows developers to ask questions directly about their programs' output, helping them to more efficiently and accurately determine what parts of the system to understand. An interrogative debugging prototype called the Whyline is described, which has been shown to reduce debugging time by a factor of eight. Several extensions and generalizations to it are proposed, including plans for evaluating their effectiveness.