Customer Milestone 1 Report: Fitness and Diet Forum - bounswe/bounswe2024group4 GitHub Wiki
- Scenario 1: Logging in and Seeing Posts
- Scenario 2: Posting an Exercise Program
- Scenario 3: Posting a Diet Program
- Scenario 4: Rating Another User's Programs
- Scenario 5: Chatting with Another User
🔴 C -> Contributed
🔵 R -> Reviewed
empty cell -> None
| Berat Yılmaz | Bilge Kaan Güneyli | Miraç Öztürk | Murat Can Kocakulak | Zeynep Buse Aydın | Nurullah Uçan | Ceyhun Sonyürek | Ahmet Batuhan Canlı | Talha Ordukaya | |
|---|---|---|---|---|---|---|---|---|---|
| Design | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Create scenario for creating and sharing diet program | -- | 🔵 | -- | 🔴 | 🔴 | -- | -- | -- | -- |
| Create scenario for rating shared exercises and diet programs | -- | -- | -- | -- | -- | -- | 🔴 | -- | -- |
| Create scenario for logging in and interacting with a post | -- | -- | 🔴 | -- | -- | -- | -- | -- | -- |
| Create scenario for chatting with another user | -- | -- | -- | -- | -- | 🔴 | -- | -- | -- |
| Create scenario for creating and sharing exercise program | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Create user requirements | -- | 🔴 | -- | -- | 🔵 | -- | -- | -- | -- |
| Create system requirements | -- | 🔴 | -- | -- | -- | -- | -- | -- | -- |
| Create non-functional requirements | -- | 🔵 | -- | -- | -- | -- | -- | -- | -- |
| Create mockups (mobile) for scenarios | -- | -- | -- | -- | -- | -- | -- | -- | 🔴 |
| Create mockups (web) for scenarios | 🔴 | 🔵 | -- | -- | 🔵 | -- | -- | -- | 🔵 |
| Create sequence diagrams of creation actions | -- | 🔴 | -- | -- | 🔴 | -- | -- | -- | 🔵 |
| Create sequence diagrams of deletion actions | -- | -- | -- | -- | -- | 🔴 | -- | -- | 🔵 |
| Create sequence diagrams of view actions | -- | -- | -- | -- | -- | -- | -- | -- | 🔴 |
| Create sequence diagrams of rating a program and supermember actions | -- | -- | -- | -- | -- | -- | -- | -- | 🔵 |
| Create sequence diagram of searching | -- | 🔴 | -- | -- | -- | -- | -- | -- | 🔵 |
| Create sequence diagrams of follow actions and account features | -- | -- | -- | -- | -- | -- | 🔴 | -- | 🔵 |
| Create sequence diagram of adding exercise to database | -- | 🔴 | -- | -- | 🔵 | -- | -- | -- | 🔵 |
| Create sequence diagram for Wikidata and Nutrition Analysis API Integration | -- | 🔵 | -- | -- | 🔴 | -- | -- | -- | 🔵 |
| Create sequence diagram of Exercises API integration | -- | 🔴 | -- | -- | 🔵 | -- | -- | -- | 🔵 |
| Create sequence diagram of post interactions | -- | -- | 🔴 | -- | -- | -- | -- | -- | -- |
| Create the class diagram of the "Fitness and Diet Forum" project | -- | -- | -- | 🔴 | -- | -- | -- | -- | -- |
| Create the use case diagram of the "Fitness and Diet Forum" project | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Mobile Implementation | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Initialize | 🔵 | -- | -- | -- | -- | 🔵 | 🔴 | -- | -- |
| Implement tab bar | 🔴 | -- | -- | -- | -- | 🔵 | 🔵 | -- | -- |
| Implement exercise selection UI | 🔴 | -- | -- | -- | -- | 🔵 | 🔵 | -- | -- |
| Implement exercise program widget | 🔵 | -- | -- | -- | -- | 🔵 | 🔴 | -- | -- |
| Implement feed (home) page and post object | 🔵 | -- | -- | -- | -- | 🔴 | 🔵 | -- | -- |
| Create readme | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Research | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Research W3C | -- | -- | -- | -- | -- | 🔴 | -- | -- | -- |
| Frontend Implementation | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Initialize | -- | -- | 🔵 | -- | 🔴 | -- | -- | -- | -- |
| Dockerize | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Create the home page and dashboard | -- | -- | 🔵 | -- | 🔵 | -- | -- | -- | -- |
| Create post component | -- | -- | 🔴 | -- | 🔵 | -- | -- | -- | -- |
| Implement My Meals page | -- | -- | 🔵 | -- | 🔴 | -- | -- | -- | -- |
| implement create a meal UI | -- | -- | -- | -- | 🔴 | -- | -- | -- | -- |
| Create readme for frontend | -- | -- | -- | -- | 🔴 | -- | -- | -- | -- |
| Backend Implementation | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Initialize | -- | 🔴 | -- | 🔴 | -- | -- | -- | -- | 🔵 |
| Implement Workout Program Creation | -- | 🔴 | -- | 🔵 | -- | -- | -- | -- | 🔵 |
| Implement Authentication in Backend | -- | -- | -- | 🔵 | -- | -- | -- | -- | 🔴 |
| Create README for Backend | -- | 🔵 | -- | 🔴 | -- | -- | -- | -- | 🔵 |
| Create general README | -- | 🔴 | -- | -- | 🔵 | -- | -- | -- | 🔵 |
| Dockerize | -- | 🔴 | -- | 🔴 | -- | -- | -- | -- | 🔵 |
| Report | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Create RAM for Milestone | 🔴 | -- | -- | -- | -- | -- | -- | -- | -- |
| Requirements addressed | -- | 🔴 | -- | -- | -- | -- | -- | -- | -- |
| Summary of the project | -- | -- | -- | -- | -- | -- | -- | -- | -- |
| Evaluation of tools | -- | -- | 🔴 | -- | -- | -- | -- | -- | -- |
| Summary of the customer feedback and reflections | -- | -- | -- | -- | 🔴 | -- | -- | -- | -- |
| List and status of deliverables | -- | -- | -- | -- | -- | -- | 🔴 | -- | -- |
| Add evaluation of the status of deliverables | -- | -- | -- | -- | -- | -- | -- | -- | 🔴 |
| Project Plan | -- | -- | -- | -- | -- | 🔴 | -- | -- | -- |
| -- | -- | -- | -- | -- | -- | -- | -- | -- |
We are developing a fitness and diet forum targeting fitness enthusiasts. So far, we have created scenarios and mockups, defined our requirements, and in the design phase, we have developed sequence diagrams, class diagrams, and use case diagrams. In the implementation phase, we have initialized our frontend, backend and mobile parts. Then, we have successfully implemented our distinguishing features—meal creation and exercise program creation—meal creation on the web and exercise program creation on mobile.
Next, we will implement standard forum features such as login and profile functionalities. Following that, we’ll integrate APIs to assist with meal and exercise program creation. We plan to expand our exercise pool with more comprehensive exercises like cardio. We’re also considering adding a tracking mechanism for both exercises and meals, a feature to demonstrate or explain how exercises are performed, and improvements to make the meal-adding process easier for super users.
- We should include both macronutrients and micronutrients of the food in the nutrients tab.
- Cardio exercises can be added to the exercises list, they do not necessarily just weight exercises for one specific muscle group.
- Nutrients are scaled (they are all in grams), it would be better if we also scale ingredients as well so that they will have the same unit.
- There should be a mechanism for keeping track of the meals just like the exercises. Users should be able to keep track of what they ate, how many grams of which nutrient and how many calories they got from a meal.
- We should add a "how to" part inside of exercises so that the users will know how to do that exercise, what not to do and what to be careful about.
- Users should be able to keep track of each exercise, not the whole exercise program as a package.
| Deliverable | Status | Due Date | Related Link |
|---|---|---|---|
| Software Requirements Specification | Delivered on time | 25 Oct 2024 at 17:00 | Requirements |
| Class Diagram | Delivered on time | 25 Oct 2024 at 17:00 | Class Diagram |
| Use Case Diagrams | Delivered on time | 25 Oct 2024 at 17:00 | Use Case Diagrams |
| Sequence Diagrams | Delivered on time | 25 Oct 2024 at 17:00 | Sequence Diagrams |
| Updated Project Plan | Delivered on time | 25 Oct 2024 at 17:00 | Github Roadmap |
| Communication Plan | Delivered on time | 25 Oct 2024 at 17:00 | Communication Plan |
| Responsibility Assignment Matrix | Delivered on time | 25 Oct 2024 at 17:00 | RAM |
| Weekly reports and any additional meeting notes | Delivered on time | 25 Oct 2024 at 17:00 | General Meeting Notes #2, Lab4 Meeting Notes, General Meeting Notes #1, Lab3 Meeting Notes, Lab2 Meeting Notes, Lab1 Meeting Notes, Lab4 Report, Lab3 Report, Lab2 Report, Lab1 Report |
| Customer Milestone 1 Report | On progress | 25 Oct 2024 at 17:00 | Milestone Report |
| A pre-release version of your software | Delivered on time | 22 Oct 2024 at 08:00 | Release 0.1.0 |
This document set clear expectations early, reducing ambiguity and aiding prioritization of tasks. By aligning requirements with the project plan, we minimized the need for mid-project revisions and were able to schedule tasks more effectively.
Completing UML diagrams before development provided a visual roadmap, enabling efficient task assignment and reducing potential bottlenecks. These diagrams aligned technical and non-technical team members on the system’s structure, fostering a shared understanding and smoothing the transition into coding.
Detailed scenarios gave us a user-focused view, while mockups provided a reference point for frontend development, aligning functionality and design. Their early completion reduced rework and facilitated a smooth start to implementation.
The project plan and RAM offered an organized structure for managing tasks and responsibilities, supporting balanced workloads across sub-teams. Minor adjustments are expected as task demands evolve, but these tools have promoted a structured and collaborative environment, essential for maintaining momentum.
Consistent documentation of meetings and reports has strengthened internal communication, providing a reliable reference for decisions and action items. This regular review process has kept the team aligned with project goals and facilitated accountability.
We extensively utilized GitHub Issues for task allocation and tracking.
This facilitated clear communication and collaboration among the different subteams (mobile, frontend, backend).
GitHub allowed us to manage tasks effectively and maintain an organized workflow throughout the project.
In our project, we utilized a combination of robust development tools to create a cohesive application across multiple platforms.
For the backend, we employed Django, leveraging its rapid development capabilities, built-in security features, and scalability to efficiently manage our RESTful APIs and database interactions.
The frontend was built using React, which allowed us to develop a responsive and visually appealing user interface with a component-based architecture, enhancing code reusability and maintainability.
For mobile app development, we focused solely on React Native, benefiting from its ability to create a seamless experience specifically for Android devices.
This technology stack facilitated effective integration among various components of our application, although we faced challenges in ensuring smooth communication between the backend and frontend.
Additionally, the process of revising and merging pull requests fostered strong team collaboration and control.
Team members reviewed each other’s code, provided constructive feedback, and ensured adherence to coding standards.
This practice not only improved code quality but also enhanced our collective understanding of the codebase.
Overall, these tools significantly contributed to our development process, enabling efficient workflows and high-quality deliverables.
For communication, we utilized group WhatsApp chats for general team discussions and team-specific groups.
This streamlined conversations among different technology-focused subteams.
Additionally, we used Discord for course-related notifications, ensuring timely updates for all members.
Meetings were held via Zoom, while face-to-face evaluations took place during lab hours, allowing for in-depth discussions and feedback.
We relied on GitHub Wiki for documentation and knowledge sharing.
This played a crucial role in maintaining a centralized repository of project information.
This resource was invaluable for onboarding new team members and ensuring that everyone had access to the necessary documentation.
In conclusion, the tools and processes we implemented were instrumental in managing the complexities of our project.
The task sharing was executed in a very organized manner.
This allowed each subteam to focus on their specific areas while ensuring that everyone was aligned with the overall project goals.
This structure not only promoted effective collaboration among team members but also fostered a culture of mutual control.
Team members regularly reviewed each other's work through the process of revising and merging pull requests.
This practice enhanced code quality and reinforced collective ownership of the project.
Furthermore, our communication was robust and effective, facilitated by various platforms such as WhatsApp and Discord.
These tools enabled timely updates and swift responses, which were critical in maintaining momentum throughout the project.
Regular meetings via Zoom and face-to-face evaluations during lab hours further strengthened our team dynamics.
These interactions allowed for in-depth discussions and real-time feedback.
Overall, the combination of well-organized task management, strong collaboration, and effective communication significantly contributed to our ability to deliver high-quality results.
The lessons learned during this milestone will undoubtedly inform our strategies for future phases of the project, as we continue to refine our processes and enhance our teamwork.
The requirements addressed in the milestone are listed below. The table below displays these requirements regarding on which department the relevant requirement is met.
1.1.1.1 Guest activities
- 1.1.1.1.1 Guests shall be able to see only the log-in and sign-up pages.
- 1.1.1.1.2 Guests shall be able to sign-up to the platform with an e-mail address, unique username and a password that contains at least 8 characters which includes at least 1 special character, 1 numerical figure, 1 uppercase letter and 1 lowercase letter.
1.1.2.1 Authentication
- 1.1.2.1.1 Members shall be able to log-in to their account by providing their username and password.
1.1.2.3 Member activities
- 1.1.2.3.3 Members shall be able to create diet and workout programs by combining options provided by the platform.
- 1.1.2.3.5 Members shall be able to view other members' posts.
- 1.1.2.3.6 Members shall be able to comment on posts.
- 1.1.2.3.7 Members shall be able to like and unlike posts.
- 1.1.2.3.13 Members shall be able to bookmark and unbookmark content.
1.1.2.4 Super-member activities
- 1.1.2.4.1 Super-members shall be subject to all the requirements which are related to members.
- 1.1.2.4.3 Super-members should be able to provide new food options to the food database of the platform.
1.2.1 Main page
- 1.2.1.1 Main page shall display the latests contents created by the users followed.
- 1.2.1.2 Main page shall be able to be scrolled to display older content.
1.2.2 Diet program/Meal
- 1.2.2.3 The platform shall return the nutritional values of foods which shall be retrieved from the Edamam Nutrition API.
- 1.2.2.4 The platform shall provide links to recipes of foods which shall be retrieved from the Edamam Nutrition API.
1.2.3 Workout program
- 1.2.3.1 Members shall be provided muscle options to combine in their workout program.
- 1.2.3.2 Members shall be provided exercise options for the muscles they have chosen which shall be retrieved from the Ninjas Exercises API and platform database to create exercise programs.
1.2.5 Posts
- 1.2.5.1 Posts shall support having text, images, diet programs, workout programs and contain user-curated content.
2.1 Accessibility & Availability
- 2.1.1 The platform shall be available in English.
- 2.1.2 The platform shall support UTF-8 character encoding to accommodate a wide range of characters and symbols.
2.7 Compatibility
- 2.7.1 The platform’s web interface shall be compatible with the latest versions of major browsers including Chrome, Firefox, Safari, and Edge.
- 2.7.2 The Android application shall support Android 13.0 and above.
| Backend | Web | Mobile |
|---|---|---|
| 1.1.1.1.1 | 1.1.2.3.3* | 1.1.2.3.3* |
| 1.1.1.1.2 | 1.1.2.3.5 | 1.1.2.3.5 |
| 1.1.2.1.1 | 1.1.2.3.6 | 1.1.2.4.1 |
| 1.1.2.3.3* | 1.1.2.3.7 | 1.2.1.1 |
| 1.1.2.4.1 | 1.1.2.3.13 | 1.2.3.1 |
| 1.2.3.1 | 1.1.2.4.1 | 1.2.3.2 |
| 1.2.3.2 | 1.1.2.4.3 | 1.2.5.1 |
| 2.1.1 | 1.2.1.1 | 2.1.1 |
| 2.1.2 | 1.2.1.2 | 2.1.2 |
| 1.2.2.3 | 2.7.2 | |
| 1.2.2.4 | ||
| 1.2.5.1 | ||
| 2.1.1 | ||
| 2.1.2 | ||
| 2.7.1 |
Member: Berat Yılmaz
Responsibilities: My responsibilities were creating the web mockups and contributing to mobile development.
Main contributions: I created the web mockups, implemented exercise selection and creation UI in mobile app, and deployed our frontend and backend to DigitalOcean.
Code-related significant issues:
Non-code-related significant issues:
- #337 Create web mockups
Pull requests that you have created, merged, and reviewed:
- #366 Add tab bar to mobile
- #383 Partially implement exercise creation UI
- #391 Finish exercise selection UI
- #398 Add frontend to docker compose
- #399 Use backend to get exercises
- #404 Fix exercise selection UI
Reviewed or merged:
- #372 Add Post Component and Integrate into Home Feed
- #373 Workout program component added to mobile
Member: Bilge Kaan Güneyli
Responsibilities: One of my responsibilities in the project were creating the user requirements with Batuhan and system requirements by myself and also reviewing all the requirements. I was also responsible for the sequence diagrams of searching features and API integrations, in this task we had to cooperate with Buse because our tasks were highly related. In the coding side of the project, I was responsible for initializing the backend, creating the endpoints related to workout plans, dockerizing the backend in which I got help from Can and creating a general readme.Main contributions: One of my main contributions in the project was communicating with my friends (mainly Buse) to decide the integration of Edamam API and diet program features. I also contributed to creation of most of the requirements for the project.
My code related contributions were initializing the backend, creating workout related endpoints. Creating the Dockerfile and creating a draft of docker-compose file for Can to finalize. I also reviewed some of the PRs related to the backend part.
Code-related significant issues:
- Initialize backend
- Dockerize backend
- Create docker compose
- Implement workout program creation in backend
- Create general readme
Non-code-related significant issues:
- #331 - created user requirements
- #333 - created and reviewed system requirements
- #353 - created sequence diagram of searching
- #355 - created sequence diagram of adding exercise to database
- #357 - created sequence diagram of Exercises API integration
- #405 - updated requirements
- #356 - reviewed sequence diagram of Wikidata and Edamam API integration
- #375 - reviewed backend readme
Pull requests:
- #345 - Initialized backend
- #377 - Implemented the workout program endpoints and dockerized backend
- #401 - Created general readme
- #389 - Reviewed the file structure of backend
- #400 - Reviewed backend readme
Additional information: We created the presentation scenario with my friends. I participated in all the meetings and as addition, I made a lot of communication on Whatsapp in order to decide certain aspects of the project.
Member: Murat Can Kocakulak
Responsibilities: I was responsible for creating exercise program scenario, reviewing the backend initialization, creating the app structure inside backend folder, creating class diagram and reviewing authentication in the backend for sign-up, login, and logout functionalities and creating exercise program. Additionally, i added the ReadMe file for backend
- Create the general structure of Backend: In order to be able to work on it together without potential conflicts, I have separated the backend apps like use_auth, exercise_program, diet_program etc
- DockerFile: Finalized the Docker File, getting it ready for deployment
- Project Evaluation: Evaluated the status of our deliverables, analyzed their impact on the project plan, and provided reflections to guide future development.
- #342 I reviewed initializing of the backend and created the app file structure.
- #361 I finalized the dockerization of backend
- #375 I created the ReadMe of backend stating which prompts to write on the terminal in order to start the backend
- #375 I created Readme for Backend
- #358 I created class diagram of the project
- #340 I created scenario for creating and sharing exercise program
- #371 I structured the backend app files accordingly
- #389 I have changed the urls structure to fitness_project urls file instead of keeping urls separate inside apps
- #394 I finalized the dockerazation of the project
- #400 I created ReadMe for the Backend
- #377 I reviewed implementing workout program
- #388 I reviewed authentication properties that Talha made
Throughout the project, I had the change to communicate with my group and design our path. Because I was more experienced on the Backend part thanks to last semester, I managed to be more comfortable with the changes that I made. I think separating the app structure inside backend will boost our collaboration and work management in the future
Member: Zeynep Buse Aydın
I was responsible for several key aspects of the project, including the design part and focusing on frontend on the code part. My responsibilities included creating sequence diagrams of creating meal (and food) and exercise programs, designing scenarios for creating and sharing diet, and diet API integration, implementing features in frontend and reviewing the frontend PRs.
I took on both technical and organizational responsibilities in the project. On the technical side, I initialized the frontend project, implemented the "Meals" page, and added functionality for creating and managing meals and food items. I reviewed all the frontend PRs including the implementing sidebar, navbar, and post features to ensure a consistent user interface.
On the organizational side, I put so much effort on communicating with Kaan to decide the integration of Edamam API and diet program features. I designed scenarios for diet program creation, created sequence diagrams for diet program, food and exercise creation including the Nutrients API integration. I also wrote a readme file for running the frontend, and summarized customer feedback for the milestone report.
- #341 I initialized the frontend project. PR#347
- #360 I reviewed the sidebar and navbar in frontend. PR#381
- #364 I reviewed post component in frontend.
- #365 I implemented the "Meals" page in frontend with displayable data. PR#379 PR#386
- #392 I implemented the create a meal part in frontend with also creating and adding food to the meal functionality. PR#393
- #330 I created the scenario for creating and sharing a diet program.
- #348 I created the sequence diagrams of creation actions: Create Post, Create Exercise Program, Create Diet Program
- #356 I created the sequence diagram of creating new food options (covers Wikidata and Nutrition Analysis API integration).
- #357 I reviewed the sequence diagram of Exercises API integration
- #396 I created readme file of frontend which includes the instructions on how to run the project. PR#402
- #411 I added the summary of the customer feedback and reflections from the demo session to the milestone report.
- #347 I initialized frontend project.
- #378 I reviewed tailwind css initialization.
- #379 I implemented the "Meals" page in frontend with displayable data. There was a small conflict in tailwind config file which I solved basically just getting the most recent file in this commit.
- #381 I reviewed the sidebar and navbar in frontend.
- #386 I implemented the MealList component.
- #387 #395 I reviewed the post component and its like/unlike, comment displays in frontend.
- #393 I implemented creating a meal (including creating and adding food to the meal), and deleting a meal.
- #401 I reviewed general readme.
I presented the customer demo. I designed the presentation (the scenario) with my teammates. I was always available to communicate with my teammates if there is anything to discuss, decide or solve. I was present in all lab sessions and I attended one of our two meetings.
Member: Nurullah Uçan
My responsibilities included developing key features for the mobile application, particularly focusing on the implementation of the feed (home) page, which displays user posts. I also created scenarios for the chatting with another user feature to enhance user interaction. On the documentation side, I researched and documented W3C standards, created sequence diagrams for deletion actions, and contributed to the project roadmap to guide our development process.
I contributed significantly to the development of the feed (home) page UI and outlined scenarios for the chatting feature to improve user interaction. I researched and documented W3C standards, providing valuable insights that will aid in future development. Additionally, I helped shape the project roadmap by prioritizing key features.
- #370 Implement feed (home) page and post object in mobile
- #335 Create scenario for chatting with another user
- #344 Research and document W3C Standards
- #350 Create sequence diagrams of deletion actions
- #413 Create the project plan on the roadmap
- #372 Add Post Component and Integrate into Home Feed
- #366 Add tab bar to mobile (Reviewed)
- #373 Workout program component added to mobile (Reviewed)
- #383 Partially implement exercise creation UI (Reviewed)
- #390 A widget for workout programs to edit them (Reviewed)
Before this milestone, the HomeScreen, Signup, and Login components were created in my own branch; however, they were not connected to the backend, so we decided not to present them in the customer milestone to provide a better overall demonstration.
Member: Ceyhun Sonyürek
I contributed to the project design by creating scenarios and preparing sequence diagrams. On the implementation side, I was part of the mobile team, where I helped initialize the mobile setup, developed the exercise program widget, worked on UI design, and reviewed other team members' work, providing feedback and suggestions.
- Created scenario for rating shared exercises and diet programs.
- Created sequence diagrams of follow actions and account features.
- Initialized mobile and reviewed all mobile PR's.
- Developed the exercise program widget.
- Attended all labs and shared ideas and supported every team decision.
- #332 Create scenario for rating shared exercises and diet programs
- #354 Create sequence diagrams of follow actions and account features
- #416 Add list and status of deliverables to milestone report
- #346 Initialize mobile
- #366 Add tab bar to mobile (Reviewed)
- #372 Add Post Component and Integrate into Home Feed (Reviewed)
- #373 Workout program component added to mobile
- #383 Partially implement exercise creation UI (Reviewed)
- #390 A widget for workout programs to edit them
- #391 Finish exercise selection UI (Reviewed)
Attended all labs, worked hard, implemented lots of codes and contributed to our strong teamwork.
Member: Ahmet Batuhan Canlı
Responsibilities: My responsibilities were writing system requirements and non-functional requirements and also reviewing user requirements.For the design part creating use case diagram.For the development part creating topbar and navbar, dockerizing frontend, initializing tailwindcss were my responsibilites.Main contributions: About our project domain and which API’s we can use I communicated with my team and we share our ideas.I wrote system requirements part with Kaan and I wrote non-functional system requirements.I also created our project’s use case diagram.I created topbar and left-sidebar for our frontend part.I also dockerized frontend part of our project.
Code-related significant issues:
- #362 – I dockerized frontend part by creating a dockerfile and testing it on docker PR
- #360 – I created topbar and left-sidebar of our project PR
- #341 – I contributed initializing process with reviewing and initializing tailwind css PR
- #364 – I reviewed the post component
- #365 – I reviewed the meals page
- #392 – I reviewed the create meal UI Non-code-related significant issues:
- #333 – I created our system requirements with Kaan.We also reviewed each other’s parts. Requirements
- #338 – I created our non-functional Requirements
- #359 – I created the Use case diagram
Pull requests :
- PR-378 – I added the tailwind css to our project. I created the pr
- PR-381 – I created the sidebar and the topbar for our frontend.I created the pr and merged.
- PR-382 – I created the dockerfile of our frontend. I created the pr and merged.
- PR-379 – I reviewed meals feature created by Buse. I have not encountered any conflict issues.
Additional information: I controlled the computer when we show our frontend part in our demo, We worked on a scenario for it. Also I communicate with my team via whatsapp to exchange ideas.
Member: Talha Ordukaya
I was responsible for creating mockups for all five user scenarios, reviewing the backend initialization, creating sequence diagrams for key user actions (viewing a post with its comments, viewing the following feed, and viewing profiles), and implementing authentication in the backend for sign-up, login, and logout functionalities. Additionally, I added an evaluation of the status of deliverables and its impact on our project plan.
- Mockups: Designed detailed mockups for all five user scenarios outlined in our project wiki, enhancing the team’s understanding of the user interface and user experience.
- Sequence Diagrams: Developed sequence diagrams for critical user actions, providing clear visual representations of system interactions for viewing posts, following feeds, and profiles.
- Backend Authentication: Implemented authentication endpoints in the backend, enabling users to securely sign up, log in, and log out.
- Project Evaluation: Evaluated the status of our deliverables, analyzed their impact on the project plan, and provided reflections to guide future development.
- #336 I created mockups (mobile) for scenarios.
- #351 I created sequence diagrams of view actions.
- #415 I added evaluation of the status of deliverables for Milestone 1.
- #388 I added sign up, login and log out functionalities.
- #345 I reviewed initializing backend.
- #376 I reviewed Can init backend to main.
- #376 I reviewed creating workout programs and exercises.
- #377 I reviewed implementing workout program and dockerized backend.
- #389 I reviewed Can final urls structure.
- #400 I reviewed creating README.md for backend.
Throughout the project, I actively participated in team meetings and collaborated closely with my teammates to ensure alignment between frontend and backend development. I took the initiative to address critical tasks like backend authentication, balancing design and implementation responsibilities. By reflecting on the project’s progress, I helped re-prioritize tasks to meet milestones and proposed workflow improvements. I expanded my technical skills in both design and backend development. Additionally, I contributed to documentation by ensuring that diagrams and mockups were accessible and up-to-date, and assisted in maintaining clarity for the team’s benefit.
Member: Miraç Öztürk
Responsibilities
- Attended all labs and meetings to stay updated with the project’s progress.
- Actively worked on completing assigned tasks within the team.
- Took on responsibilities in frontend development.
- Adapted to group dynamics and fostered effective communication.
Main Contributions
- As a new member, I focused on integrating myself into the team.
- Participated in frontend development tasks.
- Successfully completed my assigned responsibilities.
- Developed a user scenario and contributed to the creation of a sequence diagram.
- Created and enhanced a post component for the frontend, ensuring thorough testing.
Code-related Significant Issues
-
Resolved Issue #364: Create post component
- In PR #387, I successfully developed the post component and ensured it was properly integrated into the application flow.
-
Resolved Issue #364: Implement like and comment features for posts
- In PR #395, I added the functionality for users to like and comment on posts.
- Utilized diverse static data, sourced from real-world examples, to effectively showcase the features of the component I developed.
Non-code-related Significant Issues
-
Resolved Issue #329: Update pages as a newcomer to the team
- I created the "About Me" page and included my information as a new team member.
-
Resolved Issue #334: Create a scenario for logging in and interacting with a post
- Successfully developed a scenario outlining user login, post serving, and liking functionalities.
-
Resolved Issue #349: Create sequence diagrams for like, bookmark, and comment features
- Prepared a sequence diagram illustrating all three functionalities simultaneously.
-
Resolved Issue #409: Writing Evaluation of tools and processes used to manage the team project for milestone report
- Composed a comprehensive and informative chapter summarizing the evaluation.
-
Resolved Issue #410: Create Milestone 1 Individual Contributions
- Authored my individual contributions for the milestone report.
Pull Requests
-
PR #387:
- Encountered conflicts during the development process, which I resolved by carefully reviewing requirements to ensure a seamless integration without errors.
- PR #395:
Additional Information
- Participated in all labs and meetings to ensure active engagement and collaboration within the team.