Categories
Uncategorized

Decide on an interface metaphor for the interaction (reference: 12.3.1 – Interface Metaphors for information).

TASKS

  1. Research
  2. Read: chapter 12 in the text
  3. Watch: https://www.youtube.com/watch?v=OT3yYXkafy8
  4. Design
  5. Decide on an interface metaphor for the interaction (reference: 12.3.1 – Interface
    Metaphors for information).
  6. Decide on an interaction type (see 12.3.1, p. 402).
  7. Complete and included the conceptual model a couple pages down that covers everything
    in your interface.
  8. Create lo-fidelity prototype to represent the interaction using paper and pencil (black and
    white only)
  9. Photograph each stage of the prototype, numbering them clearly (the numbering system is
    up to you). Include in your submission a list of these numbers and the description/purpose
    of the relevant screen/action/etc. (This is to help you stay organized just as much as to
    help your instructor understand your process.)
  10. Explain the situation (ie, this project) to a friend/relative/classmate. Have them go through
    your paper prototype interface and talk about their experience as they’re “using” it. Try not
    to tell them what to do, only nudge them if they get stuck. Write up your thoughts,
    reactions, feelings, realizations, etc., in a one page (250-350 word, double spaced, APA
    format) paper. You’re to reflect on how you felt and reacted during their “test.”
  11. Create and submit a PDF that includes the interface metaphor description, interaction type
    description, the completed conceptual model, the images and descriptions of the
    prototype, and the narrative of your reaction to your tester’s experience. The PDF should
    be titled as: 401-Project3-YourLastname.pdf
    PERSONA
    Rick, late 60s, widower with one child and two grandchildren.
    Rick plays a very active role in the life of his grandchildren, but particularly in that of his grandson,
    Morty, often acting as his guardian while Morty’s parents are both working. Rick wanted to treat Morty
    today so he took him out of school for lunch.
    Though they have time for lunch, Rick is a busy person, and also needs to run a few errands and do
    some work back in his lab garage. The reason he is interested in the newly opened Burger Express is
    in hopes of running into its owner, whom Rick has heard much about. Though Morty doesn’t like
    hamburgers (and Rick knows this), he is hopefully they will find menu items everyone enjoys.
    Rick has a low tolerance for ambiguity and is in a hurry. He uses technology every day—-
    including being familiar with the hardware being utilized by Burger Express-—and can be critical
    of poorly designed technology and interfaces.
    THE SCENARIO
    Rick is a first-time customer to Burger Express. He has brought his son Morty, 14, to lunch. The
    hostess seats them in a booth and turns the tablet toward them. She asks if they have been to Burger
    Express before and if they need help with the tablet. Rick uses similar technology daily and Morty is
    pretty good, himself. He tells the hostess that they will be fine and skips the server’s instructions. On
    the screen it says to slide a credit card to begin. Rick assumes this is like a gas station, placing a hold
    on an account to prevent customers skipping payment later.
    Once activated, the system displays a list of available drinks. Rick selects a Diet Coke and then
    changes his mind and orders water. Morty wants milk.
    Rick decides on a hamburger with lettuce, tomato, mayo, and pickles and selects french fries for his
    side and a Szechwan dipping sauce. He orders Morty a personal pepperoni pizza and a half-dozen
    wings with lemon and pepper flavoring.
    The food arrives quickly and is very tasty. Rick goes back to the tablet, selects to pay, and the
    system offers 15%, 18%, 20%, or ‘other’ as gratuity choices. He pays with the credit card he scanned
    when sitting down and enters his email to have the receipt emailed to him. He signs up for coupons,
    sent weekly.

CONCEPTUAL MODEL
Note that this conceptual model is incomplete and possibly even wrong in spots! It’s your job to
complete and/or fix it.
Objects Attributes Operations
Customer
Order
Current credit card, table location, list of selected
menu items
Send ot kitchen, pay bill, request
refill
Menu
Item
Food type (ex: appetizer, hamber, pizza, drinks,
dessert), title, description, price
Add item to order, remove from
order, customize item
Service
Request
Request type (refill, change in order, technical
support)
Request service, cancel service
request

Leave a Reply

Your email address will not be published. Required fields are marked *