Finding causes of program output with the java whyline

Conference on Human Factors in Computing Systems - Proceedings

Volumn , Issue , 2009, Pages 1569-1578

  Ko, Andrew ^a   Myers, Brad A ^b  

^a UNIVERSITY OF WASHINGTON   (United States)

^b Carnegie Mellon University ^*  (United States)

Author keywords

Debugging; Instrumentation; Slicing; Whyline

Indexed keywords

CONTROL GROUPS; DIAGNOSTIC TOOLS; INSTRUMENTATION; JAVA PROGRAM; OPEN SOURCE PROJECTS; SLICING; SOFTWARE DEVELOPMENT TOOLS; WHYLINE;

COMPUTER DEBUGGING; COMPUTER SOFTWARE; HUMAN ENGINEERING; JAVA PROGRAMMING LANGUAGE; TOOLS;

PROGRAM DEBUGGING;

EID: 84892468995     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1518701.1518942     Document Type: Conference Paper

References (22)

1. Abraham R, and Erwig M. 2005. Goal-directed debugging of spreadsheets. IEEE Visual Languages and Human-Centric Computing, 37-44.
2. Baowen X., Ju Q., Xiaofang Z., Zhongqiang W., & Lin C. 2005. A brief survey of program slicing, IEEE Software Engr. Notes, 30(2), 1-36.
3. Bothell D. 2004. ACT-R Environment Manual, Version 5.0, http://act-r.psy.cmu.edu/software/EnvironmentManual.pdf.
4. Chalupsky H. and Russ T.A. 2002. WhyNot: Debugging failed queries in large knowledge bases. Nat 7 Conf. on Artificial Intelligence, 870-877.
5. Clark P., Chaw SY, Barker K, Chaudhri V, Harrison P, Fan J, John B, Porter B, Spaulding A, Thompson J, & Yeh PZ 2007. Capturing and answering questions posed to a knowledge-based system, Int 7 Conf. on Knowledge Capture, 63-70.
6. Ernst M.D., Czeisler A., Griswold W.G., & Notkin D. 2000. Quickly detecting relevant program invariants. Int'l Conf on Soft. Engr. (ICSE), 449-458.
7. Gilmore D.J. 1992. Models of debugging, Acta Psychologica, 78, 151-173.
8. Ko A.J. & Myers B.A. 2004. Designing the Whyline: A debugging interface for asking questions about program failures. ACM Conf. on Human Factors in Computing Systems (CHI), 151-158.
9. Ko A.J., Myers B.A., Coblenz M. & Aung H.H. 2006. An exploratory study of how developers seek, relate, and collect relevant information during software maintenance tasks. IEEE Trans, on Soft. Engr., 32(12), 971-987.
10. Ko A.J., Myers B.A., Chau D.H. 2006. A linguistic analysis of how people describe software problems. IEEE Visual Languages and Human-Centric Computing, 127-134.
11. Ko A.J., DeLine R, & Venolia G. 2007. Information needs in collocated software development teams. Int 7 Conf. on Soft. Engr. (ICSE), 344-353.
12. Ko A.J. 2008. Asking and answering questions about the causes of software behaviors. Human-Computer Interaction Institute CMU-CS-08-122.
13. Ko A.J. & Myers B.A. 2008. Debugging reinvented: asking and answering why and why not questions about program behavior. Int 7 Conf. on Soft. Engr (ICSE)., 301-310.
14. LaToza T.D., Garlan D, Herblseb J.D. & Myers B.A. 2007. Program comprehension as fact finding. ACM Int'l Symp. on Foundations of Soft. Engr., 361-370.
15. Lewis B. 2003. Debugging backwards in time, Int Workshop on Automated Debugging, 225-235.
16. Myers B.A., Weitzman D, Ko A.J., & Chau D. H. 2006. Answering why and why not questions in user interfaces. ACM Conf. on Human Factors in Computing Systems (CHI), 397-406.
17. Robillard M.P., Coelho W & Murphy G.C. 2004. How effective developers investigate source code: An exploratory study, IEEE Trans, on Soft. Engr., 30(12), 889-903.
18. Sillito J., Murphy G.C., & De Voider K. 2006. Questions programmers ask during software evolution tasks. ACM Int'l Symp. on Foundations on Soft. Engr., 23-34.
19. Tassey G. 2002. The economic impacts of inadequate infrastructure for software testing. National Institute of Standards and Technology, RTI Project Number 7007.011.
20. Wagner E. & Lieberman H. 2003. An end-user tool for e-commerce debugging. Int 7 Conf. on Intelligent User Interfaces, 331-331.
21. Weiser M. 1982. Programmers use slices when debugging, Communications of the ACM, 25(7), 446-452.
22. Zeller A. 2002. Isolating cause-effect chains from computer programs. ACM Int 'I Svmp. on Foundations of Soft. Engr., 1-10.