Meeting Notes #14 08.04.2023

📅 Date: 08.04.2023
🗺️ Location: Google Meet
🕐 Time: 21.00 - 00.30
✏️ Note Taker: Erkam Kavak

👥 Participants:

• Ahmet Kudu
• Ayberk Erdem
• Beyzanur Bektan
• Emre Türker
• Erkam Kavak
• Hüseyin Çivi
• Melih Portakal
• Ömer Akalın
• Ömer Bahadıroğlu

Agenda:

• Revision of the sequence diagrams which are assigned on the previous meeting.
• Identifying all the shortcomings so far for the project.
• Preparing for the milestone report and assigning tasks to everyone for the report.

Discussion Notes

• This meeting was a daily meeting for the part up to the milestone task.
• In the previous meeting, groups were formed to create sequence diagrams. In this meeting, the approaches were discussed.
• Huzeyfe Bahadıroglu raised the issue of whether we should limit ourselves to the class diagram when creating sequence diagrams and expressed concern that if we were to limit ourselves to the class diagram, the sequence diagrams would be overly simplistic in their representations. After consulting with the assistant, it was decided that the sequence diagram should not be limited by the class diagram.
• Melih brought up the question of whether annotations and tags should be created before or after creating the content (posts, events, LFG). Specifically, the question was whether, in cases where annotations and tags are added when creating new content, they should be saved to the database before or after the content itself is saved. The majority agreed that it would be more logical to create the content first, and then create the annotations and tags afterwards, and this decision was made.
• Since there were not much time left for the deadline of the milestone report, everyone left to more of their own initiative for the sequence diagram part.
• Ahmet Kudu will take over the tasks of joining groups and participating in events instead of Sena Ozpınar. Sena Ozpınar will work on the use case and sequence diagram sections of the account.
• After revising the sequence diagrams, we began preparing the milestone report section. Here, the required tasks for the report and how to accomplish them were determined. The required tasks are assigned to group members.
• It was decided not to carry out the user scenario part until deadline since it was not mentioned that it needed to be done in the initial stages, and now there is not enough time to complete.
• We discussed how to prepare the project plan, RAM, and communication plan sections in the deliverables. Excel files were created for the project plan and RAM sections. Huzeyfe Bahadıroglu created the communication plan.
  • Excel file link for the project plan section
  • Excel file link for the RAM section
• As it was believed that it would facilitate writing the milestone report, all the shortcomings in the project so far were identified and collected in a Google Drive document. These shortcomings were then assigned to group members.

Action Items

Action	Assignee	Deadline	Issue
Adding meeting notes #14	Erkam Kavak	09/04/2023	#93
Preparing executive summary for the milestone report	Emre Turker	09/04/2023	#104
Preparing list and status of deliverables for the milestone report(part D1-D2)	Ömer Bahadıroglu	09/04/2023	#95
Preparing list and status of deliverables for the milestone report(part D3-D4-D5)	Melih Portakal	09/04/2023	#92
Preparing evaluation of the status of deliverables for the milestone report	Huseyin Civi	09/04/2023	#103
Preparing evaluation of tools and processes for the milestone report	Omer Talip Akalin	09/04/2023	#102
Resolving the shortcomings for the requirements part	Ahmet Kudu	09/04/2023	#109
Organizing the sidebar section and adding missing items	Beyzanur Bektan	09/04/2023	Related Issue
Organizing the mockups and completing missing parts	Ayberk Erdem	09/04/2023	#87
Creating the Use Case Diagram for the Account	Ayberk Erdem	09/04/2023	#96