Customer Milestone 1 Report of CMPE 451 Fall 2025

Customer Milestone 1 Report

Group Name: Group 9
Project: Affordable & Healthy Eating Hub

---

Deliverables Overview

Deliverable	Link	Notes
Revised Software Requirements Specification (SRS)	Requirements	Updated requirements
Revised Software Design (UML Diagrams)	Sequence Diagrams, Class Diagrams, UML Use Case Diagrams	Class, Use Case, Sequence
Team Development Policies	Team Policies
Communication Plan	Communication Plan
Project Plan	CMPE451 Implementation Roadmap	Timeline, scope, owners, and dependencies for Milestones 1–3; kept in the team wiki.
Weekly Reports & Meeting Notes	Weekly Reports & Meeting Notes
Milestone Review	(see below)	Summary and reflections
Individual Contributions	(see below)	Each member's contribution wiki link placed below
Pre-release Software

---

Milestone Review

1. Project Status Summary

• Current status:
  Customer Milestone 1 completed with 76% of targeted requirements fully implemented (31/43 requirements). Application is functionally deployed via Docker with web, mobile, and backend operational. Core features (food database, forum, recipes, meal planner, registration) are production-ready. Critical gaps remain in recipe cost calculation, authentication (via email services), budget features, and advanced moderation. The project is on track for MVP milestone with strategic adjustments based on customer feedback.

• Major accomplishments:

  • Food Database & Proposals: 500+ food items with complete user proposal and moderator approval workflow
  • Forum System: Full-featured community platform with posts, comments, likes, tags, and filtering
  • Recipe Management: Robust ingredient tracking with nutritional aggregation and scoring
  • User Profiles: Complete allergen management (12 predefined + custom), profession tags with certificate upload
  • Token Issuance: JWT-based secure login/logout with password change functionality
  • Meal Planner: Functional deterministic generation with dietary filters, exceeding expectations (done viable implementation vs. expected planned interfaces)
  • Testing Foundation: 11 backend test files + frontend/mobile test suites with good coverage
  • Production Deployment: Docker-compose setup with MySQL, Django, Nginx, SSL/TLS support

• Features implemented:
  Complete (31 requirements): Food proposals (1.1.2.1), allergen management (1.2.1-1.2.4), profession tags (1.2.9), recipe system (1.3.1-1.3.3, 1.3.7-1.3.8), full forum (1.4.1-1.4.7), meal planner core (1.5.2-1.5.5), account management (1.7.1-1.7.4), basic moderation (1.8.1, 1.8.4-1.8.6)

  Partial (6 requirements): Micronutrient display (1.1.2.2 - 40%), certificate verification with bugs (1.2.10 - 30%), budget features (1.5.1 - 30%), role definitions (1.8.2-1.8.3 - 60%), report system UI (1.8.7 - 40%)

  Not Implemented (6 requirements): Recipe cost calculation (1.3.5-1.3.6), email services (1.7.5-1.7.6), advanced moderation (1.8.8-1.8.9)

• Features pending or planned:
  MVP Milestone (Nov 25): Recipe cost system, email services (password reset/verification), meal planner budget features, complete market system (inventory, stores, listings, shopping lists), automated content moderation with appeals, community impact metrics, extended user profiles, forum reporting system

  Final Release (Dec 16): WCAG 2.1 AA accessibility compliance, security hardening (logging, backups, privacy controls), performance optimization (50+ concurrent users, <5s search), full internationalization (RTL/LTR support)

• Upcoming goals for next milestone:

  1. Fix Critical Bugs: Certificate verification, micronutrient display, authentication edge cases
  2. Complete Core Features: Recipe cost calculation, email integration, budget UI and logic
  3. Implement Market System: Producer inventory management, store creation, consumer search/shopping lists
  4. Advanced Moderation: Automated detection, appeals system, reporting backend, 48-hour SLA
  5. Community Features: Impact metrics, contribution badges, "This helped me" tracking
  6. Quality & Performance: >70% code coverage, API documentation, performance testing (50 concurrent users)

  Success Criteria: All M1 bugs fixed, recipe costs working, email operational, market complete, moderation automated, appeals functional, community metrics visible, performance targets met

2. Customer Feedback and Reflections

