Objectives
- explore alternative interaction techniques
- implement interfaces on a variety of platforms
- demonstrate the ability to learn new technologies with limited classroom instruction
- Prototype #1 due Friday, Sept 21 at 3:00 pm
Requirements
You will create TWO rapid prototypes during the semester on different
platforms from what you have chosen for your semester project. For example,
Visual Basic, XHTML 1.0 transitional compliant web pages, C#, VoiceXML,
Java, etc...
BeVocal.com
Sign up for a free developers account at cafe.bevocal.com. Explore the variety of tutorials and resources to develop an Interactive Voice Application (IVR) using VoiceXML 2.1.
Spend some time interacting with 1-800-USA-RAIL for inspiration.
Provide the following:
- voice recognition for customer responses
- text to speech (TTS) for greetings and prompts are OK but using recorded audio files creates a more interesting and professional user experience.
- an attractive cover page that includes your name, proprietary business title, phone number and information to access your application
- Executive Summary - a brief summary and evaluation of the platform
for developing applications. Include highlights of any features you
think notable. What did you do to demonstrate extra effort?
- Demo Scripts - provide a series of scripts that highlights your efforts: extra credit, creativity, error checking. Your instructor will supplement these scripts with his own devious testing for features and usability. Each script should clearly indicate the prompt and recommended user response.
- Usability Testing Results - ask two or three friends to use your application while you listen. Make note of errors they encounter and what you did to improve the usability of your application. Ideally, you will do this several times as part of an iterative design process.
- up to ten pages of representative code (with excellent documentation including your name as author)
- be prepared for a brief demo during class time
Specifications
Design an interface for someone to order pizzas for take out. Avoid the temptation
to develop an ellaborate solution with price calculations or a backend
database. Use your experience with ordering pizzas to predict possible
errors and special cases. The system should allow the user to quickly
and easily order pizzas with the following features. Strive for a friendly and natural conversation.
- up to four different types of pizzas
- provide graceful error recovery and help prompts
- confirm the order and allow modification for each pizza
- do not worry about customer identification or address
Each pizza has the following options:
- Size: small, medium, large and party
- Crust: thin, thick, deep dish
- Toppings (0 or more): peperoni, sausage, peppers, onion, extra cheese and mushrooms
- Quantity: 1 - 9 of the same type of pizza
Grading Criteria
Each prototype is worth 15% of your course grade. Each grade will be
based on:
- Executive Summary (10%)
- Demo Scripts (10%)
- Usability Testing Results (10%)
- Documented code (10%)
- Usability (20%)
- Functionality (20%)
- Wow! Custom recorded audio files or some other extra effort (20%)
|
