You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is created to design and implement a UML Sequence Diagram for our Affordable & Healthy Eating Hub platform. The diagram should illustrate the interactions between system components and users based on our written user scenarios. We will focus on the following key processes as shared by team members:
Cem: Login, Register, Rate Health Score (Dietitian)
Ali: Rate Taste/Difficulty Score (User), Post a Question, Filter Recipes
Selçuk: Delete a Comment, Like a Recipe, Follow/Unfollow User
This diagram will provide a clear, visual representation of these interactions over time, which will help us better understand and refine our platform's workflows.
📌 Subtasks:
Identify key system processes and interactions for visualization based on the written user scenarios:
Cem: Login, Register, Rate Health Score (Dietitian)
Ali: Rate Taste/Difficulty Score (User), Post a Question, Filter Recipes
Selçuk: Delete a Comment, Like a Recipe, Follow/Unfollow User
Draft initial sequence diagram sketches for the selected scenarios.
Refine the diagrams based on team feedback.
Finalize and add the sequence diagram(s) to the wiki.
✅ This issue follows the issue template rules to maintain consistency.
✅ The assignee(s) ensure this issue is clear, structured, and meets all must-have criteria.
✅ Open to feedback & improvements, because even the best code can get better!
💡 And remember: "It works on my machine" doesn’t mean it works for everyone, and "It’s not a bug, it’s a feature" only works if everyone agrees!
The text was updated successfully, but these errors were encountered:
🔍 Issue Description:
This issue is created to design and implement a UML Sequence Diagram for our Affordable & Healthy Eating Hub platform. The diagram should illustrate the interactions between system components and users based on our written user scenarios. We will focus on the following key processes as shared by team members:
This diagram will provide a clear, visual representation of these interactions over time, which will help us better understand and refine our platform's workflows.
📌 Subtasks:
📌 Expected Effort:
📌 Deadline:
📌 Reviewers:
📌 Reviewer Deadline:
⚡ Footer
✅ This issue follows the issue template rules to maintain consistency.
✅ The assignee(s) ensure this issue is clear, structured, and meets all must-have criteria.
✅ Open to feedback & improvements, because even the best code can get better!
💡 And remember: "It works on my machine" doesn’t mean it works for everyone, and "It’s not a bug, it’s a feature" only works if everyone agrees!
The text was updated successfully, but these errors were encountered: