Customer Meeting 1 - bounswe/bounswe2026group4 GitHub Wiki

Details

📅 Date: 18 / 02 / 2026
📍 Location: Google Meet — https://meet.google.com/sce-esnr-mio
🕒 Duration: 17:45 – 18:15
👥 Customer: Kutay Eroğlu

👥 Participants

  • OĞUZ SEMİH ARIK
  • ÖMER FARUK ÇELİK
  • SEZİN DOĞAN
  • MERT EREN KAPLAN
  • AYSU KESKİN
  • KEMAL MAHMUTOĞULLARI
  • OSMAN YUSUF TOSUN
  • AHMET ÇAĞDAŞ GİRİTLİ

Purpose of the Meeting

Asking the customer (Kutay Eroğlu) our predetermined requirement elicitation questions and structuring our project requirements based on the direct answers, attitude, and guidance of the customer.

Meeting Results

Scope of the product (Local vs Global)

  • A map is the best tool when looking for a place. For interface. Map is MUST.
  • The whole map. A user should be able to consume stories from other locations. Inclusiveness.
  • Hisarüstü data/stories are sufficient when populating the database.

User roles

  • Guest and role concept discussed.
  • What should an unregistered user see in the app? → Should be able to see stories (read-only).
  • Incorrect stories, security issues, and spam → need registered users.
  • Should there be roles? Contributor and documentarian mentioned. Description states elderly and youth connection, but not limited to that.
  • If they have a story to tell, why not?

Profile page visibility & posting location flexibility

  • Example scenario: Family in Kırşehir but user lives in İstanbul → should be able to share that story.
  • User should be able to post stories of another place (Kırşehir–İstanbul story).
  • Think of well-meaning scenarios.

Reward system

  • Can put a requirement for reward system.

Main page experience

  • Seeing a specific location's stories fast.

Post display formats

  • Domain specific → not just a feed.

Search & filtering

  • Customer cannot specify exact filtering dimensions.
  • Focus should be on needs.
  • Absolute must → filtering and searching.

Who can create posts

  • Measures should be taken against misuse and exploitation.
  • Do not restrict posting by location, but moderation is required.

Supported media types

  • Good to have (not absolute must).
  • Not only text.
  • Should be able to combine media types.

Social interaction features

  • Like / dislike / comment / save → Yes.

Story metadata (posting fields)

  • Must-have fields should exist, but the team should determine them.
  • When someone reads a story, what information is required to understand it is real?
  • Time resolution may vary (e.g., “in my childhood…”).
  • Year is needed as a starting point.
  • Flexible ranges (2010–2020, 80’s, etc.).
  • Timeline of a location can show decades.

Notifications

  • Might be enforced in the future.
  • Not a consideration now.

Complaints & privacy

  • Edge case.
  • Especially privacy issues.

Verification & moderation

  • Verification is vague.
  • Do not restrict but allow reporting.
  • Hard to automate verification → moderator needed.
  • Look at how Google Maps handles it.

Extra Notes

  • A page for a larger location (e.g., Istanbul) can be implemented.
  • Customer was not a huge fan but it can be a good addition.

Stakeholder Insights

  • Customer strongly emphasized that map is the core interface element and should be central to the experience.
  • Inclusiveness is important → users should be able to explore stories from different locations, not only their own.
  • Customer prefers not restricting storytelling too much, but enabling reporting and moderation instead.
  • Flexibility in storytelling is important (location mismatch scenarios, approximate time ranges).
  • Filtering and searching are considered absolute must features, even though exact criteria are not defined yet.
  • Media richness is desirable → stories should support combined media (not text only), but it is not a strict requirement.
  • Customer tends to favor guidance over strict rules (fields exist, but team defines them).

Decisions (Implicit / Directional)

  • Map-based interface is mandatory.
  • Guests can read stories (read-only).
  • Registered users are required to reduce spam and incorrect content.
  • Moderation is required, but strict verification is not.
  • Posting should not be restricted by location.
  • Search and filtering are mandatory.
  • Social interaction features (like / comment / save) will exist.
  • Story posts must contain some required metadata (fields to be defined by team).
  • Timeline concept based on year/period is supported.
  • Notifications are not in scope for now.

Open Questions

  • Exact user roles definition (contributor, documentarian, others?).
  • Exact filtering dimensions (time, location, topic, etc.).
  • Definition of required story fields.
  • Reward system design and scope.
  • Verification workflow details.
  • Complaint and privacy handling workflow.
  • Large location pages (e.g., Istanbul) → optional feature, unclear priority.
  • Media requirements → which combinations must be supported at MVP level.
  • Moderation workflow design (manual vs hybrid).