• Customer: Burak Suyunu

• Alper Canberk Balcı

• Halil Burak Pala

• Mehmet Emre Akbulut

• Sinan Kerem Gündüz

• Kardelen Demiral

• Yavuz Samet Topçuoğlu

• Mehmet Akif Yılmaz

• Burak Mert

• Engin Oğuzhan Şenol

• Baver Bengin Beştaş

• Oğuzhan Demirel

• Buse Tolunay

• Meeting for getting feedback from TA about UML Diagrams and Requirements.

• Getting feedbacks about requirements.
• Getting feedbacks about UML Diagrams.

• Some feedback about requirements were taken:
• Some feedback about UML Diagrams were taken.

We asked about our work and Customer made some observations and suggested feedbacks.

• Some requirements elements in Admin, Sorting, and Search sub sections need to be carried into User Requirements.

• Search <-> Sort Results: include/extend, he is not sure. Customer took note of it.
• Extension or generealization for Sort Results <- Sort Discussion Threads/Sort Articles, he is not sure.

• Chatbot: Remove Node Class and make this part more abstract.
• Chatbot may deepen the query or it may return a solution(suggestions), so the mechanism is simple and remaining is database processes.

• Remove UI Class
  • We removed them.
• Make sure the direction of the arrows leading into classes is correct.
  • We pretty much are. Functions of a class goes into the class.
• You can add constructors to Class Diagrams and write those functions on arrows instead of <>
  • We added constructors with void return.
• Functions that go into DB may be in classes in Class Diagram.
  • We used save, update etc. according to the answers of Prof. Uskudarli in Slack.
• If a function returns void (or not have return) you can add boolean return, and return True/False in Sequence Diagrams.