-
Notifications
You must be signed in to change notification settings - Fork 0
Milestone Report ‐ Milestone Summaries
Date: Apr 25 2025
Main Goal: Present the requirements and initial design of the application to the customer. Demonstrate a basic version of the application with partial feature implementation to gather early feedback.
Sub-goals
- Complete requirements and design related documentation.
- Learn the basics of backend, frontend and mobile development.
- Set up the skeleton of the implementation.
Deliverables
- Requirements Specification Document
- Scenarios
- Use Case Diagrams
- Class Diagrams
- Sequence Diagrams
Date: May 11 2025
Main Goal: Speed up implementations and retain the momentum we lost due to unexpected events. Implement the selected subset of the requirements, which can be found in Milestone 2.
Sub-goals
- Determine and implement backend endpoints required in the milestone requirements.
- Start the integration of endpoints to frontend and mobile.
- Research how to deploy our website and release mobile apk.
Date: May 14, 2025
The final stage of the project for the semester. The selected requirements will be implemented and a populated and functional demo will be presented to demonstrate the system’s capabilities.
Sub-goals
- Implement missing endpoints if any and integrate with frontend and mobile.
- Deploy the application and release mobile apk.
- Populate the database with real-world data.
Requirements to be implemented
1.1. Food Database 1.1.1 The system shall include a list of at least 500 common food items with nutritional details, including protein, fat, and caloric content. 1.1.3 The system shall calculate and display a nutrition score (scale of 0.00-10.00) for each food item based on: Protein content (30% of score) Carbohydrate quality (30% of score, favoring complex carbs over simple sugars) Nutrient balance (40% of score, representing the overall balance of macro and micronutrients) 1.1.4 The system shall support the following dietary options: (If posible a subset) a) Low-fat b) High-protein c) Vegetarian d) Vegan e) Celiac-friendly f) Gluten-free g) Lactose-free 1.4. Forum & Nutrition Tips
- 1.4.1 Posts shall have tags, and the post owners shall be able to edit those tags.
1.4.2 Users shall be able to write free-text forum posts. 1.4.3 Nutrition tips shall be provided to guide users on healthy eating habits. 1.4.4 Users shall be able to browse forum posts. 1.4.5 Users shall be able to filter posts by tags and sort them by rating. 1.4.6 Users shall be able to interact with forum posts by, a) Liking posts b) Commenting on posts c) Sharing posts via a link d) Unliking liked posts 1.4.7 Posts can have tags that could be used for filtering the following tags: a) Dietary tip b) Recipe c) Meal plan 1.7. Account Management
- 1.7.1 Users shall be able to sign up by giving their mail address, choosing a unique username and a secure password.
- 1.7.2 Users shall be able to log in using their username and password.
- 1.7.3 Users shall be able to log out of their account.
Deliverables
- Final Milestone Report
- Project Repository (including Issues, Wiki, and implementation)
- Live Demo with Sample Data


-
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