Use Case: Login

Description: The user logs into the department portal to access personal and academic information.

Actors:

$-$ Student

$-$ Instructor

Preconditions:

$-$ The portal is accessible.

Main Flow:

$1.$ User enters username and password.

$2.$ System validates credentials.

$3.$ If valid, user is logged in$.$

Postconditions:

$-$ User gains access to the portal.

$---$

Use Case: Course Registration

Description: The student registers for courses, either online or manually with an instructor.

Actors:

$-$ Student

$-$ Instructor

Preconditions:

$-$ Student is logged into the portal.

Main Flow:

$1.$ Student selects courses for registration.

$2.$ System checks eligibility based on GPA and academic level.

$3.$ If eligible, student completes registration.

$4.$ Instructor manually registers students for courses.

Postconditions:

$-$ Student is registered for selected courses.

$---$

Use Case: Update Profile

Description: The user updates personal information in the portal.

Actors:

$-$ Student

$-$ Instructor

Preconditions:

$-$ User is logged into the portal.

Main Flow:

$1.$ User navigates to the profile update section.

$2.$ User modifies personal information.

$3.$ System validates changes and updates the profile.

Postconditions:

$-$ User's profile is updated with new information.

$---$

Use Case: Search Course

Description: The user searches for courses within the portal.

Actors:

$-$ Student

$-$ Instructor

Preconditions:

$-$ User is logged into the portal.

Main Flow:

$1.$ User enters search criteria $($e$.$g$.,$ course code, course name$).$

$2.$ System retrieves matching courses.

$3.$ User views the search results.

$**$Postconditions:$**$

$-$ User has information about the searched courses.

$---$

### Use Case: Email Confirmation

$**$Description:$**$ The system sends an email confirmation for a specific event $($e$.$g$.,$ registration, profile update$).$

$**$Actors:$**$

$-$ System

$**$Preconditions:$**$

$-$ Relevant event triggers email confirmation.

$**$Main Flow:$**$

$1.$ System generates an email confirmation.

$2.$ System sends the confirmation to the user's email.

$**$Postconditions:$**$

$-$ User receives an email confirming the action.

$---$

### Use Case: Course Confirmation

$**$Description:$**$ The system confirms a successful course registration.

$**$Actors:$**$

$-$ System

$**$Preconditions:$**$

$-$ Student has completed the course registration.

$**$Main Flow:$**$

$1.$ System generates a course confirmation message.

$2.$ System displays the confirmation to the student.

$**$Postconditions:$**$

$-$ Student receives confirmation of course registration.

$---$

### Use Case: Student Identity Validation

$**$Description:$**$ The system validates the identity of a student during a critical process.

$**$Actors:$**$

$-$ System

$-$ Student

$**$Preconditions:$**$

$-$ Student is engaged in a process requiring identity validation.

$**$Main Flow:$**$

$1.$ Student provides necessary identification information.

$2.$ System validates the identity through secure means.

$**$Postconditions:$**$

$-$ Process continues with confirmed student identity.

$---$

Use Case: Course Schedule Clash

Description:The system detects a schedule clash during course registration.

Actors:

$-$ System

$-$ Student

Preconditions:

$-$ Student is attempting to register for courses.

Main Flow:

$1.$ System checks the selected courses for schedule conflicts.

$2.$ If a clash is detected, system notifies the student.

Postconditions:

$-$ Student adjusts the course selection to resolve the conflict.

Use Case: Drop Course

Description: The student drops a registered course.

Actors:

$-$ Student

Preconditions:

$-$ Student is logged into the portal.

Main Flow:

$1.$ Student navigates to the course drop section.

$2.$ Student selects the course to drop.

$3.$ System confirms the course drop.

Postconditions:

$-$ Student is no longer registered for the dropped course.

Use Case: Add Course

Description: The student adds a new course to the registration.

Actors:

$-$ Student

Preconditions:

$-$ Student is logged into the portal.

Main Flow:

$1.$ Student navigates to the course add section.

$2.$ Student selects the course to add.

$3.$ System confirms the course addition.

Postconditions:

$-$ Student is registered for the added course.

Use Case: Course Availability

Description:The system checks and displays the availability of courses.

Actors:

$-$ Student

$-$ Instructor

Preconditions:

$-$ User is logged into the portal.

Main Flow:

$1.$ User views the list of available courses.

$2.$ System displays current course availability status.

Postconditions:

$-$ User has information about the availability of courses$\mathrm{.}9$:$54$

Ims$23-24$fall.emu.edu.tr

use case specification description $23\frac{27}{10}\frac{?}{2023}$

Use Case Name

Description $-$ a brief summary of what the use case is about

$\backslash$table$[[$Scenario$,\backslash$table$[[$A quick summary of what is going to happen in the use case $-],[$exclude actor$]]],[$Triggering event,$\backslash$table$[[$What the actor does in relation to the system $-$ should be first in$],[$flow of events$]]],[$Actors$,$List the primary actors $-$ the ones with their hands on the keyboard$]$Draw tables for the usecases below using the image for reference: