Speech Applications Builder Configurator User Guide • May 15, 2004 • page 9 of 116
Introduction to Speech Applications Builder
Some terminology
The Speech Applications Builder (SAB)
Configurator
is a tool for building, testing, deploying and
updating voice-driven automated telephone services, such as Telephone Banking or Catalogue
Ordering.
An automated telephone service consists of one or more
applications
.
An application includes one or more interactions with the caller. These interactions are called
dialogs
.
The software that performs a dialog is called a
dialog flow
(or a
dialog model
).
The main dialog flow may contain one or more
sub-dialog flows
(and a sub-dialog flow may have
sub flows of its own).
SAB dialog flows are built using pre-defined SAB
components
, and are created as a type of flow
diagram, drawn using the SAB GUI. For a description of the SAB GUI, see page 19.
There are several types of SAB component:
•
dialogs
- which handle interactions with the caller and may include speech recognition
•
processes
- which retrieve data and perform data manipulation
•
rules
- which allow branching or decision making
•
interrupt
- which is used to provide an alternative dialog flow in response to a particular
recognition result
, such as the caller saying “
Help
” or “
Main Menu
”
For an overview of how the components are used, see page 10.
For a List of Components, see page 108.
The SAB GUI
SAB dialogs are developed using the SAB GUI. This provides:
•
Development facilities
- which allow you to create a dialog by selecting and configuring
components and connecting them together in a call flow. The GUI also provides debugging
tools.
•
Search facilities
- which allow you to search for components and prompt files, by name or
partial name.
•
A
file directory
- which provides easy access to dialog flows and prompt files.
•
A
version control mechanism
- which allows you to label and store earlier versions of a
dialog flow. Speech Applications Builder also provides a formal mechanism for migrating a
dialog from the development phase (the
tool environment
) to the deployment phase (the
production environment
) and then to the decommissioned phase (the
decommission
environment
).
•
Administrative functions
.
For a description of the SAB GUI, see page 19.