GR1 - Task analysis

User analysis

The users will be students and young adults who buy food for themselves/their household and who are interested in staying within a budget and not wasting purchased food. Many students in this age group live in dorms or apartments and share food storage space with others. Users we talked to expressed frustration at the difficulty of remembering what was in the refrigerator when it is packed with others' food. Most in this group do not cook or go through their fridge every day, making it even harder to keep track. For instance, a student remembered planning on cooking chicken after working three days straight only to realize that the chicken was expiration and bad. These situations waste food and money for those who are likely to be on some sort of budget. 

Characteristics:

  • age 17 - 35
  • likely share kitchen facilities, and may loose track of food they have there
  • may be financially tight
  • interested in limiting food waste
  • unsure how to use up/freeze certain products purchased
  • doesn’t cook every night
  • buys food once every 1-3 weeks

Needs:

  • have access to list of food in refrigerator and cabinets
  • know how much money has been spent on food in a given period of time
  • track how long food has been stored for t
  • easily access hints for preserving/cooking food to prevent waste

Personae:

  1. Matt is a freshman at MIT, lives in a dorm and shares a kitchen with 9 other students. He buys enough food for a week at a time. Matt’s hall-mates sometimes bring back leftover food from events, and he doesn’t know what to do with the extra food he bought earlier in the week.
  2. Sarah is a vegan living with three others in a small house in Summerville. She buys fresh greens, carrots and squash every week, but often forgets about how quickly greens go bad. She eats other food first, and only gets through half the bag of spinach before it gets slimy.
  3. Ben is a junior who gets $250 dollars to spend on food a month from his parents. He went way over this budget last semester and his parents got angry. Ben wants to track his spending to avoid doing that again. 

Task analysis

  1. Task: Manage food budget
    1. Subtask: set monthly food budget
      1. Precondition: Log into account (register if new user)
      2. Identify amount
    2. Subtask: view food spending
      1. Precondition: Log into account
      2. Select viewing method (progress bar, graph, etc.)
    3. Subtask: add food purchases
      1. Precondition: Log into account
      2. Enter value spent on food
  2. Task: Keep track of food supply
    1. Subtask: view food items and expiration status
      1. Precondition: Log into account
      2. Select viewing/sorting method
    2. Subtask: add food items to food supply
      1. Precondition: Log into account
      2. Specify food item
      3. Specify quantity
      4. Specify date added
    3. Subtask: remove food item(s) from food supply
      1. Precondition: Log into account
      2. Select food item(s)
      3. Delete selected items
  3. Task: Find and save recipes
    1. Subtask: find recipes based on food supply
      1. Precondition: Log into account
      2. Precondition: Specify current food supply (so that recipes can be found using those foods)
      3. Enter desired recipe difficulty
      4. View found recipes
    2. Subtask: save recipes
      1. Precondition: Log into account
      2. Precondition: Perform recipe search and select recipe
      3. Click to save recipe
    3. Subtask: view saved recipes
      1. Precondition: Log into account
      2. Select sorting method (newest, difficulty, etc.)

Domain analysis

  • No labels

1 Comment

    • Great user analysis, task analysis, and domain analysis.