Scenario 1 - bounswe/bounswe2026group9 GitHub Wiki

User Profile

Arda Turan
Footballer
Male
He loves interesting parties
39 years old

Goals

Looks at the current map for the beach music party event
He couldn't find what he wanted on the map
He decided to create a new event for Saturday night
Make the event visible on the map for everyone who is 18+ to discover

Pre-Conditions

Some people are already using the website
User is already registered to the system
Arda has good host points in the system
He is using the platform on the website on his laptop

Main Flow

Arda opens the website and browses the map view to find a beach party near Kadıköy for Saturday night
He filters events by the "Music / Party" category, sets the date to Saturday, and adjusts the distance filter to nearby locations
The map updates and shows a few event pins, but none of them match what he is looking for
He clicks on one event pin to check the details, but it is a private event, so the system only shows limited information
He checks another event, but it has already reached its attendee limit
Frustrated with the results, he decides to create his own event and clicks "Create Event"
He enters the event title: "Kadıköy Beach Party Night"
He writes a short description about the party and selects "Music / Party" from the category catalog
He sets the start date/time to Saturday 21:00 and the end date/time to Sunday 02:00
He clicks on the map to mark Kadıköy beach park as the event location, and the system captures the coordinates
He uploads a party poster image that he designed
He sets the event visibility to Public
He checks the 18+ age restriction box
He sets the attendee limit to 50
He clicks "Publish Event" and the system saves the event and displays it on the map
The event detail page is created with all the information, images, and the map location
Arda views his event on the map and confirms that everything looks correct
People really like Arda's party idea because Arda has a great rating. A lot of people already bookmarked it.

Criteria

FRU-1.1 - Registered users shall be able to create community events
FRU-1.1.1 - Users shall provide an event title, description, and category, and shall specify the start and end date/time
FRU-1.1.2 - Users shall be able to upload one or more images for the event and display them on the event page
FRU-1.1.4 - Users shall be able to set the event's visibility as public or private
FRU-1.1.5 - Users shall be able to classify the event by selecting an event type from a predefined catalog
FRU-1.1.6 - Users shall be able to specify the event location.
FRU-1.1.7 - Users shall be able to mark an event as 18+ (age-restricted)
FRU-1.1.8 - Users shall be able to set an optional attendee limit (capacity)
FRU-2.1 - Users shall be able to browse and discover events via a map view and a list view
FRU-2.1.1 - Users shall be able to filter events by criteria including catalog/type, distance, and time/date
FRU-3.1 - Registered users shall be able to view an event details page for public events
FRU-3.1.1 - Users shall be able to bookmark events to view later and to receive relevant notifications/updates.
FRS-3.1.3 - The system shall enforce private event access control at the backend level.
FRS-3.2 - The system shall clearly label events marked as 18+ and may restrict interaction for underage users.
FRS-4.1 - The system shall provide both map and list views for event discovery.
FRU-4.3 - Private events shall be visible to all users in browse/search results, but full details shall not be visible to non-host users
FRU-5.1.3 - host rating.
FRS-5.2.2 - The system shall prevent additional users from marking the event as Going once the capacity limit is reached.
FRS-5.2.3 - The system shall display the event as full or sold out when capacity is reached.
NFR-01 - Search response time
NFR-02 - Update/cancellation visibility time
NFR-04 - Private event protection (backend enforced)