Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Example: Submit Grades Use Case Specification

Course Registration System

Use-Case Specification

Submit Grades Use Case

Version: Draft

Revision History

DateVersionDescriptionAuthor
21/Dec/98DraftDraft VersionS. Gamble

Table of Contents

  1. Brief Description
  2. Flow of Events

    2.1    Basic Flow - Submit Grades

    2.2    Alternative Flows

  3. Special Requirements
  4. Preconditions

    4.1    Login

  5. Postconditions
  6. 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

  1. The system displays a list of course offerings the Professor taught in the previous semester.
  2. The Professor selects a course offering.
  3. 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.
  4. The system displays each student and any grade that was previously assigned for the offering.
  5. 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

Issue: Error conditions for this use case have not been analyzed and need to be added here.

3.    Special Requirements

Special requirements will be determined during the next iteration.

4.    Preconditions

4.1    Login

Before this use case begins the Professor 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.