1. Brief Description
2. Flow of Events

   2.1    Basic Flow - Add a Professor

   2.2    Alternative Flows

                       2.2.1    Modify and Delete a Professor

3. Special Requirements
4. Preconditions

   4.1    Log In

5. Postconditions
6. Extension Points

1. Brief Description

This use case allows the Registrar to maintain professor information in the registration system. This includes adding, modifying, and deleting professors from the system.

The actor of this use case is the Registrar.

The use case begins when the Registrar selects the "maintain professor" activity from the Main Form.

2.1    Basic Flow - Add a Professor

1. The Registrar selects "add a professor."
2. The system displays a blank professor form.
3. The Registrar enters the following information for the professor: name, date of birth, social security number, status, and department.
4. The system validates the data to insure the proper data format and searches for an existing professor with the specified name. If the data is valid the system creates a new professor and assigns a unique system-generated id number. This number is displayed, so it can be used for subsequent uses of the system.
5. Steps 2-4 are repeated for each professor added to the system. When the Registrar is finished adding professors to the system the use case ends.

2.2    Alternative Flows

        2.2.1    Modify and Delete a Professor

TBD

Special requirements will be determined during the next iteration.

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

Postconditions will be determined during the next iteration.

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