-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting #4
Asaf31214 edited this page Mar 14, 2025
·
3 revisions
Date
10/03/2025
Time
21.00
Via
Google Meet
Member | Participation |
---|---|
Burak Tigin | ✓ |
Asaf Kanlıpıçak | ✓ |
Battal Hazar | ✓ |
Enver Eren | ✓ |
Gökberk Yavuz | ✓ |
Mehmet Batuhan Çok | |
Ömer Faruk Koramaz | |
Sezer Çot | |
İsmail Tarık Erkan | ✓ |
Ufuk Altunbulak | |
Yağız Kaan Aydoğdu | ✓ |
- Review and finalize numeric values for non-functional requirements.
- Plan scenario writing tasks.
- Decide responsibilities for Use Case and Class Diagrams.
- Determine issue creation and sub-issue assignment.
- The group finalized numeric values for all non-functional requirements (replacing the previous “XX” placeholders).
- Agreed that everyone will write or contribute to the scenario by Saturday.
- Identified the need to complete both Use Case and Class Diagrams this week.
- Formed two sub-teams:
- Class Diagram Team: Ömer Faruk Koramaz, Mehmet Batuhan Çok, Sezer Çot, Asaf Kanlıpıçak, and İsmail Tarık Erkan.
- Use Case Diagram Team: The remaining members (Burak, Gökberk, Battal, Yağız, Enver, etc.).
- Each main deliverable (Scenario, Use Case Diagram, Class Diagram) will have its own main issue, with sub-issues assigned to individual contributors.
- Scenario main issue will be created by İsmail Tarık Erkan.
- Use Case Diagram main issue will be created by Battal.
- Class Diagram main issue will be created by Asaf.
- All tasks are to be completed by Saturday.
# | Action | Assigned To | Issue Links |
---|---|---|---|
1 | Write scenario and create sub-issues for contributions | Scenario main issue to be opened by İsmail Tarık Erkan | Scenario Issue (Main) → sub-issues by each member |
2 | Complete Use Case Diagram by Saturday | Use Case Diagram Team; main issue by Battal | 42 |
3 | Complete Class Diagram by Saturday | Class Diagram Team; main issue by Asaf | Class Diagram Issue (Main) → sub-issues |