Methods and systems for developing and testing speech applications

• US 20060230410A1
• Filed: 03/22/2006
• Published: 10/12/2006
• Est. Priority Date: 03/22/2005
• Status: Abandoned Application

• Current Assignee: Parus Holdings, Inc.
• Original Assignee: Parus Holdings, Inc.
• Inventors: Shirobokov, Mike, Garratt, Sean, Kurganov, Alex
• Application Number:
  US11/387,151
• Publication Number:
  US 20060230410A1
• Time in Patent Office: Days
• US Class Current: 719/311
• CPC Class Codes: H04M 2203/254 where the visual mode comprises menus
• CPC Class Codes: H04M 2203/355 Interactive dialogue design tools, features or methods
• CPC Class Codes: H04M 3/4938 comprising a voice browser which renders and interprets, e.g. VoiceXML

Abstract

A system and method for facilitating the efficient development, testing and implementation of speech applications is disclosed which separates the speech user interface from the business logic. A speech user interface description is created devoid of business logic in the form of a machine readable markup language directly executable by the runtime environment based on business requirements. At least one business logic component is created separately for the speech user interface, the at least one business logic component being accessible by the runtime environment.

Claims

1. A method for developing a speech application, comprising the following steps:

creating a speech user interface description devoid of business logic in the form of a machine readable markup language directly executable by a runtime environment based on business requirements; and

creating separately at least one business logic component for said speech user interface, said at least one business logic component being accessible by said runtime environment.

2. The method of claim 1 wherein said markup language is Web Speech Dialog Markup Language.

3. The method of claim 1 wherein said speech user interface description is created by utilizing a graphical user interface toolkit.

4. The method of claim 3 wherein said speech user interface description comprises dialogs, grammars, prompts, and transitions.

5. The method of claim 1 wherein said speech user interface description contains at least one placeholder, said placeholder corresponding to said at least one business logic component.

6. The method of claim 5 wherein said at least one placeholder triggers said runtime environment to execute said at least one business logic component during execution of said speech user interface description.

7. The method of claim 6 wherein said at least one business logic component receives at least one command from a user during execution of said at least one business logic component.

8. The method of claim 7 wherein said user command is selected from the group consisting of:

speech command, touch-tone command, keyboard command, keypad command, mouse command, touchpad command, drag-and-drop command, and any other mechanical or electronic device capable of interpreting user intent.

9. The method of claim 1 further comprising the step of separately testing said speech user interface and said at least one business logic component for errors.

10. The method of claim 9 wherein said testing is automated, said testing utilizing two or more interpreter instances communicating with one another, wherein at least one instance plays the role of a caller and at least one instance plays the role of a server.

11. A system for developing a speech application comprising:

a runtime environment;

a speech user interface description devoid of business logic in the form of a machine readable markup language directly executable by said runtime environment based on business requirements; and

at least one business logic component for said speech user interface, said at least one business logic component being accessible by said runtime environment.

12. The system of claim 11 wherein said markup language is Web Speech Dialog Markup Language.

13. The system of claim 11 further comprising a toolkit, said toolkit configured to create said speech user interface description by utilizing a graphical user interface for said runtime environment.

14. The system of claim 13 wherein said speech user interface description comprises dialogs, grammars, prompts, and transitions.

15. The system of claim 11 wherein said speech user interface description contains at least one placeholder, said placeholder corresponding to said at least one business logic component.

16. The system of claim 15 wherein said at least one placeholder is configured to trigger said runtime environment to execute said at least one business logic component during execution of said speech user interface description.

17. The system of claim 16 wherein said at least one business logic component is configured to receive at least one command from a user during execution of said at least one business logic component.

18. The system of claim 17 wherein said user command is selected from the group consisting of:

speech command, touch-tone command, keyboard command, keypad command, mouse command, touchpad command, drag-and-drop command, and any other mechanical or electronic device capable of interpreting user intent.

19. The system of claim 11 wherein said runtime environment is configured to separately test said speech user interface and said at least one business logic component for errors.

20. The system of claim 19 wherein said testing is automated, said testing comprising two or more interpreter instances communicating with one another, wherein at least one instance is configured to play the role of a caller and at least one instance is configured to play the role of a server.

21. A method for developing, testing and implementing a speech application, comprising the steps of:

utilizing a speech user interface dialog development toolkit to create a speech user interface description;

said toolkit creating said speech user interface description in the form of a machine readable markup language, wherein said markup language describes only said speech user interface and not any underlying business logic, said speech user interface description comprising dialogs, commands, prompts, and transitions;

developing said business logic separately from said speech user interface description, with the only interaction between development of said business logic and creation of said speech user interface being in the form of at least one placeholder to indicate where said business logic may be required to return information;

separately testing said speech user interface and said business logic and providing feedback, said feedback relating to said speech user interface being separate from said feedback relating to said business logic;

utilizing an interpreter to execute said markup language, said interpreter separately interacting with said business logic as required by said at least one placeholder.

22. A system for developing, testing and implementing a speech application comprising:

a computer containing storage mediums with computer code mechanisms, wherein the computer code mechanisms collectively comprise;

a speech user interface dialog development toolkit, said toolkit configured to create a machine readable markup language;

said machine readable markup language describing only said speech user interface and not any underlying business logic, said machine readable markup language comprising at least one placeholder;

at least one business logic component, said business logic component associated with said at least one placeholder of said machine readable markup language; and

an interpreter, said interpreter configured to execute said machine readable markup language, said interpreter further configured to separately interact with said business logic as required by said at least one placeholder.