Finding causes of program output with the Java Whyline

Debugging and diagnostic tools are some of the most important software development tools, but most expect developers choose the right code to inspect. Unfortunately, this rarely occurs. A new tool called the Whyline is described which avoids such speculation by allowing developers to select questions about a program's output. The tool then helps developers work backwards from output to its causes. The prototype, which supports Java programs, was evaluated in an experiment in which participants investigated two real bug reports from an open source project using either the Whyline or a breakpoint debugger. Whyline users were successful about three times as often and about twice as fast compared to the control group, and were extremely positive about the tool's ability to simplify diagnostic tasks in software development work. AUTHOR KEYWORDS Debugging, Whyline, slicing, instrumentation. ACM Classification Keywords D.2.5 [Testing and Debugging]: Debugging aids, tracing; H.5.2 [...

• Type: Conference
• Year: 2009
• Where: CHI
• Authors: Andrew Jensen Ko, Brad A. Myers
• Keywords: ACM Classification Keywords, CHI 2009, Debugging Aids, Human Computer Interaction, Software Development Tools