Computing Reviews
Today's Issue Hot Topics Search Browse Recommended My Account Log In
Review Help
Search
Capturing user tests in a multimodal, multidevice informal prototyping tool
Sinha A., Landay J.  Multimodal interfaces (Proceedings of the 5th international conference, Vancouver, British Columbia, Canada, Nov 5-7, 2003)117-124.2003.Type:Proceedings
Date Reviewed: Mar 12 2004

This paper describes an interesting tool, developed by the authors, that helps designers create an on-screen prototype of a device. The authors use a bread toaster to illustrate the kind of design activity they support. Basically, their approach consists of providing a storyboard of the various actions a design may take, providing an easy way to specify the sequence of actions (put in the slices of bread, then pull down the toaster bar), and graphically displaying the output of each action on one or more output devices. These output devices might include a personal computer (PC) screen, a personal digital assistant (PDA) device, or a speaker (to which text-to-speech output may be directed).

The emphasis of the paper is on the flexibility with which the input to the model can be provided (via mouse click, keyboard, or voice input). The input may be a single input from one or more of these devices (a mouse click, a character from the keyboard, or a word input via a microphone), or an AND combination of inputs entered within one second of each other (a keyboard input of “d” and voice input of “down”). The tool contains many other capabilities, which I don’t have the space to mention.

The tool seems to be thought out and implemented fairly thoroughly. In fact, some of its capabilities may not be initially used by novice users. It appears to me that all of this multimodal, multidevice input and output may not be necessary to design the user interface of a toaster. It would be interesting if the authors had described other applications where these capabilities may indeed be justified. There may be many: the dashboard controls in a car, a complex audio/video set, and so on. The authors should have tried out their software on designers of these types of equipment to better understand their requirements. The software seems like a solution looking for a problem. Perhaps this is simply the technological exploration phase of a project, before a more disciplined software engineering approach is applied to understanding the requirements, which in turn may be met with available technology.

Reviewer:  Birol Aygün Review #: CR129239 (0409-1102)
Bookmark and Share
 
Prototyping (H.5.2 ... )
 
 
Interaction Styles (H.5.2 ... )
 
 
User Interfaces (D.2.2 ... )
 
 
Design Tools and Techniques (D.2.2 )
 
Would you recommend this review?
yes
no
Other reviews under "Prototyping": Date
Design as exploration: creating interface alternatives through parallel authoring and runtime tuning
Hartmann B., Yu L., Allison A., Yang Y., Klemmer S.  User interface software and technology (Proceedings of the 21st Annual ACM Symposium on User Interface Software and Technology, Monterey, CA, Oct 19-22, 2008)91-100, 2008. Type: Proceedings
Dec 4 2008
Using task context to achieve effective information delivery
Gomez-Perez J., Grobelnik M., Ruiz C., Tilly M., Warren P.  CIAO 2009 (Proceedings of the 1st Workshop on Context, Information and Ontologies, Heraklion, Greece, Jun 1, 2009)1-6, 2009. Type: Proceedings
Sep 24 2009

E-Mail This Printer-Friendly
Send Your Comments
Contact Us
Reproduction in whole or in part without permission is prohibited.   Copyright 1999-2024 ThinkLoud®
Terms of Use
| Privacy Policy