Changes

Page history
Uploading plantUML code for my use case diagram authored by Haidari Alhaidari (vrl968)'s avatar Haidari Alhaidari (vrl968)
Hide whitespace changes
Inline Side-by-side
Deliverable_2.md
View page @ ff11dc88
...@@ -4,7 +4,7 @@ ...@@ -4,7 +4,7 @@
## UML Use Case Diagram ## UML Use Case Diagram
### Peter ### Peter
### Charles ### Charles
...@@ -14,6 +14,37 @@ ...@@ -14,6 +14,37 @@
### Haidari ### 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 ### 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). 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,20 +59,19 @@ We build a use case diagram for my [first user story](https://git.cs.usask.ca/vr ...@@ -28,20 +59,19 @@ 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. **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. 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 Scenario example: Leaving, deleting or editing a review on a tool
1. User opens the website login page 1. User opens the website login page
2. User enters their username and password 2. User enters their username and password
3. System compares the user password and username and confirms that they are matching 3. System compares the user password and username and confirms that they are matching
4. The system logs the user to the website, displaying product postings by them and other users, as well as the history of products the user lent or rented 4. The system logs the user to the website, displaying product postings by them and other users, as well as the history of products the user lent or rented
5. The user chooses a product posting, including the user who posted the product 5. The user chooses a product posting, including the user who posted the product
6. When the user presses the posting, the system will show them all previous reviews for both the product and the user that posted the product 6. When the user presses the posting, the system will show them all previous reviews for both the product and the user that posted the product
7. If the user had left a review before, the review will appear on top 7. If the user had left a review before, the review will appear on top
8. The user can then press the edit review button to the side of the review, which opens a new window showing the user's previous review 8. The user can then press the edit review button to the side of the review, which opens a new window showing the user's previous review
9. The user can then edit the existing review 9. The user can then edit the existing review
10. When the user is done editing their review and rating, they can press the "confirm update" button 10. When the user is done editing their review and rating, they can press the "confirm update" button
11. The system will verify that the number of characters in the review is less than or equal to 250 11. The system will verify that the number of characters in the review is less than or equal to 250
12. The system updates the review of the item/user in the system data base. 12. The system updates the review of the item/user in the system data base.
...@@ -59,7 +89,7 @@ Scenario example: Leaving, deleting or editing a review on a tool ...@@ -59,7 +89,7 @@ Scenario example: Leaving, deleting or editing a review on a tool
## Design Storyboard ## Design Storyboard
### Peter ### Peter
### Charles ### Charles
...@@ -73,16 +103,15 @@ 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. 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. 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**. 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 ## Software Architecture
...@@ -90,7 +119,7 @@ Now we turn to another acceptance test, where the user is able to **see their pr ...@@ -90,7 +119,7 @@ Now we turn to another acceptance test, where the user is able to **see their pr
## Activity Diagram ## Activity Diagram
### Peter ### Peter
### Charles ### Charles
...@@ -104,4 +133,4 @@ Now we turn to another acceptance test, where the user is able to **see their pr ...@@ -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. 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} ![Activity_diagram](uploads/f29c7984d61ecb0c7e94e7a730ec6da3/Activity_diagram.png){width="450" height="1944"}
\ No newline at end of file \ No newline at end of file