Elicitation Questions Social Event Mapper - bounswe/bounswe2026group9 GitHub Wiki
1. Product Scope and Policy
1.1 Event Scope (In-scope vs Out-of-scope)
1.1.1. Which event types must the platform support at launch (e.g., concerts, workshops, exhibitions, parties, meetups)?
1.1.2. Which event types must the platform explicitly not allow (e.g., private house parties, 18+ nightlife, political/protest events, religious events, fundraising) or which event types are allowed only under restrictions, and what restriction is required for each?
1.1.3. Must the platform support both “institutional/classical” events (concert/theater) and user-created community events equally in discovery and publishing?
1.2 Geographic Scope
1.2.1. What is the geographic coverage at launch (single city, multiple cities in Türkiye, Türkiye-wide, global)?
1.2.2. Must the platform support online-only events with no physical location?
1.3 Time Horizon
1.3.1. Must default discovery show events happening “now” and “soon” (near real-time) rather than mainly future planning?
1.3.2. Must the platform support recurring events (e.g., weekly repeating events)?
2. Event Publishing & Data Requirements
2.1 Required Event Fields
2.1.1. Which fields must be mandatory for publishing an event (title, description, category, start time, end time or duration, location coordinates, address label, cover image)?
2.1.2. Must the system prevent publishing if mandatory fields are missing or invalid?
2.2 Venue Metadata
2.2.1. Which venue metadata must be supported on the event (accessibility, age restriction, capacity, dress code, language, price/free)?
2.2.2. Must any venue metadata be mandatory for certain event categories (e.g., age restriction required for nightlife)?
2.2.3 Accessibility (Disability Support)
2.2.3.1. Must events specify accessibility features using a structured checklist (e.g., wheelchair accessible, step-free entrance, accessible restroom, elevator, seating available, quiet area, captions/sign language)?
2.2.3.2. Must the platform support indicating which disability groups the event is suitable for (e.g., mobility impairment, visual impairment, hearing impairment, neurodivergent/sensory sensitivity)?
2.2.3.3. Which accessibility fields are mandatory vs optional (e.g., for indoor venues, must “wheelchair access” be explicitly set to Yes/No/Unknown)?
2.3 Host Eligibility
2.3.1. Who must be allowed to publish events: any registered user, or only verified/approved hosts?
2.3.2. Must host verification exist (email verification, phone verification, manual admin approval)?
2.4 Multi-Location & Itinerary (Event Roadmap)
2.4.1. Can a single event have multiple locations/venues (e.g., meetup point + after-party), or must it be exactly one location?
2.4.2. If multiple locations are allowed, does each location need its own start/end time (or is one global event time enough)?
2.4.3. Do you need a structured itinerary/agenda (a list of time-based segments like “18:00 meetup → 19:00 workshop”)?
2.4.4. For itinerary segments, are start/end times required, or is ordering (sequence) sufficient?
2.4.5. If multi-location is supported, must the system define one “primary location” for discovery and pin display?
2.5 Equipment / Materials Requirements
2.5.1. Should hosts be able to specify required vs optional equipment/materials (e.g., “laptop required”, “notebook optional”)?
2.5.2. Must materials support “provided by host/venue” vs “bring your own”?
2.5.3. Must materials be shown in the event details before, and where should equipment requirements be shown (event details page, RSVP flow, reminders/notifications)?
3. Users, Roles & Permissions
3.1 Roles
3.1.1. What user types/roles will exist (e.g., guest, registered user, attendee, publisher/host, admin/moderator)?
3.1.2. Which actions must be allowed for each role: view events, save events, comment, message host, create events, edit own events, cancel events, moderate/report handling?
3.2 Account Requirements
3.2.1. Which actions must require login (saving, commenting, messaging, publishing)?
3.2.2. What sign-in methods must be supported (email/password, Google, Apple, phone)?
3.3 Event Visibility & Access Control (Private Events)
3.3.1. Which visibility modes must be supported (public, unlisted link-only, private invite-only, private code-based, private request-to-join)?
3.3.2. When a user is not authorized to view a private event, must it be completely hidden from the map/search?
3.3.3. How must access be granted for private events (invite list, invite link, access code, join request approval)?
4. Discovery Experience (Map/List/Search)
4.1 Primary Browsing UI
4.1.1. Must the map view be the default entry point for discovery?
4.1.2. Must list view be available as an alternative view?
4.1.3. Which event info must be visible without opening details (title, category, start time, distance, price/free badge, cancellation badge)?
4.2 Search Radius & Map Behavior
4.2.1. What is the default search radius (e.g., 500m, 2km, 10km)?
4.2.2. Should the radius adapt dynamically to the map zoom level?
4.2.3. Must search results update based on the visible map area (map bounds) rather than only the user’s location?
4.3 Time Filtering
4.3.1. Must the UI support selecting a custom time window (start/end) for discovery?
4.3.2. Must quick filters exist for “Now”, “Today”, and “This Weekend”?
4.4 Multi-Location Map Representation
4.4.1. If multi-location events exist, must the map show multiple pins for one event?
4.4.2. If an itinerary exists, must the map show the route/sequence between locations?
5. Taxonomy, Ranking & Filters
5.1 Categories & Tagging
5.1.1. What categories exist, and who defines them (fixed taxonomy vs host-chosen tags)?
5.1.2. Must events support multiple categories?
5.2 Ranking / Sorting Goals
5.2.1. Which sorting modes must exist (distance, soonest start, newest, popularity)?
5.2.2. Must ranking prioritize upcoming events over far-future events even if far-future events are closer?
5.3 Filters
5.3.1. Which filters must be supported at launch (date range, distance, category, price, age restriction, accessibility, online/in-person, language)?
5.3.2. Must filters persist between sessions for logged-in users?
5.3.3. Which filter will be the default one?
5.3.4 Accessibility Filters
5.3.4.1. Must users be able to filter events by accessibility features (e.g., step-free access, accessible restroom, captions/sign language, quiet-friendly)?
5.3.4.2. Must users be able to filter by “suitable for” disability categories (mobility / visual / hearing / sensory)?
5.3.4.3. Should events with “Unknown/Not provided” accessibility be excluded by default when an accessibility filter is applied?
6. Social Features & Interaction
6.1 Messaging
6.1.1. Will there be messaging between users and publishers/hosts (similar to Airbnb-style messaging)?
6.1.2. Must hosts be able to send announcements to all RSVP’d attendees?
6.2 Engagement (Likes/Comments/Reviews)
6.2.1. Must users be able to comment on events, and who will be authorized to do so?
6.2.2. Must the platform support event ratings/reviews after the event ends?
6.3 Host Reputation
6.3.1. Must hosts have a public profile page with past events and ratings?
6.3.2. Must a host's reputation score exist based on cancellations, ratings, and reports?
6.4 RSVP / Attendance
6.4.1. Must the platform support RSVP states “Interested” and “Going”?
6.4.2. Must hosts be able to set a capacity limit for an event?
6.4.3. If capacity is full, must the platform support a waitlist?
6.4.4. Must attendees be able to see how many people are going/interested?
7. Alerts, Empty States & Reporting
7.1 Empty States
7.1.1. When no events match, must the UI show “no events found” plus suggestions to expand the radius or change the time window?
7.2 User-Generated Alerts / Reports
7.2.1. Must users be able to report a host profile?
7.2.2. Must users be able to report an event for misinformation, spam, or safety concerns?
7.3 Notifications
7.3.1. Must the platform notify users about event updates (time/location changes) if they saved or RSVP’d?
7.3.2. Must the platform notify users about cancellations if they RSVP’d?
7.3.3. Must users be able to control notification preferences (updates, reminders, nearby recommendations)?
8. History & Past Events
8.1 Past Events Visibility
8.1.1. Will users be able to view past events (history/archive)?
8.1.2. Must past events be visible to everyone, or only to the host and attendees?
8.1.3. How long must past events be retained (e.g., 90 days, 1 year, indefinitely)?
9. Updates, Cancellations & Integrity
9.1 Editing Published Events
9.1.1. Must hosts be able to edit events after publishing?
9.1.2. Which fields must remain editable after publish (time, location, description, category, capacity, visibility)?
9.1.3. If an event time/location is edited, must the system notify all users who saved or RSVP’d?
9.2 Cancellation and Postponement
9.2.1. Which event states must exist (scheduled, updated, cancelled, postponed, sold out, moved online)?
9.2.2. When an event is cancelled, must it be removed from discovery immediately?
9.2.3. When an event is cancelled, must it remain visible on the event page with a “cancelled” label?
9.2.4. Must the system notify RSVP’d users on cancellation immediately?
9.3 Spam, Duplicates, and Abuse
9.3.1. Must the platform detect and prevent duplicate events (same title/time/location by same host)?
9.3.2. Must there be rate limits on event creation per host (e.g., max events per day)?
9.3.3. Must there be a user reporting flow for events and hosts?
10. Non-Functional Requirements (Verifiable)
10.1 Performance
10.1.1. What is the maximum acceptable response time for search queries (e.g., under 500 ms for 95% of requests)?
10.1.2. How many concurrent users and events must the system support at launch?
10.2 Privacy
10.2.1. Must the platform avoid storing precise user location, except for immediate search?
10.2.2. Must users be able to use the platform without granting location access (manual area search)?