Meeting #5 (13.03.2019)

1. Details

• Location: Cmpe Building B5
• Date: 13 March 2019
• Time: 18:00 - 19:30

Attendees

• Ali Meriç Deşer
• Yusuf Mert Bila
• Furkan Kadıoğlu
• Veli Can Ünal
• Mahmut Uzunpostalcı
• Hasan Öztürk
• Abdullah Yıldız
• Selamettin Dirik
• Meltem Suiçmez
• Abdullah Enes Öncü

2. Agenda

• 2.1. Reviewing our feedback, small discussion about mockups and what happened in the ps.
• 2.2. Discussing which technologies to use in the project, everyone will contribute with what they think would be best.
• 2.3. Going over the class diagram, one volunteer should explain what is done so far and what is left.
• 2.4. Clarifying discussions in the class diagram. Assigning members to finish the class diagram.
• 2.5. Coming up with the scenarios that are going to be shown in sequence diagrams. Assigning members to them.

3. Discussion

• 3.1. Went over our mockups feedback one by one and assigned members according to the modifications to be made. We opened our mockups page and pointed our what will be modified. Opened a related issue about it to track the progress.
• 3.2. Mert explained AWS amplify to the group, how we can use it and what attributes are the good about it. He also mentioned that Amazon Cognito would be good to use. For back-end our two options are node.js and django; for front-end the are angular, vue and react; for android koitlin is decided for now. Selamettin explained that react is good for interchanging platforms. Veli mentioned that Ruby on Rails may be considered for backend.
• 3.3. Mert showed on the board what has achieved yet at the class diagram to inform every group member. He explained every class' purpose, fields and methods. Writing and Annotations classes were undetermined. Enes suggested we should have a draft essay class. Furkan suggested isReviewCompleted field in Writing class can be edited to enum to represent other statuses. About essay-annotation subject, we decided that if a learner wants to send an edited essay according to the expert's feedback, user would have to send another writing request to that expert. Only one essay text will be shown in one writing class. We will use color codes when we edit the class diagram. Green for when one class is finished&open for review, blue when it is being edited, white when it is not finished and orange when it should be discussed with the group.
• 3.4. We watched an introductory video about sequence diagrams. https://www.youtube.com/watch?v=pCK6prSq8aw We learned the conventions and how to make a sequence diagram. We found 8 key subjects:

1. Solve Exercise
2. View Profile & Rating
3. Chat
4. Search
5. Report w/Admin
6. Writing Divions are made and represented in the actions. All groups will meet and do their job.

4. Actions

ID	Who	What	Deadline
1.	Enes, Furkan, Hasan	Working on class diagram	14.03.19 13.00
2.	Mert, Abdullah, Selamettin	Working on sequence diagram(Writing)	14.03.19 15.00
3.	Abdullah, Enes	Working on sequence diagram(Chat)	15.03.19 13.00
4.	Mahmut, Veli	Working on sequence diagram(Search)	16.03.19 21.00
5.	Meriç, Furkan	Working on sequence diagram(Solve exercise)	15.03.19 13.00
6.	Meltem, Mahmut, Veli	Working on sequence diagram(Report)	16.03.19 19.00
7.	Mert, Meltem	Working on sequence diagram(View Profile&Rate)	15.03.19 12.00
8.	Meriç	Updating Requirements	16.03.19 midnight