We describe the design and implementation of the dialogue management module in a voice operated car-driver information system. The literature on designing 'good' user interfaces involving natural language dialogue in general and speech in particular is abundant with useful guidelines for actual development. We have tried to summarize these guidelines in 7 'meta-guidelines', or commandments. Even though state-of-the-art Speech Recognition modules perform well, speech recognition errors cannot be precluded. For the current application, the fact that the car is an acoustically hostile environment is an extra complication. This means that special attention should be paid to effective methods to compensate for speech recognition errors. Moreover, this should be done in a way which is not disturbing for the driver. In this paper, we show how these constraints influence the design and subsequent implementation of the Dialogue Manager module, and how the additional requirements fit in with the 7 commandments.
[1]
Ben Shneiderman,et al.
Designing the user interface (2nd ed.): strategies for effective human-computer interaction
,
1992
.
[2]
R. Leiser.
Driver-vehicle interface: dialogue design for voice input
,
1993
.
[3]
Kathryn M. Dobroth,et al.
Automating Services with Speech Recognition over the Public Switched Telephone Network: Human Factors Considerations
,
1991,
IEEE J. Sel. Areas Commun..
[4]
H. Grice.
Logic and conversation
,
1975
.
[5]
Jonathan Grudin,et al.
The case against user interface consistency
,
1989,
CACM.
[6]
Wayne H. Ward.
Extracting information in spontaneous speech
,
1994,
ICSLP.
[7]
GrudinJonathan.
The case against user interface consistency
,
1989
.
[8]
W. Chafe.
Givenness, contrastiveness, definiteness, subjects, topics, and point of view
,
1976
.
[9]
Dan R. Olsen,et al.
Developing user interfaces
,
1998
.