...
| Panel |
|---|
Hello and thank you for help us with our project, OpenMenu! This is ______, _ _____, and _ ____. Picture this: You are going out to a restaurant on a Friday night with a couple friends. When you are seated, you notice that instead of menus, your waiter has grabbed tablets instead. Your waiter informs you that the restaurant is trying out a new electronic ordering system. The purpose of this new ordering system is to make ordering and waiting at restaurants faster and more efficient and to entertain customers while waiting for their orders to arrive. To help us test the system, we're going to ask you to do some scenario tasks. |
...
| Panel |
|---|
User and Task AnalysisWhat We Learned When we thought about what we wanted to get out of 6.813, we wanted to learn more about making technologies easier to use for populations that normally don't interact with technology. WIth this in mind, we decided to make a menu system because menus are used by both technologically advanced users and users who don't even own a computer. We learned that interviewing people who would be typical users of our product are extremely beneficial in learning about that the user, the user's technical abilities, and the user's desires in our product. Performing our task analysis was useful throughout the production of OpenMenu because it gave us goals we wanted to accomplish that we can always keep in mind. What We Would Have Done Differently We believe that this process went extremely well, and we wouldn't have changed much. We felt as through the user groups we chose were ideal for our product and the tasks we choose were valid for OpenMenu. |
| Panel |
|---|
DesignsWhat We Learned One of the first things we had to do was write an example scenario which helped us conceptualize how our product would be used in a hypothetical situation. We incorporated all of the tasks that we created during our Task Analysis to confirm that our tasks were still valid. After creating our scenario, each member separately came up with their own design which resulted in three completely different designs for OpenMenu. We choose to do so separately because we didn't want own ideas to conflict with each other before we got all of our ideas on paper. From these three designs, we choose what seemed like good ideas to test for paper prototyping and which ones we wanted to scrap off the board (to save time in implementation and testing). |
| Panel |
DesignsOur designs turned out pretty well. The design that we ended up choosing, the tab-based design, turned out really well and we got a lot of positive feedback on the tab system. Our end implementation actually turned out to be pretty different to our original design. Although it was still tab-based, the tabs were completely different than what we had originally designed. One thing that surprised us was how useful the designs turned out to be when doing our prototyping, especially our paper prototyping, since we had something to base our prototype off of instead of trying to create it in our heads as we made our prototypes. |
| Panel |
|---|
Paper & Computer ProtypingComing Soon. |
...