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: Post Advertising Content**

Version 2.0

Revision History

DateVersionDescriptionAuthor
October 9, 19991.0Initial versionContext Integration
December 1, 19992.0Updated after Elaboration phaseContext Integration
Table of Contents
  • [Provide Advertising Content](#Provide Advertising Content)
  • [Flow of Events](#Flow of Events)
  • [Special Requirements](#Special Requirements)
  • Preconditions
  • Postconditions
  • [Extension Points](#Extension Points)

Post Advertising Content

Brief Description

This use case occurs when an advertiser wants to post advertising content (banner ads) on the web site and specify which subscriber profiles should be used for display.

Flow of Events

Basic Flow

  1. Advertiser selects “Post Content”
  2. System validates account billing information to ensure new content will be accepted.  This consists of verifying that the advertiser account is in good standing (no outstanding balance over 30 days).
  3. System prompts for name of content.
  4. Advertiser uploads content in GIF format.
  5. System stores GIF in a staging area and records location and name of file.
  6. System acknowledges successful saving of content.
  7. System displays potential categories for ad display. Categories are maintained as a reference list within the system.
  8. Advertiser selects categories for which this ad should be shown.
  9. System displays potential frequencies and prices for the ad. Frequencies are maintained as a reference list, prices are based on advertiser’s contract with WebNewsOnLine.  Pricing codes are maintained as part of the [advertiser profile](ex_gloss2.md#Advertiser Profile).
  10. Advertiser selects desired frequency for this ad
  11. System creates preliminary billing record for this ad based on number of categories selected, frequency, and advertiser’s profile.
  12. System places content in editor’s “to-do” workflow queue for approval.   If more than one editor is defined, a round-robin approach is used to attempt to balance load.   Editors may be marked as unavailable (if, for instance, they are on vacation or sick or out of the office), in which case they will not be included in the round-robin process.

Alternative Flow

  1. Invalid Account Information

  2. Advertiser selects “Post Content”

  3. System validates account billing information to ensure new content will be accepted

  4. Account information is invalid, advertiser is prompted to contact WebNewsOnLine.   System presents central phone number for advertising department (stored in system).

Special Requirements

None.

Preconditions

User is connected and validated as an advertiser.

Advertiser account exists.

Postconditions

When this use case is complete, advertising content can be displayed.

Extension Points

None.