Designing the whyline: a debugging interface for asking questions about program behavior

ABSTRACT

Debugging is still among the most common and costly of programming activities. One reason is that current debugging tools do not directly support the inquisitive nature of the activity. Interrogative Debugging is a new debugging paradigm in which programmers can ask why did and even why didn't questions directly about their program's runtime failures. The Whyline is a prototype Interrogative Debugging interface for the Alice programming environment that visualizes answers in terms of runtime events directly relevant to a programmer's question. Comparisons of identical debugging scenarios from user tests with and without the Whyline showed that the Whyline reduced debugging time by nearly a factor of 8, and helped programmers complete 40% more tasks.

REFERENCES

• 1: Mikhail Auguston , Clinton Jeffery , Scott Underwood, A Framework for Automatic Debugging, Proceedings of the 17th IEEE international conference on Automated software engineering, p.217, September 23-27, 2002
• 2: Alan Blackwell , Margaret Burnett, Applying Attention Investment to End-User Programming, Proceedings of the IEEE 2002 Symposia on Human Centric Computing Languages and Environments (HCC'02), p.28, September 03-06, 2002
• 3: J. S. Briggs , S. D. Jamieson , G. W. Randall , I. C. Wand, Task time lines as a debugging tool, ACM SIGAda Ada Letters, v.XVI n.2, p.50-69, March/April 1996 [doi>10.1145/230509.230513]
• 4: Simon P. Davies, Models and theories of programming strategy, International Journal of Man-Machine Studies, v.39 n.2, p.237-267, Aug. 1993 [doi>10.1006/imms.1993.1061]
• 5: Davies, S.P. Display-based problem solving strategies in computer programming, Empirical Studies of Programmers, 6th Workshop, 1996, Washington, D.C., 59--76.
• 6: Paul Gestwicki , Bharat Jayaraman, Interactive Visualization of Java Programs, Proceedings of the IEEE 2002 Symposia on Human Centric Computing Languages and Environments (HCC'02), p.226, September 03-06, 2002
• 7: Gilmore, D.J., Models of debugging. Acta Psychologica, (78), 1992, 151--173.
• 8: T. R. G. Green, Cognitive dimensions of notations, Proceedings of the fifth conference of the British Computer Society, Human-Computer Interaction Specialist Group on People and computers V, p.443-460, February 1990, Univ. of Nottingham
• 9: Green, T.R.G. and Petre, M., Usability analysis of visual programming environments: A 'cognitive dimensions' framework. Journal of Visual Languages and Computing, 7, 1996, 131--174.
• 10: Hugh Beyer , Karen Holtzblatt, Contextual design: defining customer-centered systems, Morgan Kaufmann Publishers Inc., San Francisco, CA, 1998
• 11: Colleen Kehoe , John Stasko , Ashley Taylor, Rethinking the evaluation of algorithm animations as learning aids: an observational study, International Journal of Human-Computer Studies, v.54 n.2, p.265-284, Feb. 2001 [doi>10.1006/ijhc.2000.0409]
• 12: Ko, A.J. and Myers, B.A. Development and evaluation of a model of programming errors, IEEE Symposia on Human-Centric Computing Languages and Environments, 2003, Auckland, New Zealand, 7--14.
• 13: Raimondas Lencevicius , Urs Hölzle , Ambuj K. Singh, Dynamic Query-Based Debugging of Object-Oriented Programs, Automated Software Engineering, v.10 n.1, p.39-74, January 2003 [doi>10.1023/A:1021816917888]
• 14: Henry Lieberman, Introduction, Communications of the ACM, v.40 n.4, p.26-29, April 1997 [doi>10.1145/248448.248455]
• 15: Anneliese von Mayrhauser , A. Marie Vans, Program understanding behavior during debugging of large scale software, Papers presented at the seventh workshop on Empirical studies of programmers, p.157-179, October 1997, Alexandria, Virginia, United States [doi>10.1145/266399.266414]
• 16: James Reichwein , Gregg Rothermel , Margaret Burnett, Slicing spreadsheets: an integrated methodology for spreadsheet testing and debugging, Proceedings of the 2nd conference on Domain-specific languages, p.25-38, October 03-06, 1999, Austin, Texas, United States
• 17: Romero, P., et al., A survey of external representations employed in object-oriented programming environments. Journal of Visual Languages and Computing, 14, 2003, 387--419.
• 18: Rothermel, G., Harrold, M.J., and Dedhia, J., Regression test selection for c++ software. Software Testing, Verification & Reliability, 10(2), 2000, 77--109.
• 19: Tassey, G., The economic impacts of inadequate infrastructure for software testing. National Institute of Standards and Technology, RTI Project Number 7007.011, 2002.
• 20: Tip, F., A survey of programming slicing techniques. Journal of Programming Languages, 3, 1995, 121--189.
• 21: Andreas Zeller, Isolating cause-effect chains from computer programs, Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering, November 18-22, 2002, Charleston, South Carolina, USA [doi>10.1145/587051.587053]
• 22: Xiangyu Zhang , Rajiv Gupta , Youtao Zhang, Precise dynamic slicing algorithms, Proceedings of the 25th International Conference on Software Engineering, May 03-10, 2003, Portland, Oregon

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.5 Testing and Debugging
          Subjects: Debugging aids

Keywords:
Alice, debugging, program slicing