Example: Register for Courses Use Case Specification

Course Registration System

Use-Case Specification

Register for Courses Use Case

Version: Draft

Revision History

Table of Contents

1. Brief Description

2. Flow of Events

   2.1    Basic Flow - Create a Schedule

   2.2    Alternative Flows

   2.2.1    Modify a Schedule

   2.2.2    Delete a Schedule

   2.2.3    Course Catalog System Unavailable
3. Special Requirements
4. Preconditions
   1. Login
5. Postconditions
6. Extension Points

Register for Courses Use Case

- Brief Description

This use case allows a Student to register for course offerings in the current semester. The Student can also modify or delete course selections if changes are made within the add/drop period at the beginning of the semester. The Course Catalog System provides a list of all the course offerings for the current semester.

The main actor of this use case is the Student. The Course Catalog System is an actor within the use case.

2.    Flow of Events

The use case begins when the Student selects the “maintain schedule” activity from the Main Form.

2.1    Basic Flow - Create a Schedule

1. The Student selects “create schedule.”
2. The system displays a blank schedule form.
3. The system retrieves a list of available course offerings from the Course Catalog System.
4. The Student selects 4 primary course offerings and 2 alternate course offerings from the list of available offerings. Once the selections are complete the Student selects “submit.”
5. Courses are added for each selected course offering.
6. The system saves the schedule.

2.2 Alternative Flows

   2.2.1Modify a Schedule

TBD.

2.2.2Delete a Schedule

TBD.

2.2.3Course Catalog System Unavailable

If, the system is unable to communicate with the Course Catalog System after a specified number of tries, the system will display an error message to the Student. The Student acknowledges the error message and the use case terminates.

3.    Special Requirements

Special requirements will be determined during the next iteration.

   4.    Preconditions

4.1    Login

Before this use case begins the Student has logged onto the system.

5.    Postconditions

Postconditions will be determined during the next iteration.

6.    Extension Points

1. Extension points of the business use case will be identified during the Elaboration Phase.