Skip to content

8th Meeting 25.11.2020

berkayalkan edited this page Dec 15, 2020 · 2 revisions

Time & Location

  • November 25th 2020, 21:00
  • Zoom

Attendees

  • Alperen Bağ
  • Berkay Alkan
  • Berke Can Gürer
  • Burak Çuhadar
  • Çağrı Çiftçi
  • Emre Girgin
  • Eylül Yalçınkaya
  • Koray Çetin
  • Mehmet Erdinç Oğuz
  • Meriç Üngör
  • Muhammed Olcayto Türker
  • Veli Can Ünal

Agenda

  1. We will talk about the tasks of milestone 1.

Discussion

  1. Table of content.
  2. Executive Summary: Summary of project status and any changes that are planned for moving forward.
  3. List and status of deliverables.
  4. Evaluation of the status of deliverables and their impact on the plan.
  5. A summary of coding work done by each team member (in tabular format).
  6. A detailed explanation of the challenges you met during the deployment, dockerizing, and CI/CD processes.
  7. Requirements. You should highlight and reason all changes that you have done in the CMPE451 semester.
  8. Design documents. You should highlight and reason all changes that you have done in the CMPE451 semester.
  9. API documentation (Do not just put the link to your documentation. You need to document within the report.).
  10. Project plan (in tabular format; you may omit Gantt timelines and display dates/durations/assignees/predecessors only as a text for readability. Unreadable plans will NOT be graded.).
  11. User scenarios you presented during the milestone presentation.
  12. Issues will be inspected online and will not be in the delivered report.
  13. Meetings will be inspected online and will not be in the delivered report.
  14. The wiki page will be inspected online and will not be in the delivered report (don't forget to keep your Wiki page up to date). Note that we are expecting every available information regarding your project available on your wiki page.
  15. The code will be inspected online and will not be in the delivered report. However, the code structure and group process should be documented, for example, if each feature is a branch and what are the branches, how are pull requests used, etc.
  16. Evaluation of tools and managing the project. This is a lesson learned from the project development decisions made so far. Tools are for planning, IDE, frameworks, and everything. The management is the process used by the team, including how the tools are being effectively utilized. If there are some aspects that are not working out, what kind of changes are planned.
  17. Assessment of the customer presentation. What did you learn from your interaction about the status and direction of your project? Also, did you learn anything about presenting? Difficulties? What went well, what needs improvement for next time.

Action Items

Task No. Person Task Deadline Completion time
1 Mehmet Erdinc Oguz Table of content. 29.11.2020 [email protected]
2 Eylül Yalçınkaya Executive Summary: Summary of project status and any changes that are planned for moving forward. 29.11.2020 [email protected]
3 Meriç Üngör, Mehmet Erdinç Oğuz, Emre Girgin List and status of deliverables 29.11.2020 [email protected]
4 Meriç Üngör, Mehmet Erdinç Oğuz, Emre Girgin Evaluation of the status of deliverables and their impact on the plan 29.11.2020 [email protected]
5 Everyone A summary of coding work done by each team member (in tabular format) 29.11.2020 [email protected]
6 Meriç Üngör, Mehmet Erdinç Oğuz A detailed explanation of the challenges you met during the deployment, dockerizing, and CI/CD processes. 29.11.2020 [email protected]
7 Emre Girgin Requirements. You should highlight and reason all changes that you have done in the CMPE451 semester. 29.11.2020 [email protected]
8 Çağrı Çiftçi,Muhammed Olcayto Türker, Koray Çetin Design documents. You should highlight and reason all changes that you have done in the CMPE451 semester 29.11.2020 [email protected]
9 Muhammed Olcayto Türker, Koray Çetin API documentation (Do not just put the link to your documentation. You need to document within the report.) 29.11.2020 [email protected]
10 Mehmet Erdinç Oğuz Project plan (in tabular format; you may omit Gantt timelines and display dates/durations/assignees/predecessors only as a text for readability. Unreadable plans will NOT be graded.). 29.11.2020 [email protected]
11 Burak Çuhadar,Alperen Bağ User scenarios you presented during the milestone presentation. 29.11.2020 [email protected] 28.11.2020 [email protected]
12 Çağrı Çiftçi,Eylül Yalçınkaya,Veli Can Ünal The code will be inspected online and will not be in the delivered report. However, the code structure and group process should be documented, for example, if each feature is a branch and what are the branches, how are pull requests used, etc 29.11.2020 [email protected] 29.11.2020 [email protected]
13 Meriç Üngör, Berkay Alkan, Veli Can Ünal Evaluation of tools and managing the project. This is a lesson learned from the project development decisions made so far. Tools are for planning, IDE, frameworks, and everything. The management is the process used by the team, including how the tools are being effectively utilized. If there are some aspects that are not working out, what kind of changes are planned. 29.11.2020 [email protected] 29.11.2020 [email protected]
14 Alperen Bağ, Burak Çuhadar Assessment of the customer presentation. What did you learn from your interaction about the status and direction of your project? Also, did you learn anything about presenting? Difficulties? What went well, what needs improvement for next time. 29.11.2020 [email protected] 28.11.2020 [email protected]

🏠 Home

💻 The Project


👥 Group Members

--- Former ---


📜 Manuals


📜 Milestone Reports


🔬 Research


📜 Meeting Notes

--- CMPE 451 ---

Group Meetings

Backend Meetings

Frontend Meetings

Android Meetings

--- CMPE 352 ---


Clone this wiki locally