-
Notifications
You must be signed in to change notification settings - Fork 3
Meeting 6.1
Alper Canberk Balcı edited this page Apr 9, 2022
·
1 revision
- Alper Canberk Balcı
- Halil Burak Pala
- Mehmet Emre Akbulut
- Sinan Kerem Gündüz
- Kardelen Demiral
- Yavuz Samet Topçuoğlu
- Mehmet Akif Yılmaz
- Burak Mert
- Engin Oğuzhan Şenol
- Baver Bengin Beştaş
- Oğuzhan Demirel
- Buse Tolunay
- Homework about Software Design, teamwork effort meeting. Part 3
- Milestone 1, project plan and RAM
- Sequence Diagrams reviews
- Editing Use Case and Class Diagram
- Milestone 1, project plan, and remaining editions
# | Task | Assignee | Reviewer | Review Deadline | Task Deadline |
---|---|---|---|---|---|
1 | Customer Meeting 3 Notes upload | Alper Canberk Balcı | Halil Burak Pala | 11.04.2022 14:00 | 11.04.2022 20:00 |
- In Slack: Uskudarli: "You can indicate the database transactions with natural language. You can indicate the action with instert/add remove/delete update select/find"
- Unasked question: what to return from DB: save success or status etc.
🏠 Homepage
- Alper Canberk Balcı
- Baver Bengin Beştaş
- Burak Mert
- Halil Burak Pala
- Kardelen Demiral
- Sinan Kerem Gündüz
- Yavuz Samet Topçuoğlu
- Mehmet Emre Akbulut
- Oğuzhan Demirel
- Engin Oğuzhan Şenol
- Irfan Bozkurt
- Ozan Kılıç
Meeting Notes From CMPE352
Meeting Notes From CMPE451
- Meeting 13.1
- Meeting 14.1
- Meeting 15.1
- Meeting 16.1
- Meeting 18.1
- Meeting 19.1
- Meeting 20.1
- Meeting 21.1
- Meeting 23.1
- Meeting 24.1
Backend Team Meetings
Frontend Team Meetings
Mobile Team Meetings
- Customer Meeting 1
- Customer Meeting 2
- Customer Meeting 3
- Customer Meeting 4
- Customer Meeting 5
- Milestone 1 Presentation Notes
- Milestone 2 Presentation Notes
- Milestone 3 Presentation Notes
Scenarios
- Scenario 1 for CMPE451:Milestone 1
- Scenario 2 for CMPE451:Milestone 1
- Scenario 1 for CMPE451:Milestone 2
- Scenario 2 for CMPE451:Milestone 2
- Scenario 3 for CMPE451:Milestone 2
- Scenario 1 for CMPE451:Final Milestone
- Scenario 2 for CMPE451:Final Milestone
- Scenario 1 for CMPE352
- Scenario 2 for CMPE352
- Scenario 3 for CMPE352