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

By Amy J. Ko, Brad A. Myers. International Conference on Human Factors in Computing Systems, 2004

444 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/01dbd4ceafcd428bbb7b15db10d53952d0ad8ae7

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

In Information Systems

In Software

Citations in the corpus

Six Learning Barriers in End-User Programming Systems (2004, methodology): “We have made progress with the Whyline [7], but significant challenges remain.”
Making mashups with marmite: towards end-user programming for the web (2007, background): “Automatic generation of theories for programming bugs is currently an open problem in software engineering [ 17 ].”
Methods and tools for exploring novice compilation behaviour (2006, background): “The work of Myers and Ko regarding interfaces for programming environments—novice or expert—is encouraging work that is driven, first and foremost, by user behaviour and needs[16, 17, 18].”
Why and why not explanations improve the intelligibility of context-aware intelligent systems (2009, unknown): “The Whyline [ 16 ] and Crystal application framework 20] provide explanations that answer Why and Why Not intelligibility questions for novice programmers and desktop users respectively, but the effectiveness of these explanation types were not compared.”
Emergent, crowd-scale programming practice in the IDE (2014, background): “Other work has focused on helping users debug their programs through program analysis or crowdsourced aggregation of user activities [18, 1, 14, 24, 28].”
Trends and Trajectories for Explainable, Accountable and Intelligible Systems: An HCI Research Agenda (2018, methodology): “Some research focused on consumer-oriented applications, such as Recommender Systems [33, 81] and Adaptive User Interfaces of applications and for Software Engineering [95, 96, 135].”
An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks (2006, unknown): “In Section 7, we conclude with implications of our results on the design of software development environments.”
In-IDE Code Generation from Natural Language: Promise and Challenges (2021, background): “Ko and Myers [53, 54] provides a debugging interface for asking questions about program behavior.”
Measuring Program Comprehension: A Large-Scale Field Study with Professionals (2018, methodology): “Prior research proposed several tools to improve IDEs according to developers’ typical behavior [10], [27].”
Asking and Answering Questions during a Programming Change Task (2008, methodology): “An interrogative debugging tool by Ko and Myers called Whyline aims to help programmers both ask and answer these kinds of questions using a program slicing technique [ 32 ].”