Scenario 3_archive - bounswe/bounswe2025group1 GitHub Wiki

🌱 Scenario: Assigning and Tracking Gardening Tasks

Persona

Sophia (35) is a busy professional and a passionate gardening enthusiast living in San Francisco, California. She is an active member of a shared community garden, but due to her demanding work schedule, she finds it challenging to keep up with all the garden maintenance tasks herself. She registered to Community Garden Planner to easily find a community of volunteers to help her with tasks. To ensure fair contribution and efficient upkeep, she uses the Community Garden Planner to assign and track responsibilities among members.

Pre-Conditions

  • Sophia is registered as a Member and holds the Manager role for her garden.
  • Other garden participants (e.g., Alex) are registered Members and Workers in the same garden.
  • Notifications are enabled for task-related updates.

Scenario Steps

  1. Sophia logs into the Community Garden Planner via the mobile or web platform.
  2. She navigates to the Task Management section of her garden.
  3. She clicks “Create Task” and enters the following details:
    • Title: “Water the vegetable beds”
    • Description: “Please ensure all beds are evenly watered, especially the lettuce and herbs.”
    • Deadline: Tomorrow at 6:00 PM
    • Assignees: Selects a group of 3 community members, including Alex
  4. The task is created and automatically assigned to the selected members (FR 2.5).
  5. All assigned users receive a task notification (FR 6.1) with task details and due date.
  6. Later that day, Alex logs into the platform, views his assigned tasks, and updates the status to “In Progress” as he begins watering (FR 2.2, 2.7).
  7. After completing the task, Alex updates the status to “Completed” with a short note:

    “All beds watered. Checked moisture levels — all good!”

  8. Sophia receives a notification that the task has been marked as completed (FR 6.1).
  9. She navigates to the Task Log, reviews Alex’s note, and verifies in person the next morning that the task was successfully done.
  10. Satisfied, she leaves a thumbs-up or brief comment of thanks on the task (optional feature for feedback or acknowledgment).

Post-Conditions

  • The task is stored in the garden's task history with the status set to Completed.
  • Sophia confirms the work has been done, and no further action is needed.
  • Task responsibility is distributed and tracked fairly among the garden members.

Alternate Flows

  • If no one starts the task before the deadline, the system sends an automatic reminder to all assignees.
  • If multiple users start the task at the same time, the system allows parallel updates and notes from all participants.

Dependencies

  • Task Assignment Module (FR 2.1 - 2.8)
  • Notification System (FR 6.1, 6.2)
  • Role-based Access Control (FR 7.6.1.2, 7.6.2.2)
Version Created By Create Date Reviewer Review Date
1.0 Ahmet Ayberk Durak 25.02.2025 Tolga Acar 03.03.2025
2.0 Ceylanberk Tola 24.03.2025 Başak Tepe 25.03.2025