**Collegiate Sports Paging System

Use Case Specification: Send Content**

Version 1.0

Revision History

Table of Contents

• [Send Content](#Send Content)
• [Flow of Events](#Flow of Events)
• [Special Requirements](#Special Requirements)
• Preconditions
• Postconditions
• [Extension Points](#Extension Points)

Send Content

Brief Description

This use case occurs when content is posted to the existing WebNewsOnLine web site. Some stories will be tagged for transmission to the Collegiate Sports Paging System, and will be sent for possible paging and display.

Flow of Events

Basic Flow

1. The use case begins when a content editor places content on WebNewsOnLine web site.
2. WebNewsOnLine system checks categorization and/or headline of content just posted.
3. System checks reference information to determine whether this content category is known by the Collegiate Sports Paging System.
4. For categories that are known by the Collegiate Sports Paging System, stories are transmitted to the Collegiate Sports Paging System along with category information.
5. Content is placed into the Collegiate Sports Paging System storage for possible paging.

Alternate Flows

Content is not categorized

If the content is not categorized, the story is placed in the editor’s “to-do” workflow.

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.