Customer Meeting - bounswe/bounswe2025group8 GitHub Wiki

Customer Meeting

Date: 2025-03-06
Time: 21:00

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.

1. User and Profile Management

  • 1.1 Name, surname, username, e-mail address shall be required upon registration, phone number and social media login are optional.
  • 1.2 There should not be any restriction.
  • 1.3 E-mail address and password should be used for log-in.
  • 1.4 Name, past and active tasks, average rating, total completed tasks, reviews should be on the profile page. They cannot set to be private and other users can read reviews. User location should not be on the profile.

2. Task Posting & Management

  • 2.1 Title, description, category, location, deadline, requirements should be included. Location can be specified at neighbourhood level.
  • 2.2 Yes, system should support auto-creation of postings for recurring tasks.
  • 2.3 Maybe. There should be basic template (title, description etc.), while additional templates are optional.
  • 2.4 Urgency level determination decision is left to us.
  • 2.5 Exact location and phone number should be only visible to the volunteer once he is assigned to the task.
  • 2.6 We should decide on predefined categories.
  • 2.7 Custom tag creation is still open to discussion.
  • 2.8 Recurring tasks should not be re-created if they had no volunteers. Not recurring tasks should expire on deadline.

3. Volunteer Signup & Assignment

  • 3.1 Yes. Volunteer number for requests should be defined upon task creation.
  • 3.2 Only requesters should post.
  • 3.3 Requester confirmation should be enough.
  • 3.4 No restriction on proximity.
  • 3.5 Requester shall be able to select the assignee among volunteers.
  • 3.6 Yes, requester should be able to change assignee.
  • 3.7 After assignment the task should not allow more volunteers but task can be active again in the case of cancellation.

4. Location-Based Filtering

  • 4.1 Users should decide on task proximity.
  • 4.2 Users should be able to enter location for tasks manually.

5. Search & Sort

  • 5.1 Titles should be searchable. Other fields are not decided. Users can filter tasks by labels.
  • 5.2 Yes, user profiles can be accessed through searching and filtering. Location and rating can be used as filters.
  • 5.3 Default is combination but it should be customizable by users.

6. Communication & Notifications

  • 6.1 Phone number sharing after assignment. Built-in chat is not necessary.
  • 6.2 No built-in chat.
  • 6.3 Updates on users and bookmarked users, tasks, maybe categories.
  • 6.4 Notifications should not be customizable.

7. Review & Rating System

  • 7.1 Reviews should consist of a score and a comment, no categories.
  • 7.2 Yes, through the reporting system including report type and description.
  • 7.3 There should be reporting system to prevent fake reviews.
  • 7.4 No anonymity.
  • 7.5 Number of created tasks, completed tasks, completion rate and average rating.
  • 7.6 Yes, these metrics should be part of default sorting of tasks. Additionally there should be a filter by rating option and sorting feature.
  • 7.7 There should be badges (5 tasks completed, 10 tasks completed etc.); graphs are optional.
  • 7.8 There should not be a leaderboard.

8. Security & Privacy

  • 8.1 User accounts and data should be protected.
  • 8.2 E-mail verification is enough.
  • 8.3 Yes, there should be a reporting system.
  • 8.4 There should not be a privacy option.

9. Scalability & Performance

  • 9.1 Several large cities of users should be supported.
  • 9.2 Response time, server load, downtime should be used for assessment of system performance.
  • 9.3 It should be available globally (?).

10. Admin & Moderation Features

  • 10.1 There could be admins selected from users of the communities (optional).
  • 10.2,3 Community admins should be able to close tasks with a comment, but otherwise have no control over tasks or users.
  • 10.2,3 System moderators should have control over users and tasks such as account suspension, task deletion, except privacy-related matters.
  • 10.4 ---
  • 10.5 Not required from the system to auto-detect foul language, but can be reported by users.

11. Payments & Monetization

  • 11.1 There should not be any kind of payment system.
  • 11.2 Voluntary donations would sustain the app.

12. Bookmarking

  • 12.1 Users can bookmark tasks, and follow each other.
  • 12.2 Bookmarked items should be organized using predefined tags provided by community admins, allowing users to select these tags for searching.
  • 12.3 Yes, users should receive notifications when a bookmarked task is updated.
  • 12.4 No, there is no limit for the number of a user’s bookmarks.
  • 12.5 Bookmarks should be kept private.