Deliverable_2.md

@@ -4,6 +4,16 @@
 
 ## UML Use Case Diagram
 
+### Peter 
+
+### Charles
+
+### Heer
+
+### Matt
+
+### Haidari
+
 ### 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).
@@ -45,16 +55,6 @@ Scenario example: Leaving, deleting or editing a review on a tool
 
 ![Use_Case_Diagram](uploads/fed444af10b4b800c844c7e8e5fdfcc4/Use_Case_Diagram.png)
 
-### Peter 
-
-### Charles
-
-### Heer
-
-### Matt
-
-### Haidari
-
 ## UML Class Diagram
 
 ## Design Storyboard
@@ -90,3 +90,18 @@ Now we turn to another acceptance test, where the user is able to **see their pr
 
 ## Activity Diagram
 
+### Peter 
+
+### Charles
+
+### Heer
+
+### Matt
+
+### Haidari
+
+### Hakeem
+
+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