Create a use case $($using the full template$)$ to describe the interactions of what Flagler students need to do to register a course online via my$.$flagler.edu. This use case is for registering one course, not for registering a full set of courses.

Assuming that $($preconditions$)$:

The student has met the advisor and has been cleared for online registration.

My$.$flagler.edu is available online.

The student is authenticated when logging to my$.$flagler.edu.

The online register system should allow students to search for available courses. Course offerings, schedules and seats availability are provided by Course Offering data store $($list of classes and schedules$)$ and Registration data store $($current registration status, seat available or full$).$

Student who has any unpaid fees or has a hold on the account is not permitted to register. $($Business Office Data Store$)$

The system should prevent students from registering$/$adding a class:

When class is full $($waitlist is available to be added in$)$

When there is a schedule conflict with student$$s existing schedule

When student does not meet the prerequisite requirements $($check with Student Academic Record data store$)$

The system should also ensure that no student takes too many courses $(19$ credits maximum$).$

The system should update the schedule $($Registration data store and Student Academic Record data store$)$ at once when a student successfully registers$/$adds a course.

Here is the Use Case Template. You can skip the ID because this is stand$-$alone use case, not included in a set of use cases.

Fill out the template based on the information provided $($there is no need for the codes$).$ Base it off of registering for only one class NOT a full schedule.