Deliverable_2.md

@@ -17,20 +17,24 @@
 ## Matt:
 
 ### Individual Class Diagram
+
 ![UML_class](uploads/6890c2a019f5f6d1f83af2de6d351461/UML_class.jpeg)
 
 ### UML Use Case Diagram
-![Use_case_diagram_](uploads/144a7d4836e862a0ce8116f2062ca650/Use_case_diagram_.jpeg)
+
+![Use_case_diagram\_](uploads/144a7d4836e862a0ce8116f2062ca650/Use_case_diagram_.jpeg)
 
 ### Storyboards
+
 ![Storyboard](uploads/fa2dbe06e79b99a91f1ade94b3ae705f/Storyboard.jpg)
 
 ### Sequence Diagram
+
 ![Sequence_diagram](uploads/4145f41142c7f16f7118eea88e986821/Sequence_diagram.jpeg)
 
 ### Activity Diagram
-![Activity_diagram](uploads/0887f1d9ea1a2d85f37e9e14de2d3a2a/Activity_diagram.jpeg)
 
+![Activity_diagram](uploads/0887f1d9ea1a2d85f37e9e14de2d3a2a/Activity_diagram.jpeg)
 
 ## Peter:
 
@@ -38,6 +42,41 @@
 
 ### UML Use Case Diagram
 
+## **Actors**
+
+Primary Actor
+
+* Tool Renter
+
+Secondary Actors
+
+* Third-Party Payment System
+* Tool Rental Platform
+* Notification System
+
+## **Use Cases**
+
+Reserve Tool
+
+* View Tool Details
+* Select Time Slot
+* Process Payment
+
+\
+Receive Notifications
+
+Manage Reservations
+
+* View Reservations
+* Modify Reservation
+* Cancel Reservation
+
+## **Diagram Link**
+
+[Lucidchart document](https://lucid.app/lucidchart/a22954fb-934c-4be2-bb23-e5e90f09e18e/edit?viewport_loc=-50%2C187%2C2618%2C1127%2C.Q4MUjXso07N&invitationId=inv_44c23267-193b-4931-989e-c854336feff9)
+
+<span dir="">![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXcn2CuIXC8mx74a1COV8mtiYMRHAYCWF30iRoh50fKUSrZuieEOEZeTyfqTzt9rU2T-zwnO5yQoMA7QahN9KnGbG0whOs9-jdnJXPC7QrT4wzEcQHwcOdqcSKoZ4D1hv9Vqaf3gQA?key=j3RL-QDGquSDnMsiC5thvPsC){width=886 height=591}</span>
+
 ### Storyboards
 
 ### Sequence Diagram
@@ -146,7 +185,6 @@ We start with the class diagram for a review system. We have three classes, the
 
 ![Class_diagram](uploads/0da306b6700a856cb297035b439b77ab/Class_diagram.png)
 
-
 ### UML Use Case Diagram
 
 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).
@@ -199,7 +237,7 @@ Now we turn to another acceptance test, where the user is able to **see their pr
 
 ### Sequence Diagram
 
-![sequance_diagram](uploads/6d9cca02c7eba685ddc202129f89f1e2/image.png){width=454 height=627}
+![sequance_diagram](uploads/6d9cca02c7eba685ddc202129f89f1e2/image.png){width="454" height="627"}
 
 ### Activity Diagram
 
@@ -219,8 +257,8 @@ We create our activity diagram for the [second user story](https://git.cs.usask.
 * Merged UML class diagrams into a single UML class diagram for the team and designed the SW architecture diagram.
 
 ### Peter:
-* 16.66%
 
+* 16.66%
 
 ### Charles:
 
@@ -233,7 +271,6 @@ We create our activity diagram for the [second user story](https://git.cs.usask.
 
 * 16.66%
 
-
 ### Haidari:
 
 * 16.66%
@@ -245,7 +282,6 @@ We create our activity diagram for the [second user story](https://git.cs.usask.
 * Created individual diagrams, including activity, component, sequence, and UML class diagrams.
 * Designed the front-end for the review feature.
 
-
 ## Action Plan
 
 ### Sprint 1: Reservations