Collegiate Sports Paging System Use Case Model Survey Version 1.0 Revision History
Table of Contents
Use Case Model Survey IntroductionPurposeThis report describes the use-case model comprehensively, in terms of how the model is structured into packages and what use cases and actors there are in the model. ScopeThis Use Case Model Survey applies to the Collegiate Sports Paging System, which will be developed by Context Integration. This system will allow subscribers to be notified of events relating to collegiate sports events or teams to which they subscribe, and will enable them to view the content they have subscribed to. Definitions, Acronyms and AbbreviationsSee Glossary. ReferencesNone. Actor Catalog
Approve StoryBrief DescriptionThis 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 EventsBasic Flow
Alternate Flows
If the story has been deleted by another editor and is not currently viewable, the use case terminates. Special RequirementsSpecial requirements will be determined during the next iteration. PreconditionsEditor must be logged in. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
Edit ProfileBrief DescriptionThis use case occurs when a subscriber wishes to change their profile information or when a new subscriber wishes to enroll. Flow of EventsBasic Flow
Alternate FlowsIf this is a new subscriber, the use case "Pay Fee with Credit Card" is invoked following step 5 above. Special RequirementsSpecial requirements will be determined during the next iteration. This needs to be secured as credit card information may be in the profile. PreconditionsPreconditions will be determined during the next iteration. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase. Pay Fee With Credit CardBrief DescriptionThis use case occurs when a new subscriber wants to pay their annual subscription fee by specifying a credit card number and PIN. This may also occur when an existing subscriber wants to renew (see alternate flow 1) Flow of EventsBasic Flow
Alternate FlowsSubscriber renews subscriptionWhen this occurs, the flow runs as follows:
Invalid credit card informationIf the information provided by the subscriber is not validated by the external system, an error message will be displayed and the subscriber record will NOT be updated (so that the last steps in the above flows will not be executed). Special RequirementsSpecial requirements will be determined during the next iteration. Issue – interface specifications for external credit card system need to be verified. PreconditionsPreconditions will be determined during the next iteration. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
Print Advertiser ReportsBrief DescriptionThis 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 EventsBasic Flow
Alternate FlowsNone Special RequirementsSpecial 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? PreconditionsUser is connected and validated as an advertiser. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
Provide FeedbackBrief DescriptionThis use case occurs when a system user (advertiser, subscriber, or potential subscriber) wishes to comment on the service or the web site. Flow of EventsBasic Flow
Alternative FlowsNone Special RequirementsSpecial requirements will be determined during the next iteration. PreconditionsPreconditions will be determined during the next iteration. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
Post Advertising ContentBrief DescriptionThis 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 EventsBasic Flow
Alternative FlowInvalid Account Information
Special RequirementsSpecial requirements will be determined during the next iteration. PreconditionsUser is connected and validated as an advertiser. Advertiser account exists. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
Read Content on Web SiteBrief DescriptionThis use case occurs when an active subscriber or unregistered user connects to the system to view information. Flow of EventsBasic Flow
Alternate FlowsUser is not registered subscriber
Special RequirementsSpecial requirements will be determined during the next iteration. PreconditionsNone. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
Send ContentBrief DescriptionThis 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 EventsBasic Flow
Alternate FlowsContent is not categorized
Special RequirementsSpecial requirements will be determined during the next iteration. PreconditionsEditor must be logged in. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
Send PageBrief DescriptionThis use case occurs when new content is posted to the Collegiate Sports Paging System. Flow of EventsBasic Flow
Alternate FlowsNone. Special RequirementsSpecial requirements will be determined during the next iteration. PreconditionsContent is posted, headline is available, categorization is available. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase.
SubscribeBrief DescriptionThis use case occurs when a potential subscriber wants to subscribe to the service. Flow of EventsBasic Flow
Alternative FLowsUser rejects contract termsIf the potential subscriber does not acknowledge the contract terms, the use case terminates. Special RequirementsSpecial requirements will be determined during the next iteration. PreconditionsNone. PostconditionsPostconditions will be determined during the next iteration. Extension PointsExtension points of the use case will be identified during the Elaboration Phase. Copyright © 1987 - 2001 Rational Software Corporation
| |
Rational Unified Process |