• Positive aspects: Based on the demo, customer feedback was overall positive, with particular praise for the platform's focus on trust, accessibility, and seamless feature integration.

  • The author verification system (with "Nutritionist" tags and verified badges) was seen as a major strength. This directly addresses user "pain points" about misinformation and builds immediate confidence in the platform's recipes and advice.
  • The platform was praised for its deep personalization that goes beyond simple calorie/macronutrients tracking or forum. The ability to set and filter by specific religious (e.g., Halal) and lifestyle (e.g., Vegan) dietary needs right from setup makes users feel the app is built for them.
  • The meal planner was highlighted as being flexible. Users appreciated that they could not only generate a plan but also easily modify it by removing items and adding foods to their liking, giving them a sense of control.
  • The clean presentation of data, such as displaying calories and macros in large, distinct text, was highly rated. This directly benefits users who need clear information without hassle.
  • The seamless flow between the Forum, Recipe, and Food Catalog was a positive aspect. Eren's scenario clearly showed how a user could go from finding a recipe, to verifying its author, to deep-diving into a single ingredient's nutritional facts, all within one app.
  • The advanced search capabilities in the forum, such as searching by a tag ("vegan") and then searching the terms in the recipe, and in the meal planner were recognized as a powerful tool for users with specific health and performance goals.

• Requested improvements or clarifications:

  • Recommended to use schema.org format for the recipes via processing and importing the recipes, help easing and automating the post creation process since it takes significantly less effort to determine ingredients related to the serving sizes.
  • The Meal Planner feature should be implemented for mobile due to several key advantages regarding portability - one can use the meal planner to determine the meal of the day while one is outside where it is infeasible, sometimes impossible to use a laptop or a browser setup.
  • Making sure we are able to present the mobile using Android emulator on the screen for future demos.
  • Consider adding micronutrients on food items (Sounded optional, more of a soft recommendation)
  • Explain the meaning of nutrition score and how it is calculated for food items in UI.
  • What's healthy differs from person to person - may incorporate some restrictions for certain macronutrients (e.g. global constraints on sugar, salt etc.) and can also include recommendations and food macro/micro constraints for celiacs, for people with diabetes, high blood pressure etc.
  • We may include a calorie calculator for meal planner (Optional, not really sure that it is explicitly recommended)

• Action items derived from feedback:

  Action	Assignee	Deadline
  Implement schema.org Recipe Integration	Frontend and Backend Teams	MVP Milestone
  Prioritize Mobile Meal Planner	Mobile Team	MVP Milestone
  Prepare Mobile Demo Setup	Mobile Team	MVP Milestone
  Add Micronutrient Data (Optional)	Backend Team	MVP Milestone
  Explain Nutrition Score in UI	Frontend Team	MVP Milestone
  Implement Personalized Health Constraints	Frontend Team	MVP Milestone
  Evaluate Meal Planner Calorie Calculator (Optional)	Frontend and Backend Team	MVP Milestone

  • Implement schema.org Recipe Integration: Develop a processing and import system for recipes using the schema.org format to automate post creation and simplify ingredient/serving size management.
  • Prioritize Mobile Meal Planner: Focus development of the Meal Planner feature on the mobile application to ensure portability for users on the go.
  • Prepare Mobile Demo Setup: Configure and test an Android emulator (or similar tool) to ensure the mobile application can be reliably presented on-screen for future demos.
  • Add Micronutrient Data: (Optional) Investigate adding micronutrient details (e.g., vitamins, minerals) to food items.
  • Explain Nutrition Score in UI: Implement a UI element (like a tooltip or info icon) that clearly explains the meaning of the "nutrition score" and its calculation method.
  • Implement Personalized Health Constraints: Enhance the system to support personalized dietary needs, such as global macronutrient restrictions (sugar, salt) and specific constraints for conditions like celiac disease, diabetes, or high blood pressure.
  • Evaluate Meal Planner Calorie Calculator: (Optional) Assess the feasibility and value of adding a calorie calculator feature within the meal planner.

3. Deliverables Status

