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
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
- The system places a story in the editor’s "to-do" workflow.
- The editor views the story.
- The editor categorizes the story and marks it approved.
- The system includes the story and triggers initiation of paging messages.
Alternate Flows
- Reject Content
- The editor views the story.
- The editor marks the story as rejected
- The system notifies the originator of the content that the story has
been rejected
- Modify Content
- Editor selects "Modify Story"
- System displays titles of all stories available
- Editor selects specific title
- System displays characteristics of story
- Editor updates characteristics
- Editor selects "Save"
- System re-posts story, triggering paging activity as needed
- Approve Advertising Content
- The editor views the advertising content
- The editor marks it approved.
- The system includes the advertising content for display
- The system marks the preliminary billing record as approved
- Reject Advertising Content
- The editor views the advertising content
- The editor marks it rejected and provides a reason for rejection
- The system notifies the advertiser (via email) of the rejection and the
reason
- 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.
Copyright
© 1987 - 2001 Rational Software Corporation
|
|