* The **Tool Loop Communication System** enables users, such as Lily and the Other User, to engage in real-time messaging and coordinate tool-sharing arrangements. Lily can initiate a **real-time chat**, which includes the ability to **view past messages** for reference. The system also allows both users to **receive real-time messages**, ensuring smooth and instant communication. Additionally, users can **customize their notification settings** to control how they receive alerts for new messages. If necessary, within the chat, users can **coordinate tool-sharing arrangements**, allowing them to organize and confirm the exchange of tools efficiently. The system enhances collaboration by integrating messaging, history tracking, and scheduling features into a seamless user experience.
This sequence diagram illustrates the **push notification flow** in a messaging system. The **actor** enables notifications in the settings, prompting the **system** to send push notifications to the **device** when a new message arrives. Upon receiving a notification, the system updates the message status. The actor then clicks on the notification, triggering the system to mark the message as read and display any unread messages. This process repeats in a loop whenever a new notification is received, ensuring that the user stays informed of new messages.
This **activity diagram** represents the process of initiating and conducting a chat conversation within a messaging app.
The flow begins when **Lily opens the app**, displaying the “Chats” section. She then **selects a user to chat with**, leading to the **chat window opening**. Lily proceeds to **send a message** (e.g., “Hey, is the drill available?”), prompting a response from the other user (e.g., “Yes, you can pick it up at 5 PM”). The conversation concludes with confirmation, ensuring both parties are aligned on the next steps. This structured flow ensures smooth communication and decision-making between users.
ToolTara's use case diagram [here](https://editor.plantuml.com/uml/VPB1QiCm38RlUWhHUmfjcXn6AOLrE-qmnhAx5okfmRM2hT33jdTVN18sPoC-6NqVbdxRno3AIt-nOAaH54PlshEWDfvgCUn0rS8Ugq1-t9wKg7SL220gohMMy9NPFZ5t-04uh3vGFHYuUg7M124VAtw5Ac1rlqcLDqDNx3mtnj9eR5FZGHkP33IkuL7BKwtgB2kDV7NOdLauZDfkhcabXCz9no9rJcHfSDAfIlW2YFU0MNQ8EV0E7uqFmwsP2zqI_iRR0K_nIV_1-JBUBUDY6PV_O8WZhTUVK_EzSRNjDHqYoN6VPJyl6_lF2iMyKCuBcoduxRmn1i2Hd8x_wni0).
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).
...
...
@@ -29,10 +89,6 @@ We build a use case diagram for my [first user story](https://git.cs.usask.ca/vr
**Actors**: Website user (primary), website data base (secondary).
**Version**: 1.2
**Person in Charge**: Hakeem Hannoon
**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.
...
...
@@ -61,27 +117,7 @@ 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.
...
...
@@ -95,50 +131,15 @@ Now we turn to another acceptance test, where the user is able to **see their pr
This sequence diagram illustrates the **push notification flow** in a messaging system. The **actor** enables notifications in the settings, prompting the **system** to send push notifications to the **device** when a new message arrives. Upon receiving a notification, the system updates the message status. The actor then clicks on the notification, triggering the system to mark the message as read and display any unread messages. This process repeats in a loop whenever a new notification is received, ensuring that the user stays informed of new messages.
This **activity diagram** represents the process of initiating and conducting a chat conversation within a messaging app.
The flow begins when **Lily opens the app**, displaying the “Chats” section. She then **selects a user to chat with**, leading to the **chat window opening**. Lily proceeds to **send a message** (e.g., “Hey, is the drill available?”), prompting a response from the other user (e.g., “Yes, you can pick it up at 5 PM”). The conversation concludes with confirmation, ensuring both parties are aligned on the next steps. This structured flow ensures smooth communication and decision-making between users.
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.
* The **Tool Loop Communication System** enables users, such as Lily and the Other User, to engage in real-time messaging and coordinate tool-sharing arrangements. Lily can initiate a **real-time chat**, which includes the ability to **view past messages** for reference. The system also allows both users to **receive real-time messages**, ensuring smooth and instant communication. Additionally, users can **customize their notification settings** to control how they receive alerts for new messages. If necessary, within the chat, users can **coordinate tool-sharing arrangements**, allowing them to organize and confirm the exchange of tools efficiently. The system enhances collaboration by integrating messaging, history tracking, and scheduling features into a seamless user experience.
