Use Case Template

Prepared by:

Man0war777

Use case name: View courses offered by the department

Primary actor(s): Academic Staff

Brief description: The staff will be able to view the courses offered by the department upon logging into the system.

Preconditions (what must be true before the use case can start): The staff must first log in to the University’s online registration system; the system then authenticates the staff’s information before granting access.

Postconditions (what must be true when the use case ends): All courses offered by the department must be displayed.

Normal Flow of Events 1. The staff logs into the University’s registration system using a username and password

2. The system authenticates the staff’s log in information

3. At the main menu, the various departments are displayed

4. The staff selects its department, and a list of all courses offered in the department is displayed

Alternative flows (show each separately and tie to Normal Flow of Events)

Exceptional Flows: If staff enters an incorrect log in information, the system will prompt for the correct information. After the third trial, the system will lock the user out and inform the user to contact the administrator.

Prepared by:

Man0war777

Use case name: Add or remove courses offered by the department for the semester

Primary actor(s): Academic Staff

Brief description: At the add/remove courses screen, the staff is able to add or courses offered for the semester or remove the ones not offered for the same semester.

Preconditions (what must be true before the use case can start): The courses to be added or deleted must be available for the staff to proceed. In other words, if the staff wants to remove a course from the list, the course must already be in the system for this task to be performed.

Postconditions (what must be true when the use case ends): The course(s) to be added must be updated on the system, likewise the one(s) to be removed.

Normal Flow of Events 1. After logging into the system with the main menu displayed, the staff selects the applicable department

2. The system displays a list of courses offered by the department

3. To remove a course, the staff selects the applicable course(s) to be removed from the Add/Remove Course window

4. Clicks the Remove Course button

5. The system updates the database upon removing the course

6. To add a course, the staff selects a course from a list of available courses in the Add/Remove Course window

7. Clicks on the Add Course button

8. The system removes the course from the list and updates the database

Alternative flows (show each separately and tie to Normal Flow of Events) If a new course is to be introduced in the department and needed to be added to the system, the staff will click on the Add New Course button, which will bring up an Add New Course window. Here, the staff enters the course information in the necessary toolboxes provided, and the system updates the list of courses offered by the department.

Exceptional Flows: If the staff inputs an incorrect course while trying to add, the system should display an error message. For example, “Course not found, Do you want to add course?

Prepared by:

Man0war777

Use case name: Changing course information

Primary actor(s): Academic Staff

Brief description: The staff will be able to modify information about the courses offered using the Course Change screen.

Preconditions (what must be true before the use case can start):

Postconditions