Final Milestone Planning: Sprint 1 & 2 (Immediate Feedback Integration)

Project Plan: Sprint 1 & 2 (Immediate Feedback Integration)

1. Objectives for the Next Two Weeks

The primary goal for this period is "Refinement through Feedback." We are shifting focus from pure feature addition to refining existing data models and visualizations based on the critique received during the Milestone 2 review.

Key Objectives:

1. Refactor Core Data Models: Move RecipeModel to a central database structure (FNDDS integration) to stop reliance on mock data.
2. Enhance Visualization: Implement Spider Web (Radar) Charts universally for nutrition comparisons, as requested by Suzan Hoca.
3. Smart User Guidance: Implement the "Healthy Range Warning" for food quantities and include "Water Intake" in nutrition scoring.
4. Advanced Filtering: Enable users to filter foods by specific micronutrient ranges.
5. Employ W3C Standards: Ensure that our application uses W3C standards.

---

2. Task Breakdown

1. Backend Architecture & Algorithms (Week 1 Focus)

Owner: Furkan & Berk

• RecipeModel Refactoring (High Priority):

  • Task: Refactor the RecipeModel serializer and views.

  • Detail: Stop using local/hardcoded recipe tables. Refactor Recipe model to Recipe model in Schema.org and populate recipes directly from an external database.

• Nutrition Score Update:

  • Task: Update the nutrition scoring algorithm.

  • Detail: Factor in Water Intake as a positive metric in the daily health score calculation.

• Database Enrichment (Healthy Ranges):

  • Task: Add a recommended_max_quantity or healthy_range field to food items in the food catalog.

  • Detail: This is required to support the frontend warning system

2. Frontend Visualization & Guidance (Week 2 Focus)

Owner: Arda (Web) & Osman (Mobile)

• Spider Web (Radar) Charts Expansion:

  • Task: Generalize the Radar Chart component used in "Compare" and apply it to:

    • Daily Nutrition Summary.

    • Recipe Nutrition Breakdown.

  • Detail: As requested by Suzan Hoca, this visual format must be the standard for displaying nutrient balance.

• Quantity Warnings:

  • Task: Implement UI logic in the Food Log/Meal Planner.

  • Detail: If user inputs > healthy_range (e.g., 500g of sugar), display a visual warning (Toast/Red Border) suggesting a lower amount.

• Future-Oriented Meal Planner:

  • Task: Enhance the Meal Planner to consider "what if"s.

  • Detail: Allow users to plan their next meals while seeing detailed nutritions calculations, together with the healthy ranges. They should be able to select future dates (e.g., next week) and save meal plans to those specific calendar slots.

3. Advanced Search & Moderation (Continuous)

• Micronutrient Filtering:

  • Task: Update Search API and UI Filter Sidebar.

  • Detail: Add range sliders (Min-Max) for specific micros (e.g., "Vitamin C > 50mg", "Sodium < 200mg").

  • Assignee: Berk (Backend) / Frontend Team.

• Admin Panel - Proposal Editing:

  • Task: Upgrade the Moderation Dashboard.

  • Detail: Moderators must be able to edit a user's food proposal (fix typos, adjust calories) before approving it, rather than just Rejecting it.

---

3. Timeline: Two-Week Sprint

Timeline	Primary Focus	Key Deliverables
Week 1	Backend & Data Structure	• RecipeModel refactored. • Nutrition Score is improved, with additional conideration for micronutrients and water . • Food catalog updated with "Healthy Ranges." • Micronutrient Filter API ready. - W3C standards employed.
Week 2	Visuals & UX	• Spider Web Charts on Dashboard/Recipe views. • "Healthy Range" warnings operational on Web/Mobile. • Meal Planner supports future dates. • Admin Panel "Edit Proposal" feature deployed.

---

4. Impact on Previous Plan

• Delayed: The "Recipe Costing" and "Budget" features are shifted slightly to accommodate the RecipeModel refactoring, as a stable data model is required before accurate costing can be calculated.

• Documentation: The Documentation team must immediately update the Use Case Diagrams to reflect the new "Future Planning" and "Moderation Edit" flows, as the current diagrams were noted as unclear.