BACKEND Meeting Notes #1 12 10 2022 - bounswe/bounswe2022group7 GitHub Wiki

Meeting Information

Date: 12/10/2022
Time: 22:00
Online/Offline: Online
Location: Discord
Duration: 1 hour
Note Taker: Demet Yayla

Attendees

  • Cahid Arda Öz
  • Demet Yayla
  • Ali Can Milani
  • Musa Şimşek
  • Erim Erkin Doğan
  • Güney İzol
  • Aziza Mankenova
  • Atilla Türkmen
  • Can Atakan Uğur
  • Başak Önder
  • Sabri Mete Akyüz
  • Muhammet Ekrem Gezgen

Agenda

  • Discussing the fixation to be done on the UML Class Diagram
  • Finalizing the decisions about which language, framework, database to use for backend
  • Discussing what to write for this week's topic: Homepage.

Discussions

  • We chose MySQL for database.
  • We decided on some deletions and modifications on class diagram.
  • We decided on using Kotlin.
  • For HomePage, we decided which classes to implement.
  • We will do the project initialization on our local and dockerize it

Action Items

Item Responsible Person Due Date
Class diagram will be fixed according to Class Diagram Updates. Demet Yayla 15/10/2022 23.59
Event class is to be written. Demet Yayla 16/10/2022 23.59
ArtItem class is to be written. Demet Yayla 16/10/2022 23.59
PhysicalExhibition class is to be written. Demet Yayla 16/10/2022 23.59
OnlineGallery class is to be written. Başak Önder 18/10/2022 23.59
ArtItemInfo class is to be written. Başak Önder 18/10/2022 23.59
EventInfo class is to be written. 16/10/2022 23.59
Comment class is to be written. 16/10/2022 23.59
CommentReport is to be written 16/10/2022 23.59
Backend code initialization is to be done. Sabri Mete Akyüz 14/10/2022 23.59
Dockerization of backend. Başak Önder 18/10/2022 23.59
Set the database and do the dockerization for it. Başak Önder 18/10/2022 23.59

Class Diagram Updates:

  • Rename ForumPost as Post
  • Remove DiscussionForumPage
  • Remove ReplyThread and reorganize the dangling connections.

Conclusions

  • The updates for the communication plan are done.
  • The sub-teams are created for the development process.
  • Tasks for the repository revision task are divided between the team.