DOC PREVIEW
Berkeley COMPSCI 160 - WIRM: Waiter and Interactive Restaurant Menu

This preview shows page 1-2-3-4 out of 11 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

WIRM: Waiter and Interactive Restaurant MenuHi Fi PrototypeGroup 2Ian WangKristen WongJosephine ChoiOctober 25, 2001Problem and Solution OverviewTasksInterface Design RevisionsScenario #1: Ordering a lemonadeScenario #2: Ordering a cheeseburger without pickles, mayonnaise, and cheeseProject OverviewToolsHowever, our group also encountered various problems while working with Microsoft Front Page. It was difficult to lay out submit buttons on the same line that went to different pages. We also had a problem with submit buttons and having to create text links next to them. We needed to create the form first and then add the text link, which was a hassle. Also, the problem of displaying pictures next to menu items is difficult as a result of the limited memory on the Clio. So the image display is quite slow if we put any graphics on the prototype. For the future, using Microsoft Front Page also might not be sufficient because some of WIRM’s features require dynamic behavior, such as the search feature and the bill summary. For example, the bill summary needs to gradually update as the user adds a new item to the order, a task which the current prototype of WIRM does not cover. However, we are planning to use CGI scripting and Perl to accommodate these features.Overview of UI implementedUnimplemented pages/Wizard of Oz techniquesPrototype Screen DumpsWIRM: Waiter and Interactive Restaurant MenuHi Fi PrototypeGroup 2Ian WangKristen WongJason KuoJosephine Choihttp://ratbert.bmrc.berkeley.edu/courseware/cs160/fall01/Projects/Group2/assign4.docPrototype location: http://inst.eecs.berkeley.edu/~cs160-aj/READMEOctober 25, 2001CS 160Professor CannyProblem and Solution OverviewFor a majority of people who enjoy going to restaurants and expecting a satisfyingdining experience, an ideal restaurant setting would include an accessible wait staff and a diverse menu capable of accommodating individual tastes. However, this optimistic scenario is rarely the case. Busy and unavailable waiters, poorly organized menus, and lack of sufficient information on menu items are familiar and often frustrating situations that many diners have experienced. To ease the dissatisfaction associated with poor restaurant dining, our group has developed WIRM, which stands for Waiter and Interactive Restaurant Menu.WIRM essentially is an interactive menu browser that will supplement existing menus and streamline customer service by replacing most of the waiter’s functions. Alongside pictures and detailed descriptions of each menu item, WIRM also is designed to handle various practical features that will aid the diner directly at the table. Some of these include the ability to retrieve ratings and comments on dishes from previous diners, the convenience to place and cancel orders at the diner’s own leisure, and the option to call a live waiter at any time.TasksTo test our interface, we asked users to perform three tasks of varying difficulty. They were presented with the following tasks and scenarios:1) You’ve just arrived at the restaurant, and boy, are you thirsty. Your thirst must be quenched immediately, and with a nice glass of ice-cold lemonade. Using WIRM,order a glass of lemonade. (Easy)2) It’s a burger kind of day. However, you have a rare combination of allergies to dairy products and cucumbers. At the same time, you have a strange inclination to order “cheeseburgers” even though you can’t consume cheese. Order a cheeseburger with no pickles, no mayonnaise, and no cheese. Also, you absolutely love bacon; so add bacon to your concoction. (Medium)3) You have forgotten about your companion at the dinner table. She also has very particular tastes – she is a vegetarian. You also want to make sure that she gets the best dish possible at this restaurant because you want to impress her with yourelegant taste buds. Search the menu for all vegetarian items without actually scanning through the entire menu. Next, sort the items returned by customer rating. This way, you can make sure you select the best item for your buddy. Order the item with the highest customer rating. Then pay your bill. (Difficult)Interface Design RevisionsOur Hi-fi prototype reflects the changes based on the results of our Lo-fi prototype testing. The most prominent change was the removal of the “current order” column on the left side of the interface. (Fig. 1a) Users found the “current order” column, similar to a “shopping cart”, too confusing because they didn’t know whether items shown in the column were sent to kitchen ornot.In removing the left column, we moved the “Search” box into a more prominent position in the upper left corner. (Fig. 1b) The main reason for this is because one of the users did not notice the “search” option in its previous location and the “Search” box serves to provide symmetry with the “Call Waiter” button in the upper right corner.The “Order” button was renamed “Add to Order …” during a task requiring users to specify options with their food order. (Fig. 1c) Test users hesitated to press the button to continue the task since they assumed that pressing the button wouldsend their choice directly to the kitchen. The ellipses signal to the user that there are more tasksremaining before their order is processed.A feature that users found counterintuitive was specifying what they wanted with their hamburger. The users actually preferred specifying what they didn’t want, so the interface was changed accordingly. (Fig. 2a)During user testing, we noted that users were confused after completing a task since they had no feedback letting them know that the task was completed. Therefore, “confirmation” features and feedback were included in our Hi-fi prototype. (Fig. 3a, 4a, and 4b)Figure 3: Order Confirmation Figure 4: Order SummaryFigure 2: Options PageFigure 1: Prototype LayoutScenario #1: Ordering a lemonadeStep 1: Click on "Drinks" for lemonadeStep 2: Confirm the orderStep 3: Click "Add to Order..." for lemonadeStep 4: Send to kitchen or continue orderingScenario #2: Ordering a cheeseburger without pickles, mayonnaise, and cheeseFigure 1: Click on the “Entrees” tab to see Figure 1: Click on the mayonnaise, pickles, andthe various categories of entrees available. cheese checkboxes to remove them from the order. Click on "Add to Order." Figure 2: Click on “Burgers.” Figure 3: Confirm the order.Figure 4: Click the “Add


View Full Document

Berkeley COMPSCI 160 - WIRM: Waiter and Interactive Restaurant Menu

Documents in this Course
E-LEAGUE

E-LEAGUE

15 pages

iCurator

iCurator

10 pages

Project

Project

14 pages

E-Drink

E-Drink

10 pages

Load more
Download WIRM: Waiter and Interactive Restaurant Menu
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view WIRM: Waiter and Interactive Restaurant Menu and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view WIRM: Waiter and Interactive Restaurant Menu 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?