Deliverable_2.md

@@ -14,6 +14,37 @@
 
 ### Haidari
 
+```plantuml
+@startuml
+actor User
+actor Database
+
+rectangle ToolLoop {
+    usecase "Register user" as UC1
+    usecase "View profile" as UC2
+    usecase "Edit profile info" as UC3
+    usecase "Upload own photos" as UC4
+    usecase "Update Profile" as UC5
+    usecase "Delete profile" as UC6
+}
+
+User -- UC1 : First time user
+User -- UC2 : Registered user
+User -- UC3
+User -- UC4
+User -- UC5
+User -- UC6
+
+UC2 ..|> UC3 : <include>
+
+UC3 -- Database
+UC4 -- Database
+UC5 -- Database
+UC6 -- Database
+
+@enduml
+```
+
 ### Hakeem Hannoon
 
 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).
@@ -28,7 +59,6 @@ We build a use case diagram for my [first user story](https://git.cs.usask.ca/vr
 
 **Preconditions**: The character limit for a review is 250.
 
-
 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.
 
 Scenario example: Leaving, deleting or editing a review on a tool
@@ -73,16 +103,15 @@ Scenario example: Leaving, deleting or editing a review on a tool
 
 Now we design the story board for our [first user story](https://git.cs.usask.ca/vrl968/cmpt370/-/wikis/Deliverable_1#user-story-1-3). We start **displaying the reviews on a given product** with the option of adding or deleting an existing review.
 
-![image](uploads/f2f59bf511e1ada90852337e59667e84/image.png){width=1135 height=826}
+![image](uploads/f2f59bf511e1ada90852337e59667e84/image.png){width="1135" height="826"}
 
 The next acceptance test is when someone asks the user to borrow their tool. In this case the user will have the option of **checking the profile of the borrower** asking to rent the tool and display previous reviews of the other user.
 
-![image](uploads/9aed63bb5bf1ccf88ec17b92e54ab812/image.png){width=1137 height=415}
+![image](uploads/9aed63bb5bf1ccf88ec17b92e54ab812/image.png){width="1137" height="415"}
 
 Now we turn to another acceptance test, where the user is able to **see their previous rentals and add a review to them**.
 
-![image](uploads/896eb10846d9de46d72ec7b0853470d6/image.png){width=1141 height=839}
-
+![image](uploads/896eb10846d9de46d72ec7b0853470d6/image.png){width="1141" height="839"}
 
 ## Software Architecture
 
@@ -104,4 +133,4 @@ Now we turn to another acceptance test, where the user is able to **see their pr
 
 We create our activity diagram for the [second user story](https://git.cs.usask.ca/vrl968/cmpt370/-/wikis/Deliverable_1#user-story-2-3). Here the user goes through the process of reporting an item or another user in the website. The user has multiple options for the reason of the report, and the admin has options to take action based on the total number of reportings. The user can also submit multiple reports for each item/user.
 
-![Activity_diagram](uploads/f29c7984d61ecb0c7e94e7a730ec6da3/Activity_diagram.png){width=450 height=1944}
\ No newline at end of file
+![Activity_diagram](uploads/f29c7984d61ecb0c7e94e7a730ec6da3/Activity_diagram.png){width="450" height="1944"}
\ No newline at end of file