Group Milestone 3 Report

1. Executive Summary

• Project Status Summary: (Provide a concise overview of the current state of the project, what has been achieved, and what remains. Discuss the product maturity and main features implemented.)
• Status of Deliverables: (List deliverables and their states: Completed, In Progress, Not Started. Highlight which features meet all criteria: implemented, tested, documented, deployed.)
• Final Release Notes: (Detail the final release, including version numbers, major improvements since last milestone, and known issues.)
• Changes Made to Improve Development Process: (Describe what process changes were introduced since the previous milestone. For example, implementing stricter code reviews, improving CI/CD pipelines, adding new collaboration tools, or adjusting sprint planning. Explain how these changes impacted overall productivity and quality.)
• Reflections on the Final Milestone Demo:
  • Lessons Learned: (Discuss key takeaways from the final demo, focusing on what went well and what challenges were faced.)
  • What Could Have Been Done Differently: (Reflect on the early project stages and identify strategies that would have led to a more efficient project completion. Provide reasons and justifications.)

2. Progress Based on Teamwork

• Team Contributions Table: (Create a table summarizing each team member’s contributions. For example, columns could include Name, Subgroup (Backend/Frontend/Mobile), Key Features Implemented, Issues Resolved, Tests Written, Documentation Tasks, etc.)

Member Name	Subgroup	Key Features Implemented	Issues Resolved	Tests Written	Documentation & Other Contributions
Ahmet Fırat Gamsız	Frontend	...	...	...	...
Soner Kuyar	Backend	...	...	...	...
Orhan Ünüvar	Mobile	...	...	...	...
Ozan Kaymak	Mobile	...	...	...	...
Işıl Su Karakuzu	Frontend	...	...	...	...
Yusuf Aygün	Backend	...	...	...	...

(Ensure this table matches the details given in individual reports.)

3. Status of Requirements

• Requirements Progress: (List each requirement and state its status: Not Started, In Progress, Completed (implemented, tested, documented, deployed).)
• Summary: (Highlight major achievements and any requirements that remain incomplete. Explain why some requirements might not be fully completed.)

4. API Endpoints

• API Documentation: (Provide a link to the API documentation, such as a Swagger UI link or a GitHub page.)
• Core API Calls:
  1. Example Endpoint 1: (Describe the endpoint, required parameters, request method, and example request/response. Explain how to replicate the call, including any authentication details.)
  2. Example Endpoint 2
  3. Example Endpoint 3
• Postman Collection: (Optional: Link to a Postman collection or provide instructions for importing it.)

5. User Interface / User Experience

• Links to UI Code: (For each major UI component or screen, provide a hyperlink to the code in the repository.)
• Screenshots of Web and Mobile Interfaces: (Show final implemented designs and highlight any improvements from previous milestones.)
• UX Considerations: (Explain how user feedback or best practices influenced the UI/UX design. Note any changes made since previous milestones.)

6. Standards

• Application of W3C Standards: (Explain which W3C standards you applied, how they were integrated into the project, and any documentation or validation steps performed to ensure compliance.)

7. Scenarios

• Comprehensive Scenario: (Describe a realistic user scenario that showcases the core functionalities of your project end-to-end. Include steps and expected outcomes, referencing the features that were completed. For example: User logs in → browses games → filters results → comments on a move → likes a post. Explain how each part is realized in code and linked to the requirements.)

8. Individual Documentation

Ahmet Fırat Gamsız

• Member: Ahmet Fırat Gamsız, Frontend
• Responsibilities: (Overall assigned tasks.)
• Main Contributions: (List major code contributions, features implemented, or tasks completed.)
• Code-Related Significant Issues: (Link to GitHub Issues that added or fixed code critical to the final demo.)
• Management-Related Significant Issues: (Link to Issues related to planning, documentation, or other non-coding tasks.)
• Pull Requests: (List personal PRs with brief descriptions and links.)
• Unit Tests: (List tests authored, linking to the files or commits in the repository.)
• Additional Information: (Any other noteworthy contributions, attendance in meetings, communication efforts.)

Soner Kuyar

• Member: Soner Kuyar, Backend
• Responsibilities:
• Main Contributions:
• Code-Related Significant Issues:
• Management-Related Significant Issues:
• Pull Requests:
• Unit Tests:
• Additional Information:

Orhan Ünüvar

• Member: Orhan Ünüvar, Mobile
• Responsibilities:
• Main Contributions:
• Code-Related Significant Issues:
• Management-Related Significant Issues:
• Pull Requests:
• Unit Tests:
• Additional Information:

Ozan Kaymak

• Member: Ozan Kaymak, Mobile
• Responsibilities:
• Main Contributions:
• Code-Related Significant Issues:
• Management-Related Significant Issues:
• Pull Requests:
• Unit Tests:
• Additional Information:

Işıl Su Karakuzu

• Member: Işıl Su Karakuzu, Frontend
• Responsibilities:
• Main Contributions:
• Code-Related Significant Issues:
• Management-Related Significant Issues:
• Pull Requests:
• Unit Tests:
• Additional Information:

Yusuf Aygün

• Member: Yusuf Aygün, Backend
• Responsibilities:
• Main Contributions:
• Code-Related Significant Issues:
• Management-Related Significant Issues:
• Pull Requests:
• Unit Tests:
• Additional Information: