Customer Meeting ‐ 17.03.2024 - bounswe/bounswe2024group12 GitHub Wiki

Meeting Details

#	Details	Responsible	Due Date	Issue
1	Adding Customer Meeting notes to Wiki.	Isil Su Karakuzu	14.03.2024 at 23.59	#73
2	Add answers to Elicitation Questions on wiki.	Isil Su Karakuzu	14.03.2024 at 23.59	#82
3	Updating the parts affected by the given feedback.	Everyone	14.03.2024 at 23.59	⬜️

Clarify the distinction between "shall" and "should" in requirements wording: "Shall" denotes mandatory actions, while "should" indicates actions that may be challenging but are not obligatory.
Exercise caution not to overcrowd features; keep them concise.
Specify which requirements correspond to each scenario; provide five scenarios. Ensure each scenario includes a basic image for both web and mobile platforms.
For RAM: Divide the team into three groups: frontend, backend, and mobile; consider a high-level approach and create a simple Gantt chart to be included within milestones; focus solely on implementation planning, including aspects related to software design as necessary.
Revise requirement wording to focus on "how" and "what" rather than describing UI interactions; eliminate general page tasks and ambiguous language; avoid vague expressions and use clear, concise language (e.g., avoid using "dynamically").
Remove features that do not enhance the application's depth to avoid unnecessary expansion.
Essential features such as email verification, password recovery, account deletion, and post deletion should be included. Ensure everyone reads and understands the Wikidata research.
Consider adding functionality such as liking reviews or bookmarking, but ensure the system does not become overly complex.
Liking comments in the project is not obligatory.