Deliverable	Status	Comments
Requirements (SRS)	✅ Complete	Requirements v1.1.2 finalized with 43 functional requirements across 7 categories. Market features (1.6) removed per scope refinement. Reflects current product scope with clear acceptance criteria.
Design Documents	✅ Complete	Includes comprehensive sequence diagrams, class diagrams, and UML use case diagrams. Models updated to reflect current implementation including FoodProposal, MealPlan, Recipe, and Tag verification workflows.
Front-end	🟡 Functional	React + TypeScript web application fully deployed. Core features implemented: food catalog with proposals, forum with posts/comments/likes, recipe creation with nutrition tracking, meal planner, user profiles with allergens and profession tags. Missing: Recipe cost calculation and filtering features. Responsive design with consistent styling.
Mobile App	🟡 Functional	React Native (Expo) app with feature parity to web. Implemented: food browsing and proposals, forum interactions, user profile management, allergen selection, profession tags with certificate upload. Clean UI with theme support. Missing: Recipe cost features, meal planner optimization for mobile UX
Backend	✅ Functional	Django REST Framework with MySQL database. Comprehensive API coverage for all implemented features. JWT authentication, file uploads for certificates/images, pagination for performance. Implemented: 40+ endpoints across 5 apps (accounts, foods, forum, meal_planner, api). Missing: Email service configuration (password reset, verification), recipe cost calculation endpoints, report submission system.
Deployment	✅ Complete	Docker-compose configuration ready with MySQL 8.0, Django (Gunicorn), and Nginx. Health checks implemented. SSL/TLS certificate support via certbot.
Testing	✅ Ongoing	Backend: 11 test files covering authentication, profiles, allergens, forum (posts/comments/likes/recipes), food proposals. All tests passing. Frontend: Vitest setup with component and page tests. Mobile: Jest test suite with service and screen tests. Coverage: Core features well-tested, need coverage for cost calculation once implemented. Unit tests ongoing with good foundation established.

---

4. Reflection on Tools & Processes

Evaluate tools, frameworks, and processes used:

Version Control:

Git was actively and effectively used throughout the milestone. The team followed a structured workflow where each change originated from an issue, was implemented in a dedicated branch, and submitted as a pull request (PR) for peer review before merging. Branches were clearly separated by component (backend, frontend, mobile), ensuring cleaner merges and better traceability. Collaborative merge sessions were conducted during milestone preparation to prevent integration conflicts.

Project Management:

The team maintained weekly full-group meetings for progress tracking and planning. Additionally, smaller sub-team meetings (backend, frontend, mobile) were held to focus on component-specific issues. Tasks were tracked through GitHub Issues and Milestones, and ownership was clearly assigned to ensure accountability.

Collaboration:

Milestone objectives were divided into smaller, manageable tasks that were distributed fairly among team members. Communication channels such as WhatsApp and Discord were actively used to coordinate urgent updates, discuss blockers, and maintain continuous collaboration. Collective contribution and shared ownership were achieved across all teams.

Design Tools:

Design artifacts, including UML diagrams (class, sequence, and use-case), were created and maintained directly in PlantUML. The team collaboratively edited the diagrams within code blocks to ensure version control compatibility and ease of updates. Visual outputs were then exported from HackMD for documentation and wiki integration. This approach allowed for precise, code-based diagram management while keeping all design assets synchronized with the current system architecture and requirements.

Development Stack:

The development stack included:

• Frontend: React + TypeScript
• Mobile: React Native (Expo)
• Backend: Django REST Framework + MySQL
• Deployment: Docker Compose with Nginx and SSL

This stack enabled modular development and parallel progress across all components. Consistent API documentation and shared models ensured smooth communication between frontend, backend, and mobile teams.

Testing:

Testing was conducted through a combination of automated and manual approaches:

• Backend: Postman and unit tests to verify API reliability and data integrity.
• Frontend/Mobile: Manual scenario testing to ensure bug-free demo experience.
• Automated Tests: 11 backend test files and initial Jest/Vitest setups for frontend and mobile.

Reflection:

What worked well? What needs improvement for the next milestone?

What worked well:

• Milestone scenarios were successfully deployed with smooth feature integration.
• Database migration and deployment were effectively handled across environments.
• Collaboration was strong, supported by active communication and clear task ownership.

Areas for improvement:

• Physical meetings proved difficult to organize, affecting real-time collaboration during critical stages. Improved scheduling or hybrid setups could increase efficiency.
• Team members could better flag tasks that are too complex for one person or when unexpected workloads arise, allowing others to step in and assist earlier.

Overall, the established Git workflow, clear task ownership, and consistent development stack created a solid foundation for parallel development, successfully supporting the milestone goals and resulting in smooth feature integration. Our primary commitment for the next phase is to build on this by formalizing processes for time coordination and early workload flagging. This will transform our existing successful collaboration into a more predictable and highly efficient development cycle.

