-
Notifications
You must be signed in to change notification settings - Fork 1
Lab 5 Report ‐ 12.03.2026
Gülce Tahtasız edited this page Mar 19, 2026
·
5 revisions
All team members successfully completed their individual tasks for the stub application.
At this stage of the project, the team has started organizing the development workflow and defining the initial structure of the application.
The team agreed on the following development conventions:
Commit Naming:
- feat: new feature
- fix: bug fix
- docs: documentation changes
- chore: maintenance tasks
Branch Naming:
- feature/
- bugfix/
Merge Policy:
- tests pass
- documentation updated
- builds succeed
The team selected Option A: Specialized Sub-Teams.
- devops/frontend - Kağan Can
- devops/backend - Mehmet Can Gürbüz
- frontend - Gülce Tahtasız
- frontend - Ethem Erinç Cengiz
- backend - Rojhat Delibaş
- backend - Alper Kartkaya
- backend - Berat Sayın
Implementation Plan (MVP + Final Milestone): Implementation Plan
Kagan Can
- Implemented Button 4 functionality using a public JSON API.
- Integrated the API call into the stub application interface.
Ethem Erinç Cengiz
- Implemented Button 5 functionality using a Random Joke public API.
- Integrated the API response display within the stub application.
Rojhat Delibaş
- Implemented Button 1 functionality using a public API.
- Connected the API call to the stub application button handler.
Mehmet Can Gürbüz
- Implemented Button 3 functionality using the Open-Meteo Weather API.
- Displayed weather information retrieved from the API.
Alper Kartkaya
- Implemented Button 7 functionality using a Random Joke API.
- Created and configured the Dockerfile for the stub application container.
Berat Sayın
- Implemented Button 6 functionality using a Random Advice API.
- Integrated the API response into the stub application button.
Gülce Tahtasız
- Implemented Button 2 functionality using the Random Advice API.
- Added API fetch logic and displayed the returned advice in the interface.
Date: 12.03.2026
🎓 Team Members
- Weekly Meeting 1 (16.02.2026)
- Weekly Meeting 2 (25.02.2026)
- Weekly Meeting 3 (04.03.2026)
- Weekly Meeting 4 (11.03.2026)
- Weekly Meeting 5 (18.03.2026)
- Weekly Meeting 6 (25.03.2026)
- Weekly Meeting 7 (01.04.2026)
- Weekly Meeting 8 (08.04.2026)
- Weekly Meeting 9 (15.04.2026)
- Weekly Meeting 10 (29.04.2026)
- Weekly Meeting 11 (06.05.2026)
- Weekly Meeting 12 (13.05.2026)
- Lab 1 Report (12/02/2026)
- Lab 2 Report (19/02/2026)
- Lab 3 Report (26/02/2026)
- Lab 4 Report (05/03/2026)
- Lab 5 Report (12/03/2026)
- Lab 6 Report (26/03/2026)
- Lab 7 Report (02/04/2026)
- Lab 8 Report (16/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Scenario 1: Injured Neighbor
- Scenario 2: Volunteer Users Help Offer
- Scenario 3: User Registration and Profile Setup
- Use Case Diagram (Final)
- Use Case Diagram for Scenerio 1 ‐ Sub‐group 2
- Use Case Diagram for Scenerio 2 ‐ Sub‐group 3
- Use Case Diagram for Scenerio 3 ‐ Sub‐group 1
- Sequence Diagram - Alper Kartkaya
- Sequence Diagram - Kağan Can
- Sequence Diagram - Mehmet Can Gürbüz
- Sequence Diagram - Ethem Erinç Cengiz
- Sequence Diagram - Berat Sayın
- Sequence Diagram - Gülce Tahtasız
- Sequence Diagram - Rojhat Delibaş