**Collegiate Sports Paging System

Use Case Specification: Print Advertiser Reports**

Version 1.0

Revision History

Table of Contents

• [Print Advertiser Reports](#Print Advertiser Reports)
• [Flow of Events](#Flow of Events)
• [Special Requirements](#Special Requirements)
• Preconditions
• Postconditions
• [Extension Points](#Extension Points)

Print Advertiser Reports

Brief Description

This use case occurs when an advertiser accesses the Collegiate Sports Paging System to obtain reports of how their advertising content has been viewed.

Flow of Events

Basic Flow

1. Advertiser selects “Print Reports”
2. System displays all advertising content provided by advertiser
3. Advertiser selects one or more pieces of content on which to report
4. System displays a list of reports for this advertiser
5. Advertiser selects one or more reports to generate
6. Advertiser selects format (Microsoft® Word®, Microsoft® Excel®, or to browser window)
7. System creates first report and prompts user to save or view
8. Advertiser saves or views report, selects “Next Report”
9. System creates next report and prompts user to save or view
10. Bullets 8) and 9) are repeated until no more reports remain

Alternate Flows

None

Special Requirements

Special requirements will be determined during the next iteration.

Issues - what do we do with obsolete content? How long will we allow reports to be run on content no longer available on the web site? Do we need to encrypt this transmission?

Preconditions

User is connected and validated as an advertiser.

Postconditions

Postconditions will be determined during the next iteration.

Extension Points

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