5. Requirements Covered in This Milestone

Summary Statistics

• Total Requirements Addressed: 43
• Fully Implemented: 31 requirements (72%)
• Partially Implemented: 6 requirements (14%)
• Not Implemented: 6 requirements (14%)

✅ Fully Implemented Requirements (31)

1.1 Food Database (1.5/2 - 75%)

R1.1.2.1: User-proposed food items with moderator review

• Users can submit new food items via web and mobile forms
• Moderators review and approve via Django admin panel (inline editing)
• Approved proposals automatically create FoodEntry records

R1.1.2.2: Optional micronutrient data submission (🟡 Partial - 40%)

• Users can submit additional nutritional data (fiber, sugar) in proposal forms
• Optional fields supported in FoodProposal model
• Missing: Micronutrient data not displayed in food catalog view

1.2 User Profile Management (5.3/6 - 88%)

R1.2.1: Allergen selection from predefined list

• 12 predefined allergens: gluten, lactose, peanuts, soy, shellfish, eggs, tree nuts, sesame, fish, sulfites, artificial colorants, preservatives
• Multi-select interface with visual feedback

R1.2.2: Custom allergen addition

• Users can add allergens not in predefined list
• Custom allergens stored with common=false flag
• Duplicate prevention and validation

R1.2.3: Personal recipes list view

• Users can view their created and liked recipes
• Separate views for owned vs. liked recipes

R1.2.4: Contact information storage and update

• Email, address, and contact details stored in User model
• Update functionality in profile settings

R1.2.9: Profession tags with "Unverified" badge

• Users can add profession tags (Dietitian, Store Owner)
• Tags display "Unverified" badge by default
• Badge changes to "Verified" after moderator approval

R1.2.10: Certificate upload for profession tags (🟡 Viable - 30%)

• Users can upload certificates (JPG, PNG, PDF, max 5MB)
• Files stored in certificates/ directory
• Validation for file type and size
• Known Issues: Bug in tag verification system identified
• Status: Core functionality exists but requires bug fixes for production readiness

1.3 Recipe Management (6/8 - 75%)

R1.3.1: Recipes include list of ingredients

• RecipeIngredient model links foods to recipes
• Amount specified in grams per ingredient

R1.3.2: Recipes include links to nutritional values

• Each ingredient references full FoodEntry nutritional profile
• Automatic aggregation of nutritional data

R1.3.3: Recipes include preparation steps

• Instructions field for step-by-step guidance
• Rich text input supported

R1.3.7: Recipes have aggregated nutrition score

• Calculated from ingredient quality and nutritional profile
• Totals computed for: protein, fat, carbohydrates, calories

R1.3.8: Sort and filter recipes by nutrition score

• Sort: Highest to lowest nutrition score
• Filter: Minimum nutrition score threshold
• Sort: Newest to oldest by posting date

1.4 Forum & Nutrition Tips (7/7 - 100%)

R1.4.1: Posts have tags, owners can edit

• Post-Tag many-to-many relationship
• Tag types: Dietary tip, Recipe, Meal plan, Vegan, Halal, High-Protein
• Post owners can modify tags after creation

R1.4.2: Users can write free-text forum posts

• Title and content fields
• Markdown support for rich formatting

R1.4.3: Nutrition tips provided

• Users can create posts tagged as "Nutrition tip"
• Tips displayed in forum feed with special styling

R1.4.4: Users can browse forum posts

• Paginated post listing (5 posts per page, configurable)
• Post preview cards with author, date, likes, comments count

R1.4.5: Filter posts by tags and sort by rating

• Filter by: Dietary tip, Recipe, Meal plan
• Filter by dietary options: Vegan, Halal, High-Protein
• Sort by: Likes/rating, date

R1.4.6: Interact with posts (like, comment, share, unlike)

• Like/unlike posts with real-time count updates
• Comment on posts with nested replies support
• Share posts via link copy

R1.4.7: Posts have categorization tags

• Pre-seeded tags in database via migration
• Color-coded tag chips for visual distinction
• Tag-based navigation and filtering

1.5 Meal Planner (3/5 - 60%)

R1.5.1: Select budget for meal planning (🟡 Partial - 30%)

