Chau Le cs160-brDustin Preisler cs160-bgFinal Interface Write UpE-DrinkGroup 8ProblemTasksInitial Sketches to Lo-FiLo-Fi to Hi-FiOverviewUnimplementedTools UsedApendix 1 Screen Shots(SS1) Welcome ScreenLuan Nguyen cs160-ayChau Le cs160-brDustin Preisler cs160-bgAli Memarsadeghi cs160-bfFinal Interface Write UpE-DrinkGroup 8ProblemThe problem we are trying to address is the annoying task of waiting in line to order drinks at a bar. Bar patrons spend a significant amount of their time at a bar simply waiting for drinks or trying to attract the bartender’s attention to place an order. Aside from wasting time, waiting in line detracts from the overall bar experience in that it can be stressful, frustrating, and intimidating.Solution OverviewE-Drink is our solution to this problem. It is a kiosk based electronic ordering system. One of the primary goals for the E-Drink system is to make ordering drinks a less daunting task by making it as easy and accessible 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, or you can swipe in at any kiosk to make, check, change or cancel your order. 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 either have the drink brought directly to the table by a waiter or pick it up at a pick up area when his number is called.TasksHere 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.We chose Task 1, the easy task, because it exercises the most basic functionality of our system. Ordering one non-custom drink. It takes the user through most of the main screens to get a feel for the system.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. Since they want Guiness, you decide you’d like one too. Modify your drink order by first canceling your Corona, and then adding three Guinesses for you and your friends.Luan Nguyen cs160-ayChau Le cs160-brDustin Preisler cs160-bgAli Memarsadeghi cs160-bfWe chose Task 2, the medium task, because it makes use of the most used area of our system, the “My Order” screen. This area is the used for checking and updating your order. Task 2 also exercises a simple cancel single item, and an order modification.3. It is approaching the end of the night. You have had several drinks and are now ready for your special end of the night drink. Place a custom order for a dry Martini with, shaken, with an olive.We chose Task 3, the difficult task, because it is the most advanced. Placing a custom order follows the normal ordering route, but requires you to choose specific options for your drink. Testing the ease of choosing these options was themain point of Task3.Design EvolutionInitial SketchesThe basic structural design for the electronic waiter was originally composed of three components.1. A full-screen navigable menu which a users searches through to select drinks.2. A “My Order” dialog that shows the user the elements of his order.3. An order confirmation page.In our initial design, we wanted the UI to fulfill the following basic requirements:- Throughout navigation the user should always be able to access the “My Order” dialog to see what drinks, if any, he has in his order.- The “My Order” should be smaller than the other dialogs. It should appear as though it “pops up” above the menu.- The confirmation page should show confirm the user’s order, actually show him what he ordered, show his place in line, and allow him to modify his order up until it is physically made.All implementation was done with the basic goals outlined above in mind, but a lot of thedetails of each screen had to be modified from the initial sketches to this final version. The following is a list of significant changes:Initial Sketches to Lo-FiThere were just a few changes we implemented from our sketches to our Lo-Fi prototype. Most came either as a realization that we left some functionality out, or because as it was coded, certain things seemed possible and others not plausible.- We added a restart button to the Main Menu screen because we realized we hadn’t accounted for a user leaving in the middle of his orderLuan Nguyen cs160-ayChau Le cs160-brDustin Preisler cs160-bgAli Memarsadeghi cs160-bf- We included wait time and wait line, thinking that the user might want an estimate of the time before receiving his drink- We resized the bottom buttons for each screenLo-Fi to Hi-FiAfter the Lo-Fi testing took place, we realized there were a couple of signifigant changes, which needed to be made. Users were frustrated by four main things. First, they did not like having both wait line and wait time present. Second, they thought it wasnot easy enough to cancel a single item. Third, they didn’t like having buttons present if the option was not real for that stage in the task. Lastly, they were concerned about mobility. They felt they could not move around the bar because they needed to wait for their order. Users also commented that we should experiment with some colors in E-Drink.- We decided on wait line throughout the system. This would allow users to see their place in line, and would not confuse them with extra variables- We implemented a cancel button for each item in the my order screen- We changed certain buttons to have them either appear or not appear depending on your stage in the process- We did not change anything to allow for mobility but we discussed possible options for the final interface- We played with the colors, but realized afterwards that a more subdued color scheme was in orderHi-Fi to Final InterfaceHi-Fi testing and the Heuristic Evaluation gave us good feedback on some of the last changes we needed to implement. The users were confused by the Previous and Nextbuttons in the actual drink menu screen. These were for paging through the menu, but theusers thought they might be like the Web Browser version, which would take them to the previous screen in the Application.
View Full Document
Unlocking...