Basic User Scenario - bounswe/bounswe2025group7 GitHub Wiki

Explore & Register

Persona & Story:

  • John is a 29-year-old software developer living in a mid-sized urban area. Recent market research shows that around 70% of users in his age group are looking for meal planning solutions that balance health and cost-efficiency. With a monthly grocery budget of about $350—averaging roughly $7 per meal—John is keen to explore an app that helps him manage both his nutritional goals and his spending.

Goals:

  • Goal 1: Discover a wide range of healthy, budget-friendly meal plans that offer detailed cost breakdowns and nutritional benefits.
  • Goal 2: Register on the app to save his favorite recipes, generate automated shopping lists, and access personalized meal plans based on his dietary preferences and budget constraints.

Pre-conditions:

  • None, because he is just exploring the app for the first time.

Scenario:

  • Step 1:

    • Action: John opens the app and is immediately greeted by a clean, intuitive interface. A prominent banner highlights “Healthy & Budget-Friendly Meal Plans” and mentions that users typically save up to 15% on their grocery bills using the app’s tools.
    • Details (Optional): Internal metrics indicate that first-time users spend an average of 7–10 minutes exploring the home page and featured recipes.

  • Step 2:

    • Action: He navigates to the “Meal Planning” section where recipes are organized by factors such as nutritional value and cost per serving.
    • Details (Optional): The app offers data-driven filters like “Under $8 per meal” and “High Protein Options.” Analytics show that about 65% of users in his demographic rely on these filters to narrow down their choices, which helps John quickly find recipes that match his needs.

  • Step 3:

    • Action: John selects a recipe that details a complete cost breakdown, preparation time, and nutritional facts. For example, the recipe lists a cost of $6.50 per serving and includes a weekly meal plan suggestion based on similar dietary preferences.
    • Details (Optional): Impressed by the transparency and practical insights, John clicks on “Register.” According to our data, nearly 20% of users who review such detailed recipes decide to register, attracted by benefits like saving recipes, generating personalized shopping lists, and tracking weekly meal expenses.

Outcome

  • This scenario uses real data insights and typical usage metrics to illustrate how a basic user like John might experience and engage with our healthy and budget-friendly meal planning app.

Requirements Covered:

  • 1.1.1.1: Signup (and later Login, Logout, Password Recovery/Change Password).
  • 1.2.1: Planner should be able to generate and compare meal options, considering restrictions imposed
  • 1.2.2: Planner should allow users to create and edit meal plans, with restrictions, based on their diet.
  • 1.4.1. Include a feature that automatically displays ingredients and generates a relevant shopping list.
  • 1.4.2. Users should be able to add or remove items from the generated shopping list as needed.
  • 1.4.3. Display nutritional values in the shopping list.
  • 1.4.4. Users to export their shopping lists for printing.
  • 1.6.1: User can create a recipe.
  • 1.6.2: Recipe includes essential details like cost and nutritional values.
  • 1.6.3. User should add recipe to meal planner.
  • 1.6.4. User should browse recipe by title, ingredient, tag, and type.

Mockup: