Review of health information technology usability study methodologies

A driving simulator experiment was conducted to determine the effects of entering addresses into a navigation system during driving. Participants drove on roads of varying visual demand while entering addresses. Three address entry methods were explored: word-based speech recognition, character-based speech recognition, and typing on a touch-screen keyboard. For each method, vehicle control and task measures, glance timing, and subjective ratings were examined. During driving, word-based speech recognition yielded the shortest total task time (15.3 s), followed by character-based speech recognition (41.0 s) and touch-screen keyboard (86.0 s). The standard deviation of lateral position when performing keyboard entry (0.21 m) was 60% higher than that for all other address entry methods (0.13 m). Degradation of vehicle control associated with address entry using a touch screen suggests that the use of speech recognition is favorable. Speech recognition systems with visual feedback, however, even with excellent accuracy, are not without performance consequences. Applications of this research include the design of in-vehicle navigation systems as well as other systems requiring significant driver input, such as E-mail, the Internet, and text messaging.

Address entry while driving: speech recognition versus a touch-screen keyboard

The report summarizes the human factors literature on the use of speech interfaces for tasks such as music selection, email processing, dialing, and destination entry while driving. A total of 15 papers were reviewed covering 15 experiments, with subject samples ranging from 4 to 48 (mode of 24). Studies were conducted using moderate fidelity simulators (4), on the road (5), using low fidelity simulations (5), and on a test track (2). The speech interfaces were true speech recognition systems (6), Wizard-of-Oz simulations (5), or unspecified (4). People generally drove at least as well, if not better (less lane variation, speed was steadier), when using speech interfaces than manual interfaces, but using a speech interface was often worse than just driving. Speech interfaces led to less workload than manual interfaces and reduced eyes-off-the-road times, all pro-safety findings. Task completion time was less with speech interfaces, but not always (as in the case of manual phone dialing). Missing from the literature were firm conclusions about how the speech/manual recommendation varies with driving workload, recognizer accuracy, and driver age.

Safety and Usability of Speech Interfaces for In-Vehicle Tasks while Driving: A Brief Literature Review

39.1 Abstract The present chapter provides an introduction to the rationale and techniques used for the rapid prototyping of the user interface (UI). It is intended primarily for those practitioners who are now known as “user interface designers” or “dialogue designers.” The reader will become familiar with the benefits to rapid prototyping, the role of prototyping in alternative development strategies, and the classes of prototyping techniques. First we review the major issues surrounding the integration of prototyping tools into the user interface design process. Both the nature of the products that can be simulated and the nature of the users applying the tools are explored. The remaining sections analyze the components of a prototyping tool. A complete prototyping system requires methods for specifying interface graphics as well as product logic. Support tools and embedded data collection test facilities can also be integrated to facilitate the testing process.

Rapid Prototyping for User Interface Design

Autonomous vehicles have the potential to fundamentally change existing transportation systems. Beyond legal concerns, these societal evolutions will critically depend on user acceptance. As an emerging mode of public transportation [7], Autonomous mobility on demand (AMoD) is of particular interest in this context. The aim of the present study is to identify the main components of acceptability (before first use) and acceptance (after first use) of AMoD, following a user experience (UX) framework. To address this goal, we conducted three workshops (N=14) involving open discussions and a ride in an experimental autonomous shuttle. Using a mixed-methods approach, we measured pre-immersion acceptability before immersing the participants in an on-demand transport scenario, and eventually measured post-immersion acceptance of AMoD. Results show that participants were reassured about safety concerns, however they perceived the AMoD experience as ineffective. Our findings highlight key factors to be taken into account when designing AMoD experiences.

/pdf/acceptability-and-acceptance-of-autonomous-mobility-on-5drb54jtgd.pdf

Acceptability and Acceptance of Autonomous Mobility on Demand: The Impact of an Immersive Experience

The Wizard of Oz technique is an efficient way to examine user interaction with computers and facilitate rapid iterative development of dialog wording and logic. The technique requires two machines linked together, one for the subject and one for the experimenter. In this implementation the experimenter (the “Wizard”), pretending to be a computer, types in complete replies to user queries or presses function keys to which common messages have been assigned (e.g., Fl=“Help is not available”). The software automatically records the dialog and its timing.This paper provides a detailed description of the first implementation of the Oz paradigm for the IBM Personal Computer. It also includes application guidelines, information which is currently missing from the literature.

Lisa Wei-Haas

Papers

The Rapid Development of User Interfaces: Experience with the Wizard of OZ Method