Scenario: Guest User Browsing Boğaziçi History and Registering to Comment - bounswe/bounswe2026group4 GitHub Wiki
User Profile
Name: Ali Yilmaz
Age: 18 years old
Role: University student
Location: Originally from Konya, just moved to Istanbul.
Background: Ali just enrolled in Bogazici University and he is interested in history. He wants to get to know his new home.
Goals
- He wants to learn about the culture of his University and his new neighbourhood.
- He wants to read stories from old students of Bogazici University.
- He wants to see old pictures/videos of Bogazici.
Pre-Conditions
- The website is deployed and accessible via search engines.
- There are existing posts related to Boğaziçi University and Hisarüstü.
- Required system components are operational.
Main Flow
- User searches "Boğaziçi Hisarüstü History" on a search engine.
- The website appears in search results.
- User clicks the link and lands on the homepage which is a feed consisting of all stories.
- The user switches to map view which includes:
- An interactive map
- A search bar
- Pins indicating locations of stories.
- User types "Boğaziçi University" in the search bar.
- The map displays pins for all stories with location Boğaziçi University.
- User clicks a pin and a preview of the story opens.
- The user clicks 'read more' and is redirected to the story detail page.
- User reads the story about the old library building and wants to ask a question. (1.1.1.3)
- User clicks the comment section.
- Since the user is not logged in, the system redirects to the Login/Register page.
- User registers using:
- Username
- Password
- Password Confirmation
- User receives a verification code in their e-mail.
- User types the code and registers successfully.
- After registration, the system redirects the user back to the previous story page.
- User posts a comment asking about the construction of a new library.
Criteria
- 1.1.1.1 Unregistered users shall be able to view stories on the map interface.
- 1.1.1.3 Unregistered users shall be able to open and read full story details.
- 1.1.1.5 Unregistered users shall be able to search locations on the map interface.
- 1.1.1.7 Unregistered users shall be able to register/create an account.
- 1.1.1.8 Unregistered users shall have read-only access and shall not be able to perform restricted actions.
- 1.1.2.5 Registered users shall be able to comment on stories.
- 1.2.1.1 The system shall require a unique email address during registration.
- 1.2.1.2 The system shall validate the e-mail via a 6 digit validation code during registration.
- 1.2.1.3 The system shall require a unique user name during registration.
- 1.2.1.4 The system shall require a password that meets the defined criteria during registration.
- 1.2.1.5 The system shall require password confirmation during registration.
- 1.3.1.3 The platform shall display stories on the map, each represented by a pin.
- 1.3.1.5 Clicking on a pin shall display a short story preview.
- 1.3.1.7 The map shall allow users to open the full story page by clicking on the preview.
- 1.3.1.8 The map shall update displayed stories based on active search queries and filters.
- 1.3.2.1 The platform shall provide a feed view displaying stories in card format.
- 1.3.2.2 Each story card in the feed shall include title, location, date/time period, preview text, and media indicators.
- 1.3.2.3 The feed shall preserve applied filters and search criteria when returning from a story page.
- 1.3.2.5 The feed shall support continuous scrolling or pagination.
- 1.3.3.1 Selecting a story from the feed or map shall open a dedicated story page.
- 1.3.3.2 The story page shall display the full written narrative.
- 1.3.3.3 The story page shall display story metadata including location, time information, contributor name (if visible), and submission date.
- 1.3.3.4 The story page shall display embedded multimedia content if available.
- 1.3.3.5 Multimedia content shall be viewable or playable directly on the story page.
- 1.3.5.1 The platform shall allow users to search stories.