Customer Meeting 451 ‐ 1 - bounswe/bounswe2025group8 GitHub Wiki

Customer Meeting

  • Date: 06/10/2025 - 9pm
  • Platform: Google Meets
  • Note Taker: Ahmet Eren Aslan

Attendees

10/11 team members attended.

  • Abdullah Rüzgar
  • Ali Sönmez
  • Ahmet Eren Aslan
  • Alperen Garip
  • Batuhan Büber
  • Hayrettin Eren Yıldız
  • Eray Yüklü
  • Erdem Koçak
  • [] Musa Kaan Güney
  • Üveys Aydemir
  • Yusuf Kaan Akçay

Agenda

  • Present elicitation questions to the assistant.
  • Gather and summarize responses regarding functional and non-functional requirements.
  • Discuss teacher’s feedback and project expectations.

Discussion

Below are the responses of the customer to our questions. Responses are arranged according to the question numbers they correspond to. Questions can be accessed here.

  • Photo Upload Requirements:

    • Maximum file size limit is reasonable.
    • The decision on supported formats is left to the team’s discretion.
    • Multiple photos should be supported, with a maximum limit (e.g., 4).

  • Content Moderation:

    • No automatic filtering; inappropriate content will be handled through user reports.

  • Password Strength:

    • No special complexity rules required beyond minimum glossary definition.

  • Privacy Policy Consent:

    • Consent should be given during registration.
    • The policy should explain what happens upon deletion.

  • Task Assignment:

    • Both one-by-one and group selection approaches are acceptable.

  • Review System:

    • Reviews should be two-way between requesters and volunteers.

  • Bookmark Tags Management (Task Tags):

    • Users can propose custom tags.
    • Moderators can create tags upon user request.

  • Recurring Tasks:

    • Deadlines should remain the same unless the user edits them manually.

  • Feed Ranking:

    • Tasks of interest, deadlines, and location are reasonable factors to consider.
    • Detailed prioritization can be decided during implementation.
    • Example: Tasks outside the user’s city won’t appear on the home feed by default but will be searchable.

  • Location & Contact Info:

    • Skipped in this session.

  • Notification Content:

    • Example messages:
      • “Volunteer request for [task name] is accepted”
      • “Your task got volunteered by [volunteer name]”
    • Sensitive details should not be included directly in notifications.

  • Password Reset Security:

    • Reset links should be single-use and valid for one day.

  • Teacher Feedback:

    • Emphasized that standards and accessibility are key focus areas for the project.
    • Suggested preparing a demo involving accessibility, such as a blind user requesting help and a volunteer responding via phone.