DOC PREVIEW
Berkeley COMPSCI 160 - Hi-fidelity Prototyping

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

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 9 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 9 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 9 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 9 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Chau Le cs160-brDustin Preisler cs160-bgAli Memarsadeghi cs160-bfHi-fidelity Prototyping – Group 8E-Drink – Why It Solves The ProblemTasks:Task 1: Order a single Corona and confirm the orderTask 2: Modify a Current Order - add two Guinesses to itThird Task: Place a special order for a "dry" Martini with "olives" and "shaken"Luan Nguyen cs160-ayChau Le cs160-brDustin Preisler cs160-bgAli Memarsadeghi cs160-bfHi-fidelity Prototyping – Group 8E-Drink – Why It Solves The ProblemE-drink is a kiosk-based drink ordering system created to eliminate the annoying task of waiting in line to order drinks at a bar. The idea was sparked by the observation that bar patrons spend a significant amount of their time at a bar simply waiting for drinks. Aside from wasting time, waiting in line detracts from the overall bar experience in that it can be stressful, frustrating, and intimidating. One of the primary goals for the e-drink system is to make ordering drinks a less daunting task by making it as easy as possible. By having kiosks at every table in a bar, those sitting at tables can remain seated for the duration of their stay at the bar should they desire to do so. Instead of being a fifteen minute fight for survival, ordering drinks becomes a 30 second interaction with the user-friendly kiosk. When a bar patron wants more drinks, he or she simply submits the order through the kiosk and has the drink brought directly to the table by a waiter who then collects payment or adds to a tab. Our experiment was designed to test whether or not the interface we have designed is as easy to use as we hoped. We had three different regular bar-goers complete the common bar functions using our interface.Our mission statement reflects the team’s considerations throughout the design process:“Look, I’m drunk and I want more drinks! Just give me drinks!”We have this mission statement to constantly remind us of who the users of our system will be. A person having drinks at a bar does not want to do any complex analytical thinking. He simply wants drinks, and he wants them quick and easy. If it is not easy to use the system, then it’s just not going to be used. From making large and easy to see buttons, to providing only the essential information to the user, we always remember to keep it simple stupid!Tasks:Here are the tasks we gave the users:1. You are sitting at a table in a bar which has a kiosk from which you can order drinks. You, being a beer fan, want a cool Corona to sooth your taste buds. Use this kiosk to order a single Corona to be delivered to your table.2. Your two buddies just joined you at your table. You tell them that you have ordered yourself a Corona and they tell you that they also want drinks. Modify your drink order to add two Guinesses for your friends.It is approaching the end of the night. You have had several drinks and are now ready foryour special end of the night drink. Place an order for a dry Martini with olives that’s shaken.Prototype Redesign:Our design contains five possible screens. The first is the main screen where there are four possible selections of drink types, a restart button, and sometimes a “My Order” button (fig 1). The second screen is a full navigable menu where specific types ofdrinks are listed and the user searches through to select a drink (fig 2). The third screen isthe “My Order” screen which contains the information about your current order (fig 3). The fourth screen is a popup screen after you have selected a drink type, it allows you to select the number of drinks of that type you would like and to specify any special conditions you will need on the drink (fig 4, 5). The last screen is the order confirmation screen where it confirms that your order has been received, this screen allows you to cancel your whole order or modify it (fig 6).In the redesign we needed to implement these main things. The option screen sequencing, wait line generality, confirmation of order, and easy drink canceling. First with option screen sequencing we included only options which should be available at thatbranch in the order. So for instance the ‘my order’ option will not appear on the main menu screen before an order has been placed. Second we decided on a common wait lineidentifier the wait line instead of wait time, because it allows for better user patience. If auser sees that he/she is number 5 in line, that could be anywhere from 5-15 minutes. If we predicted a time and it was inaccurate then the user would be frustrated. Third we made sure that the confirmation of an order is very explicit and that the user knows the order went through. We made the confirmation convincing and it should now blink the wait line status so they realize it is being update, this is hard technically however, so it may not be completely implemented before the submission time. Fourth we plan to include easy canceling of specific drinks in the order on the ‘my order’ page but it was infeasible at this point due to space restriction. Currently you must click on a drink in your “My Order” page in order to cancel that specific drink. We will address this as soonas possible. It would simplify the canceling process and get rid of an extra screen. fig 1 fig 2 fig 3fig 3 fig 4 fig 6Scenarios:Note: due to the inability to get screen dumps of our hi-fi during the writing of this section, these are screen dumps of the lo-fi commented to explain how they are different in the hi-fi. Attached to the end of this document should be screen dumps of the hi-fi.Task 1: Order a single Corona and confirm the order Step 1: From the “Main” menu users would hit the “Beer” button.Note: At this point you would NOT have the My Order button as there is no My Order yet.Step 2: At the “Beer” menu, hit the “Corona” button.Note: Here still there is no My Order button.Step 3: Set the “Quantity” to one for one Corona. Once the quantity is set, hit the “Add to Order” button.Step 4: Press the “Finish” button to send the order to the waiter / bartender.Note: the More Drink button actually says More DrinksStep 5: The drink would be delivered in 12 minutes.Note: we use wait line now instead of wait time, so it would tell you what order # you are in the line.Task 2: Modify a Current Order - add two Guinesses to itStep 1: From the “Finish” menu, hit “Modify Order” to change the order that is made.Note: wait time should be


View Full Document

Berkeley COMPSCI 160 - Hi-fidelity Prototyping

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 Hi-fidelity Prototyping
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 Hi-fidelity Prototyping 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 Hi-fidelity Prototyping 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?