Scenario 8 - bounswe/bounswe2025group1 GitHub Wiki

Scenario: Managing Garden Membership and Role Assignment

User Persona

Marcus Chen (45) is a retired teacher who has been managing a community garden in Portland, Oregon for three years. As an organized individual with leadership experience, he needs a system to effectively manage garden membership, assign roles, track maintenance, and foster collaboration among garden members.

Pre-Conditions

  • Marcus is registered on the platform and is the Manager of his garden.
  • Several users have submitted requests to join his garden.
  • The forum and task tracking features are enabled for the garden.
  • Role-based access control is active and functioning correctly.

Scenario Steps

  1. Marcus logs into the Community Garden Planner platform and navigates to the Garden Management section (FR 1.2).
  2. He reviews and manages pending member requests:
    • He accepts two members with complete profiles.
    • He rejects one user due to missing profile information (FR 7.6.1.3).
  3. Marcus promotes Elena, a trusted member, to Manager status (FR 7.6.1.4).
  4. The newly approved members are automatically assigned the Worker role in the garden (FR 7.6.2.1).
  5. Marcus creates a custom task type: "Soil pH Testing" (FR 7.6.1.7).
  6. He assigns a Soil pH Testing task to a Worker with a one-week deadline (FR 7.6.1.5).
  7. The Worker receives the task and accepts it via the notification system (FR 7.6.2.2).
  8. Three days later, the Worker updates the task status to "In Progress" (FR 7.6.2.3).
  9. Upon completion, the Worker logs detailed pH readings into the maintenance record (FR 7.6.2.4).
  10. Marcus reviews the data and creates a follow-up soil amendment task based on the results (FR 7.6.1.6).
  11. He creates a forum post to inform members and share the proposed soil treatment strategy (FR 5.1, FR 7.6.2.5).

Post-Conditions

  • New garden members are properly added and assigned roles.
  • Manager responsibilities are delegated to a trusted member.
  • A custom task type is successfully created and used.
  • Task progress and completion are tracked and recorded.
  • Maintenance data is available for future reference.
  • Communication is facilitated among garden members through the forum.

Alternate Flows

  • If Marcus mistakenly promotes the wrong user, he can revoke Manager rights.
  • If no members accept the task, Marcus can reassign or extend the deadline.
  • If a Worker fails to update task progress, Marcus can send a manual reminder.

Dependencies

  • User Management & Role Control (FR 7.1, FR 7.6)
  • Task Assignment & Tracking Module (FR 2.1 – 2.8, FR 7.6.1.5, FR 7.6.2.3)
  • Notification System (FR 6.1)
  • Forum Module (FR 5.1 – 5.6)
Version Created By Create Date Reviewer Review Date
1.0 Suleyman Tolga Acar 05.03.2025 Ceylanberk Tola 06.03.2025
2.0 Ceylanberk Tola 27.03.2025 Burak Altunay 03.04.2025