Example: Close Registration Use Case Specification

Course Registration System

Use-Case Specification Close Registration Use Case

Version: Draft

Revision History

Table of Contents

1. Brief Description

2. Flow of Events

   2.1    Basic Flow - Successful Close Registration

   2.2    Alternative Flows

   2.2.1    No Professor for the Course Offering

   2.2.2    Billing System Unavailable
3. Special Requirements

4. Preconditions

   4.1    Login

5. Postconditions
6. Extension Points

Close Registration Use Case

- Brief Description

This use case allows a Registrar to close the registration process. Course offerings that do not have enough students are cancelled. Course offerings must have a minimum of three students in them. The billing system is notified for each student in each course offering that is not cancelled, so the student can be billed for the course offering.

The main actor of this use case is the Registrar. The Billing System is an actor involved within this use case.

2.    Flow of Events

The use case begins when the Registrar selects the “close registration” activity from the Main Form.

2.1    Basic Flow - Successful Close Registration

1. The system checks to see if a Registration is in progress. If it is, then a message is displayed to the Registrar and the use case terminates. The Close Registration processing cannot be performed if registration is in progress. .
2. For each open course offering, the system checks if three students have registered and a professor has signed up to teach the course offering. If so, the system closes the course offering and sends a transaction to the billing system for each student enrolled in the course offering.

Issue: Check with Registrar Office if courses should proceed with 3 students enrolled. Should it be a larger number?

2.2    Alternative Flows

2.2.1No Professor for the Course Offering

If in the basic flow there is no professor signed up to teach the course offering, the system will cancel the course offering. The Cancel Course Offering sub-flow is executed at this point.

2.2.2Billing System Unavailable

If the system is unable to communicate with the Billing System, the system will attempt to re-send the request after a specified period. The system will continue to attempt to re-send until the Billing System becomes available

Issues:

Need to resolve what to do if too few students registered for a course.

3.    Special Requirements

Special requirements will be determined during the next iteration.

4.    Preconditions > 4.1    Login

The Registrar must be logged onto the system in order for this use case to begin.

5.    Postconditions

Postconditions will be determined during the next iteration.

6.    Extension Points

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