Online Version - Last Updated - 20 Jan 2012 |
 |
| Home |
| |
| Procedures and Resources for Authors |
|
| Information and Resources for Volume Editors |
| |
| Orders and Subscriptions |
| |
| Published Articles |
|
| Upcoming Volumes |
| |
| Contact Us |
| |
| Useful External Links |
| |
| CRPIT Site Search |
How (Not) To Help People Test Drive Code
Marshall, S., Biddle, R. and Tempero, E.
This paper discusses the results of usability testing on the interface of Dyno. Dyno is a tool designed to support code reuse by helping software developers understand what a specified piece of code does. The tool does this by allowing a programmer to undertake a process we call test driving. This paper looks at the deficiencies uncovered in the initial interface, and the implications this has for a tool aimed at helping software developers better understand code fragments so as to be able to reuse them.
Cite as: Marshall, S., Biddle, R. and Tempero, E. (2002). How (Not) To Help People Test Drive Code. In Proc. Third Australasian User Interface Conference (AUIC2002), Melbourne, Australia. CRPIT, 7. Grundy, J. and Calder, P., Eds. ACS. 39-42.
(from crpit.com)
(local if available)
