Use Case Description
Complete Use Case Descriptions - Course Management
System
1. Use Case: Login
• Introduction:
Allows a user (Student, Faculty, or Admin) to log into the system using valid credentials.
• Actors:
Student
Faculty
Admin
• Pre-Conditions:
User must be registered in the system.
System must be online.
• Post-Conditions:
On success: user is redirected to the appropriate dashboard.
On failure: error is shown and attempt logged.
• Flow of Events:
Basic Flow
1. User enters username and password.
2. System validates credentials.
3. If valid, user is directed to their dashboard.
Alternate Flow
1. If credentials are incorrect, an error is shown.
• Special Requirements:
None
2. Use Case: View and Modify Personal Information
• Introduction:
Allows Students and Faculty to view and update their profile information.
• Actors:
Student
Faculty
• Pre-Conditions:
User must be logged in.
Profile exists in the system.
• Post-Conditions:
Profile is displayed or updated based on user's action.
• Flow of Events:
Basic Flow
1. User navigates to profile section.
2. System displays current profile info.
3. User edits and submits changes.
4. System validates and updates the information.
Alternate Flow
1. If input is invalid (e.g. missing required fields), system displays an error.
2. Changes are rejected until valid data is entered.
• Special Requirements:
Data validation rules for profile fields.
• Use Case Relationships:
None
3. Use Case: Choose Courses
• Introduction:
Allows a student to view available courses and enroll in selected ones.
• Actors:
Student
• Pre-Conditions:
Student must be logged in.
Courses are available for registration.
• Post-Conditions:
Course is added to the student’s list of enrolled courses.
• Flow of Events:
Basic Flow
1. Student views list of available courses.
2. Student selects a course to enroll in.
3. System validates eligibility.
4. Student is successfully enrolled.
Alternate Flow
1. If prerequisites are not met, enrollment is denied.
2. If course is full, student is notified.
• Special Requirements:
Course enrollment rules, seat limits, and prerequisite checks.
• Use Case Relationships:
None
4. Use Case: Add, Modify, and Remove Courses
• Introduction:
Allows the Admin to manage the course catalog.
• Actors:
Admin
• Pre-Conditions:
Admin must be authenticated.
• Post-Conditions:
Courses are created, modified, or removed.
• Flow of Events:
Basic Flow
1. Admin adds/modifies/removes course details.
2. System validates and performs the operation.
3. Course list is updated.
Alternate Flow
1. If data is incomplete or invalid, operation is rejected.
2. If course is linked to enrolled students, removal is denied.
• Special Requirements:
Validation rules, dependency checks.
• Use Case Relationships:
None
[Link] Case: Add Attendance
• Introduction:
Allows faculty to mark attendance for their assigned courses.
• Actors:
Faculty
• Pre-Conditions:
Faculty is logged in and assigned to a course.
Students are enrolled in the course.
• Post-Conditions:
Attendance is recorded for the session.
• Flow of Events:
Basic Flow
1. Faculty selects course and date.
2. Faculty marks attendance.
3. System saves attendance.
Alternate Flow
1. If course is not assigned, access is denied.
2. If system fails to save, an error is shown.
• Special Requirements:
None
• Use Case Relationships:
None
[Link] Case: Prepare and Modify Results
• Introduction:
Allows faculty to prepare and modify student results for their courses.
• Actors:
Faculty
• Pre-Conditions:
Faculty is assigned to course.
Students have completed assessments.
• Post-Conditions:
Results are saved or updated.
• Flow of Events:
Basic Flow
1. Faculty enters marks for students.
2. System calculates grades.
3. Results are stored.
Alternate Flow
1. If invalid data is entered, system rejects input.
2. If submission is incomplete, save is blocked.
• Special Requirements:
Grade calculation logic.
• Use Case Relationships:
None
[Link] Case: Request and View Results
• Introduction:
Allows students to view their academic results.
• Actors:
Student
• Pre-Conditions:
Results must be published.
• Post-Conditions:
Student views result.
• Flow of Events:
Basic Flow
1. Student requests result.
2. System retrieves and displays the result.
Alternate Flow
1. If result is not yet published, user is notified.
• Special Requirements:
None
• Use Case Relationships:
Extends: Print