Scenario 1 Use Case Diagram

Use Case Diagram 1 – Sub-group 2

Note on Ambiguities and Assumptions

The following ambiguities were identified in the scenario description. The diagram was constructed based on the assumptions listed below:

1. Cancellation of Assignment

Ambiguity: The scenario did not clearly describe exception handling after assignment.
Assumption: A helper can cancel an assignment if they become unable to help. This is modeled as an extension of viewing assigned requests.

2. Offline Behavior

Ambiguity: It was not explicitly stated how the system behaves without internet connectivity.
Assumption: The system follows an offline-first approach. Requests are saved locally and synchronized when connectivity is restored.

3. Location Handling

Ambiguity: The frequency and mechanism of location updates were not defined.
Assumption: The system periodically updates the user’s last known location (e.g., every few hours) if location permission is granted.

4. Status Lifecycle Modeling

Ambiguity: The request state transitions were not formally described.
Assumption: Status changes (Pending, Assigned, Resolved, Cancelled) are internal system states and are not modeled as separate modifying use cases.

5. Notification Logic

Ambiguity: The delivery mechanism for assignment notifications was not detailed.
Assumption: Notifications are automatically triggered after successful assignment and are handled internally by the system.