Create Use Case Diagram for Scenario 2

[delibas-rojhat]

Current Issue

The documentation currently includes Scenario 2 in textual form, but there is no corresponding Use Case Diagram that visually represents the actors and system interactions.

This makes it harder to clearly understand the scope of the system behavior and the involved actors at a high level.

Proposed Improvement

Create a UML Use Case Diagram for Scenario 2 that:

Identifies all relevant actors

Clearly defines the system boundary

Represents the main use cases described in the scenario

Shows relationships such as include/extend where applicable

The diagram will improve clarity, support documentation completeness, and provide a visual overview of the system functionality related to Scenario 2.

Affected Location

No response

Impact

None

[delibas-rojhat]

Can you review @kckagancan @erinc00 @mehmetcangurbuz08

[kckagancan]

Since the system automatically matches help requests with volunteers, there is no such thing as accept/reject. Volunteer should be able to just cancel the assignment when it is needed. He/she should not reject or accept it. Other than that it seems pretty fine.