Course Registration System Use-Case Specification Register for Courses Use Case Version: Draft Revision History
Date | Version | Description | Author
--- | --- | --- | ---
21/Dec/98 | Draft | Draft Version | S. Gamble
Table of Contents Brief Description 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 Special Requirements Preconditions Login Postconditions 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 The Student selects "create schedule." The system displays a blank schedule form. The system retrieves a list of available course offerings from the Course Catalog System. 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." Courses are added for each selected course offering. The system saves the schedule. 2.2 Alternative Flows 2.2.1 Modify a Schedule TBD. 2.2.2 Delete a Schedule TBD. 2.2.3 Course 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 Extension points of the business use case will be identified during the Elaboration Phase.

| Copyright © IBM Corp. 1987, 2004. All Rights Reserved. | Course Registration Project Web Example Version 2001.03