• MealPlan model supports budget field in backend
• Missing: Budget input UI not implemented in frontend
• Missing: Budget calculation and tracking logic not functional

R1.5.2: Share meal plans as post

• Integration with forum post system
• Meal plans tagged appropriately for discovery
• Plan details displayed in post format

R1.5.3: Generate meal plans deterministically

• Seeded pseudo-random algorithm (seed = userId + weekStartISO)
• Filters: Dietary preferences (vegan, halal, high-protein), allergen exclusions
• Target: ±10% of recommended daily macronutrients
• Reproducibility: Same seed always produces identical meal plan

R1.5.4: Save and reuse meal plans

• Create meal plan
• List user's meal plans
• Set active plan

R1.5.5: Nutritional summaries for meal plans

• Automatic calculation: total_calories, total_protein, total_fat, total_carbohydrates
• Updated via calculate_total_nutrition() method
• Displayed to users in summary format

1.7 Account Management (4/6 - 67%)

R1.7.1: Sign up with email, username, password

• CreateUserView with user registration
• Password hashing with bcrypt
• Username uniqueness validation

R1.7.2: Log in with username and password

• JWT token authentication (access + refresh tokens)
• Token-based session management

R1.7.3: Log out of account

• Token invalidation on logout
• State cleanup in frontend/mobile

R1.7.4: Change password functionality

• Validates old password before allowing change
• Secure password hashing with bcrypt
• Authenticated users only

1.8 Moderation (4/9 - 56%)

R1.8.1: Administrator and moderator privilege system

• Django built-in admin system activated
• User roles: is_staff, is_superuser flags
• Permission-based access control

R1.8.4: Food item submission review

• AdminFoodProposal panel with inline editing
• isApproved field editable in list view
• Automatic FoodEntry creation on approval
• Search and filter by name, approval status

R1.8.5: Profession tag and certificate verification

• TagAdmin panel with bulk actions
• Verify certificates action (bulk approve)
• Reject certificates action (bulk deny)
• Certificate file display and download

R1.8.6: Moderation dashboard

• Django Admin Panel at /admin/ route
• Access control: is_staff permission required
• View all models: users, posts, comments, food proposals, tags

🟡 Partially Implemented Requirements (6)

R1.1.2.2: Optional micronutrient data submission (40% complete)

• Missing: Display of micronutrient data in food catalog, user-facing views don't show micro data
• Impact: Users can submit but not view the additional nutritional information

R1.2.10: Certificate upload for profession tags (30% complete)

• Missing: Bug fixes needed in tag verification system
• Impact: Feature exists but not production-ready due to identified bugs

R1.5.1: Budget selection for meal planning (30% complete)

• Missing: Frontend UI for budget input, budget calculation logic, budget tracking features
• Impact: Meal plans can be created but without budget constraints

R1.8.2: Role definitions (60% complete)

• Missing: Specific role implementations (General Admin, System Admin, Content Admin, Data Admin, Community Moderator)
• Note: Can be implemented using Django groups and permissions system

R1.8.3: General Administrator privilege inheritance (60% complete)

• Missing: Explicit role hierarchy and documentation

R1.8.7: Report details display (40% complete)

• Missing: Backend Report model, report submission endpoints, report retrieval endpoints

❌ Not Implemented Requirements (6)

R1.3.5: Recipe cost estimation with geographic scopes (0% complete)

• Required but missing: Algorithm to average 3 lowest prices per ingredient, scope expansion logic (Neighborhood → District → City), scope level display

R1.3.6: Recipe filtering by cost (0% complete)

• Required but missing: Filter by lowest to highest cost, highest to lowest cost, best cost-to-nutrition ratio
• Dependency: Requires R1.3.5 implementation first

R1.7.5: Password reset via email (0% complete)

• Required but missing: Password reset endpoint, email sending functionality, reset token generation/validation

R1.7.6: Email authentication on signup (0% complete)

• Required but missing: Verification email sending, email verification endpoint, account activation workflow

R1.8.8: Moderation actions (remove, warn, ban) (20% complete)

• Implemented: Manual deletion via Django admin
• Missing: Dedicated API endpoints for removing posts, warning users, banning users

R1.8.9: Moderation history log (0% complete)

• Required but missing: ModerationAction model, audit trail for all moderation actions, history view for moderators

📊 Coverage by Feature Category

