Extended Use Cases for Student Alumni Management System

This section outlines the detailed extended use cases for the Student Alumni Management System.
Click any of the following to jump directly to a specific use case.

Table of Contents

1. UC1: User Registration and Login
2. UC2: Profile Management
3. UC3: Announcement Management
4. UC4: Event Management
5. UC5: Job Posting and Viewing
6. UC6: Achievement Sharing
7. UC7: Donation Management
8. UC8: Data Viewing and Search
9. UC9: Photo Gallery Management

UC1: User Registration and Login

Actors: Student, Alumni
Description:
Allows users to register for an account using valid credentials and log in to access their respective dashboards.

Precondition:
User provides valid registration details (unique email, password ≥ 8 characters with mix of cases and numbers).

Postcondition:
Account is created successfully and user is redirected to the respective dashboard.

Normal Flow:

1. User selects “Register” option.
2. System displays registration form.
3. User enters Name, Email, Degree, Department, Graduation Year (for Alumni), Contact Number, Password, and Confirm Password.
4. System validates all fields.
5. System checks if email is unique.
6. System encrypts and stores user data in the database.
7. System displays a confirmation message.
8. User proceeds to “Login” page.
9. User enters Email and Password.
10. System verifies credentials and creates a login session.
11. User is redirected to their respective dashboard.

Alternative Flow:

• If email exists → show “Email already registered.”
• If passwords do not match → show “Passwords do not match.”
• If login fails → show “Invalid credentials.”

Exception Flow:

• Database or server error → show “System unavailable. Please try again later.”

UC2: Profile Management

Actors: Student, Alumni
Description:
Allows users to view and update their personal, academic, and professional information.

Precondition:
User must be logged in.

Postcondition:
Profile is successfully updated and saved in the database.

Normal Flow:

1. User selects “Edit Profile.”
2. System displays current profile details.
3. User updates editable fields (contact info, academic details, job title).
4. User clicks “Save Changes.”
5. System validates input and updates database.
6. System displays success message and updated profile.

Alternative Flow:

• Invalid data → show “Invalid input. Please check fields.”
• No changes → show “No updates detected.”

Exception Flow:

• Database connection lost → show “Unable to update. Please try again later.”

UC3: Announcement Management

Actors: Alumni
Description:
Allows alumni to post, edit, and delete announcements visible to all users.

Precondition:
Alumni must be logged in.

Postcondition:
Announcements are successfully displayed to all users.

Normal Flow:

1. Alumni selects “Add Announcement.”
2. System displays announcement form.
3. Alumni enters title, content, and optional attachment/link.
4. Alumni clicks “Post.”
5. System stores the announcement and displays it on the dashboard.
6. Alumni can later edit or delete the announcement.

Alternative Flow:

• Mandatory fields empty → show “Title or content cannot be empty.”

Exception Flow:

• Database failure → show “Unable to save announcement.”

UC4: Event Management

Actors: Alumni
Description:
Allows alumni to create, edit, and delete events viewable by all users.

Precondition:
Alumni must be logged in.

Postcondition:
Event details are stored and displayed to all users.

Normal Flow:

1. Alumni selects “Create Event.”
2. System displays event creation form.
3. Alumni enters event name, date, location, and description.
4. System validates and saves event.
5. System displays the event on the dashboard for all users.
6. Alumni may later edit or delete the event.

Alternative Flow:

• Missing required fields → show “Please complete all required fields.”

Exception Flow:

• Database error → show “Event creation failed.”

UC5: Job Posting and Viewing

Actors: Alumni (post), Student (view)
Description:
Alumni can share job opportunities; students can browse or apply.

Precondition:
User must be logged in.

Postcondition:
Job posting is visible to all users.

Normal Flow:

1. Alumni selects “Post Job.”
2. System displays job form.
3. Alumni fills position title, company, location, description, and link.
4. System stores and displays the job on dashboards.
5. Students select “View Job” to see details.

Alternative Flow:

• Missing job title or description → show “Fields cannot be empty.”

Exception Flow:

• Database failure → show “Unable to post job.”

UC6: Achievement Sharing

Actors: Student, Alumni
Description:
Allows both students and alumni to post achievements with text or images.

Precondition:
User must be logged in.

Postcondition:
Achievement is visible in the “Achievements” section.

Normal Flow:

1. User selects “Add Achievement.”
2. System displays form for title, description, and image.
3. User submits details.
4. System validates and stores the achievement.
5. System displays it on the “Achievements” page.

Alternative Flow:

• Image upload fails → show “Image format not supported.”

Exception Flow:

• Server issue → show “Unable to save achievement.”

UC7: Donation Management

Actors: Alumni, Student
Description:
Allows alumni to create donation campaigns and users to contribute.

Precondition:
User must be logged in.

Postcondition:
Donation records and totals are stored successfully.

Normal Flow:

1. Alumni selects “Create Donation Card.”
2. Alumni enters title, purpose, and goal amount.
3. System validates and publishes the campaign.
4. Other users click “Donate” and enter payment details.
5. System records transaction and updates total.

Alternative Flow:

• Invalid amount or incomplete form → show “Please enter valid details.”

Exception Flow:

• Payment gateway error → show “Transaction failed.”

UC8: Data Viewing and Search

Actors: Student, Alumni
Description:
Allows users to search and view announcements, events, jobs, and achievements.

Precondition:
User must be logged in.

Postcondition:
Search results are displayed dynamically.

Normal Flow:

1. User selects “Search.”
2. User enters keyword or category.
3. System retrieves matching data.
4. System displays relevant results.

Alternative Flow:

• No results → show “No matching records found.”

Exception Flow:

• Database connection lost → show “Unable to fetch results.”

UC9: Photo Gallery Management

Actors: Student, Alumni
Description:
Allows users to upload, view, and delete gallery images.

Precondition:
User must be logged in.

Postcondition:
Images are stored or removed successfully.

Normal Flow:

1. User navigates to “Gallery.”
2. User selects “Upload Photo.”
3. System prompts to choose image file.
4. User confirms upload.
5. System validates image format and size.
6. System stores image and displays it in gallery.
7. User can delete uploaded photos.

Alternative Flow:

• Unsupported format → show “Please upload JPG or PNG image.”

Exception Flow:

• Server or storage error → show “Upload failed. Try again later.”