-
Notifications
You must be signed in to change notification settings - Fork 0
Elicitation Questions: Affordable & Healthy Eating Hub
-
Is there any component of this project that is for profit? No direct monetization focus. Platform serves as a marketplace for sellers to display products. [1.6.1.1.2]
-
Should there be a way for people to advertise their products? Sellers should list products and mention product origins when possible. [1.6.1.1.2]
-
Should users be able to set a budget in time intervals of their choice? Yes, optional budget setting for weekly/monthly meal planning. [1.5.1]
-
Should the budget planner adjust meal recommendations based on available funds? Yes, system will filter and recommend meals based on budget constraints while considering nutritional values. [1.5.3]
-
Can users track their grocery spending over time? Not a mandatory feature. Optional implementation. [1.6.2.3.1]
-
Should users receive notifications when they exceed their budget? No active budget tracking or notifications required.
-
Will the system integrate with third-party budgeting tools? Not specified in requirements.
-
What specific details should be included in the shopping list? System will recommend stores/sellers for ingredients based on availability and prices. [1.3.4]
-
How will the platform ensure that meal recommendations are nutritionally balanced? Product nutritional values will be predefined in the system. [1.1.1, 1.1.3]
-
How should the system determine whether a cook is experienced or not? No formal experience verification. User ratings and trust scores will indicate quality. [1.4.6]
-
Will users be able to set dietary preferences? Yes, users can add allergies and nutrition preferences (vegan, vegetarian, etc.) to filter recipes. [1.2.1, 1.1.4]
-
Should the platform provide daily/weekly nutrient breakdowns for planned meals? Users can set macronutrient priorities (low-carb, high-protein, etc.). [1.5.5]
-
Can users input health conditions to receive tailored meal recommendations? Yes, users can input allergies and dietary restrictions to filter meal options. [1.2.1, 1.5.3]
-
Should the system highlight nutrient-dense, low-cost foods for users? Yes, budget-friendly and nutritionally appropriate items will be highlighted. [1.3.5, 1.3.6]
-
Should recipes include a breakdown of costs per serving? Yes, based on standardized weight/unit measurements. [1.3.5]
-
Will users be able to filter recipes by budget, prep time, and dietary needs? Yes, comprehensive filtering options will be available. [1.3.5, 1.3.6]
-
Should users be able to rate and comment on shared recipes? Yes, forum-style rating and comment system implemented. [1.4.6.a, 1.4.6.b]
-
Can the system generate a grocery list from selected recipes? System will recommend stores for ingredients based on availability and prices. [1.3.4]
-
Should users be able to save favorite recipes for later? Yes, saving feature will be available. [1.2.7]
-
What will be the format of the recipes? Format includes: required ingredients with quantities, optional store recommendations, difficulty level, and step-by-step instructions. [1.3.1, 1.3.2, 1.3.3, 1.3.4]
-
Should users be able to see promotions and discounts from nearby stores? Not prioritized. Stores may manually enter promotional pricing. [1.6.1.1.2]
-
Should the system locate nearby food banks and farmers' markets? Any seller can create an account. Differentiation through ratings/reviews. [1.6.1.1.3, 1.6.2.1.2.e]
-
Should users be able to submit and update prices from their local stores? No, stores will be responsible for listing their own prices. [1.6.1.1.2]
-
What criteria should food stores meet to be considered 'local'? Defined at district/city level. Chain markets can participate but "local" label reserved for district/city sellers. [1.6.1.1.3]
- Three main user types: general users, dietitians, and store owners [1.2.8, 1.2.9]
- Reporting system for false information on products/stores [1.2.10, 1.4.8]
- Ranking systems for sellers, dietitians, and recipes [1.6.2.1.2.e, 1.4.5]
- Users can filter products by various features (natural, organic, etc.) [1.6.2.1.1, 1.6.2.1.2]
- Recipe measurements in grams with additional units (tablespoon, etc.) [1.3.1]
- Seasonal product availability managed by sellers [1.6.1.1.2]
- More detailed meeting transcript can be found on meeting notes discussion


-
Use Cases:
- Template
- Scenario 1: Community Sharing
- Scenario 2: For a Dietitian
- Scenario 3: Maintaining a Personal Inventory (as a Producer)
- Scenario 4: Proposing a Product and Adding a Recipe to Weekly Meal Plan
- Scenario 5: Creating a Meal Plan
- Scenario 6: Resetting Password
- Scenario 7: Moderator Actions
- Scenario 8: Searching for and Proposing a New Food Item
- Scenario 9: Budget-Conscious Grocery Shopping
- Scenario 10: Creating a New Store
- Scenario 11: User Profile Management
- Git: In a Nutshell
- Example GitHub Repositories
- System Modeling & UML
- Frontend Tutorial
- Frontend Roadmap
- Frontend Styling Guide
- Docker Summary
- Writing Endpoints
- Yusuf AKIN
- Arda SAYGAN
- Fatih Furkan Bilsel
- Berk GOKTAS
- Berkay BILEN
- Yusuf Anıl YAZICI
- Taha Topaloglu
- Nuri Basar
- Onur Kucuk
- Hasancan Keles
- Mete Damar