Scenario: Preserving the Memory of Eski Çınar Parkı – Ceyhan, Adana - bounswe/bounswe2026group4 GitHub Wiki

User Profile

Name: Ayşe Demir

Age Group: 35–44

Location: Ceyhan, Adana – İstasyon Mahallesi

Background:

Ayşe Demir is a 35-year-old woman who grew up in İstasyon Neighborhood in Ceyhan, Adana. The neighborhood culture was deeply rooted in close relationships. Neighbors knew each other well, families frequently gathered together, and children grew up collectively in shared public spaces. Community bonds were strong, and daily life was intertwined across households.

Eski Çınar Parkı was one of the most important shared spaces in the neighborhood. It was where families met in the evenings, wedding convoys passed through, Ramadan events were organized, and children played hide-and-seek until sunset. The park was not only a physical location but also a symbol of togetherness and collective memory.

In recent years, the park was demolished and replaced by a multi-story residential building. For Ayşe, this change represented more than the disappearance of a physical space, it created a fear that the shared history of the neighborhood would gradually fade. She wants to document her own memories, but she is also deeply motivated by the idea that other residents and their families might contribute photographs from personal albums and share their stories. Ayşe believes that seeing and reading those shared memories would affect her emotionally and help rebuild a sense of belonging by transforming a lost physical place into a preserved collective archive.

Ayşe is comfortable using web platforms and social media, though she is not technically advanced. She values community ties, cultural continuity, and intergenerational connection.

Goals

Ayşe uses the system to:

Preserve her childhood memories.
Digitally share old family photographs.
Document cultural activities that took place in the park.
Discover stories from other residents who grew up in the same neighborhood.
Pass the neighborhood’s history to her children and younger generations.

Her motivation is not only nostalgia, but the preservation of cultural continuity.

Pre-Conditions

Ayşe is registered and her account is verified.
She has:
- Scanned historical photographs taken in the park.
- A short recorded video where she narrates her memories (filmed on her phone).
The system has:
- Active map functionality.
- Story creation capability.
- Commenting functionality for posts.

Main Flow

Ayşe logs into the platform.
The system displays the map on the home page.
Ayşe explores the map interface and decides to add a new memory.
She clicks “Add Story.”
The system opens the story submission form.
In the location section of the form, Ayşe opens the embedded/selectable map.
She navigates to Eski Çınar Parkı / İstasyon Neighborhood on the map.
She marks the former park location from the map shown inside the story creation flow.
Ayşe continues filling the form:
- Enters the title: “Growing Up in Eski Çınar Parkı”
- Selects the time range (1970–2005)
- Writes a description of at least 200 chracters
- Uploads 3 historical photographs (JPEG)
- Uploads 1 video recording (MP4) where she narrates the story
The system:
- Validates required fields
- Verifies file sizes
- Displays upload progress
The story becomes publicly visible.
The story appears as a pin on the map.
Ayşe opens her story:

Views the photographs
Watches the video

She notices another resident’s story at the same location.
Ayşe leaves a comment expressing appreciation.
The system displays her comment with a timestamp.

Criteria

This scenario is supported by the following requirements.

Authentication and Access

1.1.2.1 Registered users shall be able to log in and log out securely.
1.2.1.6 The system shall authenticate users via email and password during log-in.
1.1.2.10 Registered users shall be able to do everything the unregistered users can do.

Map Interaction and Location Selection

1.3.1.1 The platform shall allow users to select a specific geographic location on the map when creating a story.
1.3.1.2 The system shall require users to provide a place name (venue/building/location name) in addition to selecting the geographic location.
1.3.1.6 The map shall support zooming and panning.
1.3.1.8 The map shall update displayed stories based on active search queries and filters.

Search and Filtering

1.3.5.1 The platform shall allow users to search stories by:
- Story title
- Story narrative text
- Tags
- Location name

Story Submission

1.1.2.2 Registered users shall be able to create and submit stories.
1.4.1.1 The system shall require a minimum set of fields for story submission to support authenticity and discoverability:
- Title
- Written narrative text
- Geographic location (map selection)
- Place name (venue/building name)
- Time information
1.4.1.2 The system shall support flexible time resolution for stories (e.g., exact year, approximate year, decade, or year range).
1.4.1.4 The system shall allow users to submit stories associated with locations different from their profile location.

Media Upload and Management

1.4.2.1 The system shall support story media uploads including:
- Images
- Audio recordings
- Video
1.4.2.2 The system shall support stories that combine multiple media types in a single post.
1.4.2.3 The system shall validate media file type and file size during upload.
1.4.2.4 The system shall associate uploaded media with the story record and preserve media metadata needed for rendering.

Story Visibility and Display

1.4.3.1 The system shall maintain a story status, including at minimum:
- Published
- Removed

Map Display

1.3.1.3 The platform shall display stories on the map, each represented by a pin associated with a specific geographic coordinate.
1.3.1.4 If multiple stories exist at the same geographic coordinate, the system shall distinguish them based on place name and time information.
1.3.1.5 Clicking on a pin shall display a short story preview including:
- Place name
- Time information
- Story title
1.3.1.7 The map shall allow users to open the full story page by clicking on the preview.

Story Page

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
- Year or approximate time period
- Contributor name (if visible)
- Submission date
- Number of likes
- Comments
1.3.3.4 The story page shall display embedded multimedia content (images, audio, video) if available.
1.3.3.5 Multimedia content shall be viewable or playable directly on the story page.