Use Case Diagram (Final) - bounswe/bounswe2026group11 GitHub Wiki

A unified use case diagram for the project is created using the existing diagrams of each scenario. This diagram shows a comprehensive view of all use cases and user interactions across the Social Event Mapper system, consolidating functionality from Scenario 1 (Discovery and Joining a Protected Event), Scenario 2 (Private Event Organization), and Scenario 3 (Public Event Organization).

🧑‍🧒‍🧒 Actors

The diagram identifies three primary actors:

  • Participant: Users who discover, join, and attend events. They interact with discovery features, event details, join requests, and post-event activities.
  • Organizer: Users who create and manage events. They handle event creation, privacy settings, and approval workflows for protected events.
  • Notification Service: A system actor responsible for delivering push notifications and email invitations.

📦 Packages

The use cases are organized into eight logical packages:

  1. Authentication: User registration and login via phone, username, or email
  2. Profile Management: Profile customization, participation history, and favorite locations
  3. Event Discovery: Map/list views, search, and filtering by distance, time, and category
  4. Event Details: Viewing event information, organizer reliability metrics, participant counts, and saving events
  5. Event Creation: Complete event creation workflow including mandatory fields, location/route selection, time intervals, visibility settings, tags, images, and constraints
  6. Private Event Invitation: Invitation management for private events, including adding invitees, sending notifications, and handling accept/decline responses
  7. Protected Event Join Flow: Request-based access control with organizer approval/rejection, full event access, and ticket generation
  8. Post-Event & Attendance: Ticket usage, organizer rating/feedback, and archived event search

🔄 Relationships

The diagram uses two types of relationships:

  • Include relationships (dashed arrows): Show mandatory sub-use cases that are always executed as part of a base use case (e.g., "View Event Details" always includes "View Organizer Reliability" and "View Participant & Save Count").
  • Extend relationships (dashed arrows): Show optional or conditional use cases that extend base functionality (e.g., "Discover Nearby Events" can be extended by "Filter by Distance", "Filter by Time Window", or "Browse Map View").

This unified diagram provides a complete overview of the system's functionality and serves as a reference for understanding how all user types interact with the Social Event Mapper platform.