Meeting Notes #7 04.04.2022

Date: 04 April 2022
Location: Zoom
Time: 21.00 - 01:00 (the next day)
Note Taker: Muhammet Şen

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

• Status of the requirements, updates over the last week
• Reviewing use case diagrams
• Reviewing and checking coherence of class diagrams

Discussion Notes

• We had several questions and proposals regarding the user requirements under #63.
  • We talked about what default ranking strategy for courses, notes, and discussuons should be. We decided that newest first will be our default ranking.
  • We clarified the definition of topic in our platform. Courses will have topic fields provided by the lecturer. Moreover, users will have interests and topics they want to learn more about. We can use this relationship to improve our recommendation system. A few examples for topic: Computer Vision, Psychology, Web Development.
  • We must add a requirement for logging out to user requirements.
  • We can improve our requirements by providing references between different items.
• Progress Tracking
  • We will track a user's progress in a course by using the chapters provided by the course lecturer. Course lecturer will create chapters while creating content for the course. When user completes a chapter, Enrollment class will be aware of it and set progress accordingly.
  • Tracking progress of a user is integrated with Achievement class. Hence, we need to make sure they do not overlap.
• Personal Information Class
  • Users should be able to give feedback to a course they attend to. Moreover, they may want to give feedback to the course lecturer instead of the course. Hence we need to add requirements, design diagrams for feedbacks. A feedback must have an owner, content, and targeted course/user.
• Course Class
  • We decided that notes should live under Enrollment class instead of Course class. However, courses will have public notes that can be viewed by anyone.
  • Course requirements can be a list of labels and topics with addition to a text written by the lecturer.
  • Lecturer will be able to create custom badges for the course. They will be rewarded to users as they complete chapters.
• Discussion
  • Comments of a discussion will live under that discussion. Discussion will have a list of comment ids.
• We must add corresponding requirements to each use case diagram
• We need a class to represent relationship between a course and course lecturer. It will be similar to how Enrollment class behave.
• Use case diagram for creating content will slightly change. A course lecturer shall be able to create a chapter and add the content to it. Moreiver, lecturer may add badges to a specific chapter.
• Use case diagram for viewing and enrolling to a course will be improved by changing the order of events. A user who is not enrolled to a course will be able to see course description and public notes prepared by other users.
• There will be two types of events as public and private. When a course lecturer creates an event, there will be an option for making the event public or private. If an event is private, lecturer will provide a list of possible participants and only the users in that list will be able to join to the event.
• We will prepare a use case diagram for viewing the results of a poll
• We have decided that notes can be public as well as private.
• We will prepare admin user requirements and diagrams. Admin will be able to delete comments, delete courses and specific content of a course, and ban a user.
• We have agreed on some conventions in order to have consistency between diagrams.
  • We will show list with List<>. For example, list of strings will be shown with List<String> and list of user ids will be shown with List<User.user_id>
  • We will use snake case notation in classes' fields.
    user_id: UID
linked_notes: List<UID>
  • We will use camel case notation in classes' methods. Every argument and method must have a type.
    linkAnotherNote(note_id: UID)-> String
• We will prepare requirements for comments.
• Enrollment class will store the process of a user.
• User shall be able to add files while creating a note.
• Notes will be accessible by visiting the course page.
• We could not fully understand how we are going to use geolocation in our project. We will ask to customer in the next meeting.
• We want to understand the difference between polls and quizes. It would be more clear if they were two seperate classes. We will ask to customer in the next meeting.
• User class shall contain the following and followed users.

Action Items

Action	Assignee	Deadline	Issue
Overlap of Enrollment and Achievements Classes	Şule Erkul and Muhammet Şen	05.04.2022	#97
Resolving the Feedback/Ratings	Mertcan Özkan	05.04.2022	#96
Adding corresponding requirements to use case issues	Everyone	06.04.2022	#108
Class diagram for Feedback	Muhammet Şen	06.04.2022	#113
Use case diagram for Feedback	Şule Erkul	06.04.2022	(didn't create a new one) #71
Adding Chapter to both glossary and requirements	Şule Erkul	06.04.2022	#73
Class diagram for Chapter	Salim Kemal Tirit	06.04.2022	#111
Use case diagram for viewing the results of a poll	Burak Yılmaz	06.04.2022	(didn't create a new one) #66
Adding admin user to glossary and improving requirements	Şule Erkul	06.04.2022	#73
Use case diagram for admin user	Burak Yılmaz	06.04.2022	#106
Adding comments to glossary and improving requirements	Ahmet Kudu	06.04.2022	#110
Adding logout requirements	Salim Kemal Tirit, Bengisu Takkin	06.04.2022	#63