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

**Collegiate Sports Paging System

Use Case Specification: Approve Story**

Version 1.0

Revision History
DateVersionDescriptionAuthor
October 9, 19991.0Initial versionContext Integration
Table of Contents
  • [Approve Story](#Approve Story)
  • [Flow of Events](#Flow of Events)
  • [Special Requirements](#Special Requirements)
  • Preconditions
  • Postconditions
  • [Extension Points](#Extension Points)

Approve Story

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

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

  2. The editor views the story.

  3. The editor marks the story as rejected

  4. The system notifies the originator of the content that the story has been rejected

  5. Modify Content

  6. Editor selects “Modify Story”

  7. System displays titles of all stories available

  8. Editor selects specific title

  9. System displays characteristics of story

  10. Editor updates characteristics

  11. Editor selects “Save”

  12. System re-posts story, triggering paging activity as needed

  13. Approve Advertising Content

  14. The editor views the advertising content

  15. The editor marks it approved.

  16. The system includes the advertising content for display

  17. The system marks the preliminary billing record as approved

  18. Reject Advertising Content

  19. The editor views the advertising content

  20. The editor marks it rejected and provides a reason for rejection

  21. The system notifies the advertiser (via email) of the rejection and the reason

  22. Story not viewable

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

Special Requirements

Special requirements will be determined during the next iteration.

Preconditions

Editor must be logged in.

Postconditions

Postconditions will be determined during the next iteration.

Extension Points

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