Use Case Diagram 3: Claiming Reward through Leaderboard - bounswe/bounswe2025group2 GitHub Wiki

Legend
Actors
-
User
Participant who views leaderboards and attempts to claim rewards. -
Coach
Can view leaderboards and may interact with reward-related features. -
Admin
Platform administrator who manages the reward catalog and rules. -
System
Backend services coordinating eligibility checks, reservations, and notifications.
User Actions
View Leaderboard
User opens the leaderboard to see rankings for a challenge.
View Reward Details
Inspect reward information (requirements, stock, cost).
Check Eligibility
System or user verifies whether the user meets reward criteria (rank, points, completion).
Claim Reward
User initiates the reward claim process (may require confirmation).
Reserve Reward
System temporarily reserves the reward item while transaction completes (stock lock).
Confirm Redemption
Finalize the reward claim and inform user how to redeem (pickup/code/delivery instructions).
Notify User
System sends a confirmation via in-app notification and/or email.
Administrator Actions
Manage Reward Catalog
Add, edit or remove rewards, set stock and limits.
Accept / Deny Redemptions
Admin approves manual redemption requests or resolves exceptions.
Monitor Inventory & Rules
Adjust thresholds, reset availability, and handle disputes.
System Actions (automated)
Check Eligibility
Backend calls leaderboard/ranking logic to validate claim prerequisites.
Reserve & Deduct
Reserve item in inventory, deduct user points or quota, and write redemption record.
Send Notifications
Trigger push/email/in-app messages when claim is successful or rejected.
Notes:
- The user-facing flow is: View → Check Eligibility → Claim → Reservation → Confirmation/Notification.
- Admin controls are required for catalog management and dispute resolution; most steps are automated by the System.