Finding causes of program output with the Java Whyline

Finding causes of program output with the Java Whyline
复制标题

使用 Java Whyline 查找程序输出的原因

DOI:
--
复制
发表时间:
2009
期刊:
International Conference on Human Factors in Computing Systems
影响因子:
--
通讯作者:
B. Myers
B. Myers
中科院分区:
--
文献类型:
--
作者:
Amy J. Ko;B. Myers

文献摘要

被引文献

相似文献

调试和诊断工具是一些最重要的软件开发工具,但大多数期望开发人员选择正确的代码进行检查。不幸的是,这很少发生。描述了一种称为Whyline的新工具,它通过允许开发人员选择有关程序输出的问题来避免这种猜测。然后,该工具可以帮助开发人员从输出到其原因向后工作。支持Java程序的原型在一个实验中进行了评估,其中参与者使用Whyline或断点调试器研究了开源项目中的两个真正的错误报告。 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.