Admin user stories #1
Description
User Story 1: Admin Login
Title:
As an Admin, I want to log into the portal with my username and password, so that I can manage the platform securely.
Acceptance Criteria:
The admin must enter a valid username and password to access the portal.
The system should display an error message if invalid credentials are entered.
The admin should be redirected to the admin dashboard upon successful login.
Priority: High
Story Points: 3
Notes:
Consider enforcing multi-factor authentication (MFA) for added security.
Passwords must be stored securely using encryption.
User Story 2: Admin Logout
Title:
As an Admin, I want to log out of the portal, so that I can protect system access after completing my session.
Acceptance Criteria:
The system must provide a visible logout option on all admin pages.
Upon logout, the admin session should be invalidated immediately.
The admin should be redirected to the login page after logging out.
Priority: High
Story Points: 2
Notes:
Ensure that session tokens are destroyed to prevent unauthorized reuse.
Auto-logout after inactivity should also be considered.
User Story 3: Add Doctor to Portal
Title:
As an Admin, I want to add doctors to the portal, so that new doctors can be onboarded and made available for patient bookings.
Acceptance Criteria:
The admin must be able to enter doctor details (name, specialization, contact info, availability).
The system should validate that all required fields are complete before submission.
A confirmation message should appear after successfully adding a doctor profile.
Priority: High
Story Points: 5
Notes:
Automatically send an onboarding email with login credentials to the doctor.
Consider role assignment for new doctor accounts.
User Story 4: Delete Doctor Profile
Title:
As an Admin, I want to delete a doctor’s profile from the portal, so that I can remove inactive or incorrect profiles from the system.
Acceptance Criteria:
The admin should be able to locate a doctor’s profile via search or list view.
A confirmation prompt must appear before deletion.
The doctor profile should be permanently removed from the database after confirmation.
Priority: Medium
Story Points: 3
Notes:
Consider soft deletion (mark as inactive) to preserve appointment history.
Deletion should not affect past patient records.
User Story 5: Run Stored Procedure for Appointment Statistics
Title:
As an Admin, I want to run a stored procedure in MySQL CLI to get the number of appointments per month, so that I can track usage statistics.
Acceptance Criteria:
The stored procedure should return monthly appointment counts grouped by month and year.
The procedure should run successfully without modifying existing data.
The admin should be able to view or export the results for reporting.
Priority: Medium
Story Points: 4
Notes:
Ensure appropriate database permissions for execution.
Results could later be integrated into the admin dashboard.