We build a use case diagram for my [first user story](https://git.cs.usask.ca/vrl968/cmpt370/-/wikis/Deliverable_1#user-story-1-3). This use case allows the user to leave or add a review on the website.
We build a use case diagram for my [first user story](https://git.cs.usask.ca/vrl968/cmpt370/-/wikis/Deliverable_1#user-story-1-3).
The primary actor is the user, and the secondary actor is the user data base (where all the data is saved). The actor's goal is to see and leave reviews.
**Summary**: This use case allows a user of the website to read, add, or edit a review on the website.
To leave a review, the actor has to sign in to their account, press the leave review button, leave a rating, a comment, and confirm the review. They can choose not to leave a comment.
**Actors**: The main actor is the website user, the secondary actor is the website data base.
After submitting the review, the rating of the item/user will be updated in the system, and the comment (if the user left one) will be added to the item posting/user profile.
**Version**: 1.2
**Person in Charge**: Hakeem Hannoon
**Preconditions**: None
The actor also would like to see the previous review history for the item/user.
After submitting the review, the rating of the item/user will be updated in the system, and the comment (if the user left one) will be added to the item posting/user profile.
