-
Notifications
You must be signed in to change notification settings - Fork 3
Customer Meeting 1
-
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 scenarios 1, 2, 3 and requirements, and asking questions about unclear parts of the project.
- Getting feedbacks about scenarios and mockups
- Getting feedbacks about requirements
- Asking some questions about the project
- Scenarios and mockups were presented and feedbacks were taken.
- Requirements were presented and feedbacks were taken.
- Some unclear parts were asked
-
You should consider the case where a patient does not know under which category should he/she post his/her post. Solutions:
- There can be some helper means.
- Can be solved by tags.
- Selecting more than 1 categories can be implemented.
- There can be a general category which contains these kind of posts.
- Doctors can change the category of a post.
-
Tag change of a post by a doctor can be shown in the Scenario 2. (No need to add this in mockups.)
-
You should consider the case where there is no enough number of doctors in the system. In such a case who will write articles in the Articles section? Solutions:
- Creating articles in the Articles section should be done also by users other than doctors:
- Number of Upvotes-Downvotes can be an indicator of the quality of an article created by an user.
- There can be a verification system in which doctors verify other users' articles. Users who get some number of verifications can also add articles to Articles section without verification.
-
You can consider adding a personalized homepage. There can be some recommendations, or users can be able to follow some tags or categories.
-
Should activity history be private (can be seen by user himself only)?
- Answer: This is up to you.
-
We think that a messaging system is not appropriate for this type of platform since there can be promotion of illegal drugs etc. What do you think? Is implementing a messaging system an obligation?
- Answer: Your reasoning is logical. I will ask this to Prof. Uskudarlı.
-
Should we keep separate sections for Listing and Sorting Requirements?
- Answer: You can. This can provide you ease while coding.
-
What can we do about chatbot? We are still not sure about the functionality of it.
- Answer: You can use it for advanced search in the website, or you can use it for informing users.
-
Is documentation of our requirements correct? Should we organize this page according to Software Requirements Specification?
- Answer: There is no problem with current organization. Later maybe Prof. Uskudarlı can give you an assignment about SRS.
-
We think that users can add some public personal info like age, height etc. Is there any problem with that?
- Answer: No, on the contrary it is a good idea.
🏠 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