**Collegiate Sports Paging System
Use Case Specification: Read Content on Web Site**
Version 2.0
Revision History
| Date | Version | Description | Author |
| October 9, 1999 | 1.0 | Initial version | Context Integration |
| December 1, 1999 | 2.0 | Updated after Elaboration | Context Integration |
Table of Contents
- [Read Content on Web Site](#Read Content on Web Site)
- [Flow of Events](#Flow of Events)
- [Special Requirements](#Special Requirements)
- Preconditions
- Postconditions
Read Content on Web Site
Brief Description
This use case occurs when an active subscriber or unregistered user connects to the system to view information.
Flow of Events
Basic Flow
- System scans “archived” list of content. Content subscribed to remains in a user’s “unread” category until the story has been viewed. Once the story has been viewed, the story is marked as “archived” for that subscriber. After two days in the “archived” category, the story is removed from the subscriber’s “archived” category. For any stories older than 2 days, the story is moved back into the general category and the reference count attribute of the content object is decremented.
- When a story is no longer referenced by any subscribers’ “unread” or “archived” category (reference count is 0), the system deletes the story.
- System displays banner ads, general content categories, and specific stories for which pages have been sent.
- Subscriber views stories.
- For any paged stories, the stories are marked as viewed and placed into the “archived” category.
Alternate Flows
-
User is not registered subscriber
-
System displays banner ads and general content categories
-
System provides the option for the user to subscribe
-
User views stories
-
Content is obsolete
If this content has a pending view count of 0 and the last date viewed is more than 2 days ago, the content is deleted.
Special Requirements
None.
Preconditions
None.
Postconditions
None.