2010
DOI: 10.1145/1824760.1824761
|View full text |Cite
|
Sign up to set email alerts
|

Extracting and answering why and why not questions about Java program output

Abstract: When software developers want to understand the reason for a program's behavior, they must translate their questions about the behavior into a series of questions about code, speculating about the causes in the process. The Whyline is a new kind of debugging tool that avoids such speculation by instead enabling developers to select a question about program output from a set of "why did and why didn't" questions extracted from the program's code and execution. The tool then finds one or more possible explanatio… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
96
0

Year Published

2010
2010
2023
2023

Publication Types

Select...
4
4
2

Relationship

2
8

Authors

Journals

citations
Cited by 73 publications
(96 citation statements)
references
References 37 publications
(44 reference statements)
0
96
0
Order By: Relevance
“…WhyLine [10] is a modern interactive debugging tool where the user can ask questions during debugging about why a certain change happened. By recording the execution trace, it is possible to solve complex debugging problems by navigating through history.…”
Section: Related Workmentioning
confidence: 99%
“…WhyLine [10] is a modern interactive debugging tool where the user can ask questions during debugging about why a certain change happened. By recording the execution trace, it is possible to solve complex debugging problems by navigating through history.…”
Section: Related Workmentioning
confidence: 99%
“…Most debuggers operate on a very low level and often require much time and effort by the user to deliver meaningful information. The approach taken by the WHYLINE system [19] improves this situation by inverting the direction of debugging. This system allows users to ask "Why...?"…”
Section: Related Workmentioning
confidence: 99%
“…The Natural Programming project [1] at Carnegie Mellon University (CMU) has repeatedly demonstrated that many of the these techniques can be adapted to improve the effectiveness of the tools and languages used by developers. For example, we have applied them to the user interfaces of integrated development environments (IDEs) [2,3], debuggers [4], programming languages [5], and APIs (application programming interfaces) [6][7][8][9][10]. Many HCI techniques are applicable, and we have used contextual inquiry, heuristic evaluation, cognitive walkthrough, ethnography, and controlled lab studies.…”
Section: Introductionmentioning
confidence: 99%