-
Notifications
You must be signed in to change notification settings - Fork 0
Weekly Meeting 2
muhammetsami edited this page Feb 24, 2026
·
2 revisions
- Topic: TA Feedback Evaluation & Discussion on Improvement of Scenarios
- Date: 2026-02-24
- Time: 22:00 - 23:00
- Location: Online - Google Meets
- Scribe: Muhammet Sami Çakmak
| Name | Status |
|---|---|
| Burak Öğüt | Present |
| Amin Abu-Hilga | Present |
| Övgü Su Afşar | Present |
| Muhammet Sami Çakmak | Present |
| Beratcan Doğan | Absent |
| İbrahim Kayan | Present |
| Mehmet Bora Sarıoğlu | Present |
| Halis Tunay Aslan | Absent |
- Analyzing our Teaching Assistant's feedback to Lab 2.
- Planning what we should do to make scenarios better.
- Talking about sequence diagram for the next lab.
- Headers: : The TA’s feedback regarding requirement headers was discussed. It was noted that headers should be reformatted using thicker fonts or clearer nested numbering to improve readability.
- Scenario 2: Feedback for Scenario 2 was reviewed. Although the user profile, mock-ups, and criteria were strong, the structure of the goals, pre-conditions, and main flow sections needs to be reorganized.
- Scenario 3: Feedback for Scenario 3 was discussed. The mock-up section was found to be incomplete, with missing images for steps 11–17.
- Sequence Diagram: The team discussed the importance of preparing a clear and consistent sequence diagram for the next lab, ensuring it aligns with the updated scenarios and follows UML standards.
- Decision 1: Requirement headers will be reformatted using thicker fonts or clearer nested numbering for better readability.
- Decision 2: Scenario 2 will be restructured by improving the bullet-point organization of goals, pre-conditions, and main flow sections.
- Decision 3: Scenario 3 will be updated by completing missing mock-ups for steps 11–17 and rechecking the scenario for completeness.
| Task Description | Assigned To | Priority | Deadline | Issue Link |
|---|---|---|---|---|
| [Fixing Requirements' Headers] | All | High | 2026-02-25 | #30 |
| [Improving structure of Scenario 2] | Mehmet Bora & Övgü Su | Mid | 2026-02-25 | #28 |
| [Completing Scenario 3 moke-ups] | Muhammet Sami & Beratcan & Amin | Mid | 2026-02-25 | #29 |
Team Members
- 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 (18/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Weekly Meeting Notes Template
- Lab Meeting 1 (12.02.2026)
- Weekly Meeting 1 (16.02.2026)
- Weekly Meeting 2 (24.02.2026)
- Weekly Meeting 3 (04.03.2026)
- Weekly Meeting 4 (11.03.2026)
- Weekly Meeting 5 (23.03.2026)
- Weekly Meeting 6 (29.03.2026)
- Weekly Meeting 7 (11.04.2026)
- Weekly Meeting 8 (28.04.2026)
- Weekly Meeting 9 (10.05.2026)
- Use Case Diagram 1 (New Mentor User for Mobile Scenario)
- Use Case Diagram 2 (Mentor-Mentee Matching Scenario)
- Use Case Diagram 3 (New Mentee User Scenario)
- Final Use Case Diagram
- MVP Use Case Diagram
- All Sequence Diagrams
- Sequence Diagram: Mentee Matching
- Sequence Diagram: Mentor Matching
- Sequence Diagram: Mentorship Management
- Sequence Diagram: Registration
- Sequence Diagram: Cancelling Mentorship Relationship and Auto Ban
- Sequence Diagram: Login-Logout
- Sequence Diagram: Reporting-User
- Sequence Diagram: Mentor Profile Management
- MVP Sequence Diagrams
- Test Plan & Coverage (MVP)
- Acceptance Testing Strategy
- Acceptance Tests
- Test Data Strategy
- Web Frontend Test Report
- Amin Abu-Hilga
- Övgü Su Afşar
- Muhammet Sami Çakmak
- Beratcan Doğan
- İbrahim Kayan
- Burak Ögüt
- Mehmet Bora Sarıoğlu
- Future Work (reference, not a deliverable)