Scenario 2 ‐ Private Event Organization - bounswe/bounswe2026group11 GitHub Wiki

User Profile

Pelin Tezer is a 21-year-old Industrial Engineering student known for her organizational skills and "the more, the merrier" attitude. She has a diverse social circle—ranging from her engineering classmates to her local archery club—and she wants to host a private backyard dinner to introduce these different groups to one another. Being a busy student, she values efficiency and privacy.

Goals

  • Centralized Planning: Organize a high-quality private event without managing multiple group chats.

  • Exclusivity: Ensure the event details (location/time) are only visible to her hand-picked guest list.

  • Automation: Avoid the "manual labor" of inviting 20+ people individually by using the system's invitation features.

  • Social Integration: Successfully bridge her different friend groups in a secure environment.

Pre-Conditions

  • Pelin has an existing, authenticated account.

  • Her friends are already registered users within the system.

  • Pelin has the event photo and details ready.

  • The system is online and the notification service is active.

Main Flow

  • Authentication: Pelin opens the application and logs in using her username and password.

  • Initiation: She taps the "Create a New Event" button on her dashboard.

  • Data Entry: She fills the mandatory fields:

    • Description

    • Location

    • Time Interval

    • Category

    • Image

  • Privacy Setting: Pelin navigates to the Access Control section and selects "Private (Invitation Only)."

  • Guest Selection: She enters the usernames of her friends into the invitation field.

  • Finalization: She reviews the details and clicks "Create."

  • System Action: The system validates the data, stores the event version, and hides it from the public map/search.

  • Notification: The system instantly sends an email and an in-app notification to all invited friends.

Criteria

  • 1.1.3 Users shall be able to log in using phone number or email or username + password.
  • 2.1.1 Users shall create events via a “Create a New Event” button.
  • 2.1.2 Mandatory fields (Location, Time, Category, Description, Image, Host) must be filled.
  • 2.3.1 Events must include both start and end timestamps.
  • 2.4.1 Users shall select a category from a predefined list.
  • 3.1.1 The system shall support "Private" (invitation only) privacy type.
  • 3.1.2 Private events shall not appear in search or map views for non-invited users.
  • 7.4.1 Invited users shall receive email and in-app invitations.
  • 2.1.3 The system shall validate that all mandatory fields are filled before creation.
  • 11.2.1 Private event data shall be restricted from unauthorized users.
  • 7.1.1 Users shall receive notifications via push or email based on preferences.

Mock-up