-
Notifications
You must be signed in to change notification settings - Fork 3
Customer Meeting 2
-
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 requirements, and asking questions about unclear parts of the project.
- A team discussion to review requirements until the customer came.
- Getting feedbacks about requirements.
- Asking some questions about the project.
- Review on the requirements:
- Some of the chatbot requirements (1.2.4.2.1, 1.2.4.2.6) assumes chatbot will have NLP and relearning, which we decide the opposite and have a simple decision tree.
- For example, "chatbot will propose questions to find out what is the discomfort registered user has, and ask follow up questions until it reaches a leaf node/answer."
- It will ask questions to the user, which they will choose their response via clicking on the given answers, and new questions comes until an answer is reached.
- Answer will be tags, which the user can look under for the posts that has that tags. Also, suggested posts or articles in the form of links to them in the application.
- Appropriate naming complying to the glossary is a needed review.
- Requirements were presented and feedbacks were taken.
- Some unclear parts were asked
-
You can choose not to implement a messaging system if you think that it is not appropriate for this system.
-
What is notification preference? Elaborate more.
-
Divide requirements 1.2.1.1.8, 1.2.1.1.11. They include too much information.
-
Make clear what will be the sorting mechanism of comments in the Forum. Will you use date or number of upvotes?
-
Make the terms; User, Registered User, Member more clear in the requirements.
-
In requirement 1.1.1.1.5 change the requirement of sign-up with real names in terms of members. It is not consistent with the anonymousness property.
-
Elaborate more that the terms synonyms and similar words in the search requirements.
-
Should we think about a mechanism of adding new admins to the system? -
- Answer: Generally, there is only one admin in this kind of systems. Maybe a super admin can give admin authorization to other users. Maybe you can think about adding some moderators to the categories. But it is up to you.
-
We thought that we can use chatbot for directing users to some labels or categories by asking some questions and getting some selections among some options from the users. What do you think?
- Answer: That kind of an implementation would be nice.
🏠 Homepage
- Alper Canberk Balcı
- Baver Bengin Beştaş
- Burak Mert
- Halil Burak Pala
- Kardelen Demiral
- Sinan Kerem Gündüz
- Yavuz Samet Topçuoğlu
- Mehmet Emre Akbulut
- Oğuzhan Demirel
- Engin Oğuzhan Şenol
- Irfan Bozkurt
- Ozan Kılıç
Meeting Notes From CMPE352
Meeting Notes From CMPE451
- Meeting 13.1
- Meeting 14.1
- Meeting 15.1
- Meeting 16.1
- Meeting 18.1
- Meeting 19.1
- Meeting 20.1
- Meeting 21.1
- Meeting 23.1
- Meeting 24.1
Backend Team Meetings
Frontend Team Meetings
Mobile Team Meetings
- Customer Meeting 1
- Customer Meeting 2
- Customer Meeting 3
- Customer Meeting 4
- Customer Meeting 5
- Milestone 1 Presentation Notes
- Milestone 2 Presentation Notes
- Milestone 3 Presentation Notes
Scenarios
- Scenario 1 for CMPE451:Milestone 1
- Scenario 2 for CMPE451:Milestone 1
- Scenario 1 for CMPE451:Milestone 2
- Scenario 2 for CMPE451:Milestone 2
- Scenario 3 for CMPE451:Milestone 2
- Scenario 1 for CMPE451:Final Milestone
- Scenario 2 for CMPE451:Final Milestone
- Scenario 1 for CMPE352
- Scenario 2 for CMPE352
- Scenario 3 for CMPE352