Category	Requirements	Implemented	Partial	Missing	Completion
1.1 Food Database	2	1	1	0	75%
1.2 User Profile	6	5	1	0	88%
1.3 Recipe Management	8	6	0	2	75%
1.4 Forum & Nutrition Tips	7	7	0	0	100%
1.5 Meal Planner	5	4	1	0	82%
1.7 Account Management	6	4	0	2	67%
1.8 Moderation	9	4	3	2	56%
TOTAL	43	31	6	6	76%

Key Implementation Highlights

1. Food Proposal Workflow: Complete end-to-end implementation from user submission to moderator approval with automatic catalog entry creation.

2. User Profile Richness: Comprehensive profile system with allergen management (12 predefined + custom), profession tags with verification, certificate uploads with validation.

3. Recipe System: Full recipe creation with ingredient tracking, nutritional aggregation, and forum integration. Missing only cost-related features.

4. Forum Engagement: Rich interaction system with likes, comments, sharing, and comprehensive tagging/filtering capabilities.

5. Meal Planner: Strong implementation with deterministic generation, dietary filters, and backend persistence. Budget features pending.

6. Authentication & Security: Robust JWT-based authentication with password change functionality and comprehensive test coverage.

7. Moderation Foundation: Django admin provides immediate moderation capabilities for food proposals. Certificate verification has known bugs requiring fixes. Advanced features deferred to MVP.

Features Deferred to MVP Milestone

Based on customer feedback emphasizing complete, functional features over partial implementations, the following requirements have been strategically postponed:

1. Budget Calculation System (R1.3.5, R1.3.6): Recipe cost estimation with geographic pricing and cost-based filtering
2. Email Service Integration (R1.7.5, R1.7.6): Password reset and email verification workflows
3. Advanced Moderation (R1.8.8, R1.8.9): Dedicated moderation action endpoints and audit logging

These features require substantial infrastructure work and will be delivered as cohesive, production-ready implementations in the MVP milestone rather than incomplete versions in CM1.

6. Impact on Project Plan

Our current progress has highlighted some imbalances and improvement areas in the overall project plan. Initially, our planning placed too much emphasis on the first milestone, which focused heavily on feature development rather than on requirements gathering and elicitation. As a result, later milestones appeared comparatively lighter in scope.

Originally, we intended to complete the core features early and dedicate the remaining milestones to bug fixing and incremental improvements. However, following customer feedback, we decided to adjust our approach. The feedback emphasized delivering complete, functional features in each milestone rather than partial implementations. Consequently, we postponed some requirements—particularly those related to Budget and Moderation features—to the upcoming milestones to ensure higher feature completeness and more meaningful deliverables.

Adjustments to Milestone Planning

• The features “Budget Calculation for Recipes and Meal Plans” and “Reporting and Moderation Actions”—originally planned for the first milestone—will now be completed in the upcoming MVP milestone. The team expects faster progress on Moderation Actions, while Budget Calculation remains a crucial element of the application and will receive focused attention to ensure its inclusion in the MVP.

• We identified several backend infrastructure issues that affected both the mobile and web teams. For instance, the Tag object was not user-specific—meaning when a tag was verified, it was verified for all users, which was not logical. To resolve this, we are currently revising backend data models and endpoints. These structural improvements will be finalized before the MVP milestone.

• Another key realization is the need to prioritize user experience (UX). For example, although the Meal Planner has been implemented for the web, it lacks the functionality and usability required for mobile users. Moving forward, we will place greater emphasis on improving UX and ensuring that our design decisions are informed by user empathy and usability testing.

• Finally, we decided to allocate additional time to ensure compliance with W3C accessibility standards. While inclusivity has been a focus from the beginning, adhering to W3C guidelines will help us achieve a more accessible and robust application. Related improvements will be incorporated into the MVP and final milestones.

---

Individual Contributions

Name	Individual Contribution
Yusuf Akın	Individual Contribution
Nuri Başar	Individual Contribution
Berkay Bilen	Individual Contribution
Fatih Furkan Bilsel	Individual Contribution
Mete Damar	Individual Contribution
Berk Göktaş	Individual Contribution
Hasancan Keleş	Individual Contribution
Onur Küçük	Individual Contribution
Arda Saygan	Individual Contribution
Yusuf Anıl Yazıcı	Individual Contribution
Osman Selim Yüksel	Individual Contribution

---