Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • View images of foods
  • View ingredients of foods
Filter and Compare Items

Goal: Make it easier for the user to choose their order

We will allow the user to filter the menu by type of food, such as pasta or burgers, or by ingredients, such as chicken or shrimp. This will allow the user to zone in on the kind of food they want much faster. In addition, many customers often spend a lot of time deliberating between a couple choices. Allowing the user to compare the items side-by-side is much easier and more efficient than flipping back and forth between pages of the menu.

...

  • Filter items based on type and ingredients
  • Compare between multiple items while deciding

Questions:

  • Why is the task being done?
    •  Make it easier for the user to choose their order
  • What does the user need to know or have before doing the task?
  • Where is the task being performed? On the device
  • How often is the task performed?
  • What are its time or resource constraints?
  • How is the task learned?
  • What can go wrong? (Exceptions, errors, emergencies)
View and Pay Bill

Goal: Allow the user to pay bills quickly and easily

...

Play Touchscreen Games or Browse Web

...

While waiting for food, customers are often bored with nothing to do. And since food preparation can take a long time, sometimes upwards of an hour, users can get bored or annoyed very quickly. With OpenMenu offering games and web browsing, the customers can be pass the time easily while waiting for their food.

Questions:

  • Why is the task being done?
    •  To entertain the customer while waiting for their food to arrive
  • What does the user need to know or have before doing the task?
  • Why is the task being done?
    •  
  • What does the user need to know or have before doing the task?

      ...

        • The user simply needs to be informed by the waiter/waitress that this feature exists
      • Where is the task being performed?
        • On the device
      • How often is the task performed?
        • Presumably after every customer orders (very often)
      • What are its time or resource constraints?
        • Only depends on if there are enough devices for every customer currently in the restaurant
      • How is the task learned?
        • Customer only needs to be informed that the feature exists
      • What can go wrong? (Exceptions, errors, emergencies)
        • Device could break