Collegiate Sports Paging System Supplementary Specification Version 1.0 Revision History
Table of Contents
IntroductionPurposeThe purpose of this document is to define requirements of the Collegiate Sports Paging System. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use-case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system. ScopeThis Supplementary Specification applies to the Collegiate Sports Paging System which will be developed by Context Integration. The Collegiate Sports Paging System will allow subscribers to be notified via alphanumeric pager (or cellular phone or email) of events in specific areas of interest, then to access content via an individualized web interface. This specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability as well as functional requirements that are common across a number of use cases. (The functional requirements are defined in the Use Case Specifications.) Definitions, Acronyms and AbbreviationsSee Glossary. ReferencesFunctionalityFunctional requirements are captured via the defined use cases. UsabilityEase of useThe system will not require user training beyond that of using a web browser. This will be verified by usability tests during the beta period. ReliabilityAvailabilityTo be defined in subsequent phases. PerformanceSubscriber volumeThe system will be able to support 200,000 subscribers, and provide a scaling mechanism to handle 500,000 subscribers. Paging latencyWhen a news story is posted to the system, pages must be transmitted to the pager gateway within 5 minutes. SupportabilitySubscriber softwareThe subscriber shall be able to utilize the system through commercially available browser software. No custom software will be required to reside on the subscriber’s PC. Design ConstraintsWebNewsOnLine Look and Feel
WebNewsOnLine existing system connection
Online User Documentation and Help System RequirementsEach major function provided by the system will have its own online help function. Purchased ComponentsTo be defined in subsequent phases. InterfacesUser InterfacesSee Creative Design documents: Hardware InterfacesTo be defined in subsequent phases. Software InterfacesTo be defined in subsequent phases. Communications InterfacesTo be defined in subsequent phases. Licensing RequirementsNo client licenses are required. Legal, Copyright, and Other NoticesCopyright statements indicating content ownership shall be included in content as required by policy. Applicable StandardsTo be defined in subsequent phases. Copyright © 1987 - 2001 Rational Software Corporation
| |
Rational Unified Process |