Meeting Notes #8 05.04.2022

Date: 05 April 2022
Location: Zoom
Time: 21:00 - 23:30
Note Taker: Salim Kemal Tirit

Participants:

• Arif Akbaba
• Mehmet Gökberk Arslan
• Bilal Aytekin
• Nurlan Dadashov
• Hatice Şule Erkul
• Kadir Ersoy
• Ahmet Kudu
• Muhammet Şen
• Bengisu Takkin
• Burak Yılmaz
• Salim Kemal Tirit
• Mertcan Özkan

Agenda:

• Reviewing the action items of the last meeting. (meeting notes)
• Reviewing class diagrams, their coherence, and related issues in detail.
• Connecting class diagrams.
• Determining the necessary actions for sequence diagrams.

Discussion Notes

• First, we talked about some topics that are urgent or complicated.
• Feedback Class:
  • First, we reviewed the class diagram of the Feedback class.
  • Issue #96 Resolving the Feedback/Ratings is reviewed.
  • We clarified the feedback mechanism. The last decision is: The Feedback mechanism is directly related to the course. This feedback will be a text. Also, each course will have a rating out of five. The rating of the lecturer will be calculated as the average rating of the courses s/he is lecturing. The number of participants in a course will not be significant.
  • A requirement for this feedback and rating system will be written.
  • Feedback will be added to the Attend Course part of the use case diagram.
  • Feedback will be stored in the Course class along with the rating.
  • There will be only a rating on the profile page of the Lecturer.
• CourseContent Class:
  • There will be a CourseContent class which will be connected to the Chapter class.
  • Its name was assumed to be Content while creating the Chapter class so it will be changed to CourseContent.
• Use Case Diagram - Manage Content:
  • We talked about the discussion, ask questions, and view questions parts.
  • We decided this part is complicated and needs to be simplified.
• After the discussions above we started connecting the class diagrams. We decided to proceed systematically starting with User and as we connected new classes we reviewed that class and also the issue about that class.
• Communication between classes and their relations are resolved.
• Private and Public are moved to the Personal Information class.
• We talked about the parameters of the functions in every class. They need to be in the format of function(<argument name>:<argument type>) -> <return value> as stated in the previous meeting notes. Some of them were wrong we quickly fixed them.
• We discussed if there needs to be a Following Request when a user wants to follow another user. We decided to postpone this topic to another meeting.
• We decided to add a field indicating that the user confirmed his/her email.
• Personal Information class got connected to the User class. Then the related issue #92 was reviewed. The connection was done as one to one.
• We decided the knowledge field in the Personal Information class will be a list of strings and it will also show the interests of the user.
• Personal rating was defined as an integer we decided that it needs to be stored as a double.
• We discussed if the functions defined as void actually need to return a boolean. From now on most of the void functions will return a boolean value indicating the success of the operation.
• We decided that classes need a constructor and if there is a function doing the job of the constructor it needs to be in the format of a constructor.
• User and Enrollment classes got connected. The connection was done as one to many. Related issue got reviewed.
• Course and Enrollment classes got connected. Related issue got reviewed.
• In the course class there was an Enrolled Users list it is changed to the Enrollments list. There was also a Participants field it is deleted.
• Chapter class and related issue reviewed.
• Chapter and Enrollment classes got connected since the badges will be stored in the Enrollment class.
• User and Course classes are connected directly because if the user is the lecturer of the class s/he needs to have direct access to the content of the course.
• There will be a function that is going to track the progress of the user in the Enrollment class.
• CourseContent class got connected to Chapter class. They will be stored in a list.
• Badge class got connected to User, Chapter, and Course classes.
• After the user finishes a chapter badge information will be checked and for every
• In our slack group (different than the one with the teacher) under the questions channel our questions that are going to be asked to the customer are gathered.
• Other classes are reviewed and their related issues are connected.

Action Items

Action	Assignee	Deadline	Issues
Designing The Sequence Diagrams	Each member will do the one with their related use cases.	08.04.2022	#101 #102 #105 #107 #109 #112 #116 #117 #119 #119 #120 #124 #125 #129
Adding diagrams to the wiki page and to the side bar.	Kadir Ersoy	08.04.2022	---
Doing a grammar check over the Requirements, doing a glossary update including the definition of banning.	Şule Erkul	08.04.2022	#73
Writing the requirements of feedback and rating mechanisms.	Mertcan Özkan	08.04.2022	#96
Designing Feedback class' class diagram.	Muhammet Şen	08.04.2022	#113
Adding Giving Feedback to Attend Course part in use case diagram.	Şule Erkul	08.04.2022	#71
Designing CourseContent class' class diagram.	Şule Erkul	08.04.2022	#114
Rearranging the discussion part in use case diagram	Ahmet Kudu	08.04.2022	#93