Collegiate Sports Paging System

Use Case Specification: Approve Story

Version 1.0

Revision History

Date

Version

Description

Author

October 9, 1999 1.0 Initial version Context Integration
Table of Contents

Approve Story Top of page

Brief Description

This Use Case takes place when an editor approves a story for inclusion in the Collegiate Sports Paging System. Some stories will automatically propogate from the existing system, but some stories will require editor intervention (either because their subject is not clear or the categories to which the story belongs are not clear). This flow is also used to approve advertising content being posted.

Flow of Events Top of page

Basic Flow

  1. The system places a story in the editor’s "to-do" workflow.
  2. The editor views the story.
  3. The editor categorizes the story and marks it approved.
  4. The system includes the story and triggers initiation of paging messages.

Alternate Flows

  1. Reject Content
    1. The editor views the story.
    2. The editor marks the story as rejected
    3. The system notifies the originator of the content that the story has been rejected
  2. Modify Content
    1. Editor selects "Modify Story"
    2. System displays titles of all stories available
    3. Editor selects specific title
    4. System displays characteristics of story
    5. Editor updates characteristics
    6. Editor selects "Save"
    7. System re-posts story, triggering paging activity as needed
  3. Approve Advertising Content
    1. The editor views the advertising content
    2. The editor marks it approved.
    3. The system includes the advertising content for display
    4. The system marks the preliminary billing record as approved
  4. Reject Advertising Content
    1. The editor views the advertising content
    2. The editor marks it rejected and provides a reason for rejection
    3. The system notifies the advertiser (via email) of the rejection and the reason
  5. Story not viewable

    If the story has been deleted by another editor and is not currently viewable, the use case terminates.

Special Requirements Top of page

Special requirements will be determined during the next iteration.

Preconditions Top of page

Editor must be logged in.

Postconditions Top of page

Postconditions will be determined during the next iteration.

Extension Points Top of page

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

Copyright  © 1987 - 2001 Rational Software Corporation