Course Registration System
Use-Case Specification
Submit Grades Use Case
Version 2.0
Revision History
Date
|
Version
|
Description
|
Author
|
21/Dec/98 |
Draft |
Draft Version |
S. Gamble |
15/Feb/1999 |
Version 1.0 |
Minor corrections based on
review. |
S. Gamble |
19/Feb/1999 |
Version 2.0 |
Modify section on use case
extends. Final cleanup. Add alternate flows. Resolve outstanding issues. |
S. Gamble |
|
|
|
|
Table of Contents
- Brief Description
- Flow of Events
- 2.1 Basic Flow - Submit Grades
- 2.2 Alternative Flows
-
2.2.1 No Courses Taught
-
2.2.1 Course Cancelled
- Special Requirements
- Preconditions
- 4.1 Login
- Postconditions
- Extension Points
Submit
Grades Use Case
- Brief Description
This use case allows a Professor to submit student grades for one or more
classes completed in the previous semester.
The actor in this use case is the Professor.
2. Flow
of Events
The use case begins when the Professor selects the "submit grades"
activity from the Main Form.
2.1 Basic
Flow - Submit Grades
- The system displays a list of course offerings the
Professor taught in the previous semester.
- The Professor selects a course offering.
- The system retrieves a list of all students who were
registered for the course offering. The system also retrieves the grade
information for each student in the offering.
- The system displays each student and any grade that was
previously assigned for the offering.
- For each student on the list, the Professor enters a
grade: A, B, C, D, F, or I. The system records the student's grade for
the course offering. If the Professor wishes to skip a particular student,
the grade information can be left blank and filled in at a later time. The
Professor may also change the grade for a student by entering a new grade.
2.2 Alternative
Flows
2.2.1 No Courses Taught
If in the basic flow, the Professor did not teach any course offerings
in the previous semester the system displays an error message and the use
case ends.
2.2.2 Course Cancelled
If too many students withdrew from the course during the add/drop period
and the course was cancelled after the beginning of the semester, the system
displays an error message. If the Professor chooses to cancel the operation
the use case terminates, otherwise is restarted at step 2 of the basic flow.
3. Special
Requirements
There are no special
requirements associated with this use case.
4.
Preconditions
4.1 Login
Before this use case begins the Professor has logged onto the system.
5.
Postconditions
There are no
postconditions associated with this use case.
6. Extension Points
There are no extension points associated with this use case.
|