Collegiate Sports Paging System

Supplementary Specification

Version 2.0

 Revision History

Date

Version

Description

Author

October 10, 1999 1.0 Initial version Context Integration
December 2, 1999 2.0 Update following Elaboration phase Context Integration
Table of Contents

Introduction Top of page

Purpose

The 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.

Scope

This 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 Abbreviations

See Glossary.

References

  1. CSPS Vision 1.0
  2. CSPS Requirements Management Plan 1.0
  3. CSPS Creative Design Brief 1.0
  4. CSPS Design Comps 1.0

Functionality Top of page

Functional requirements are captured via the defined use cases.

Usability Top of page

Ease of use

The system will not require user training beyond that of using a web browser. This will be verified by usability tests during the beta period.

Reliability Top of page

Availability

The system will be available 24 hours per day, 7 days per week.

Performance Top of page

Subscriber volume

The system will be able to support 200,000 subscribers, and provide a scaling mechanism to handle 500,000 subscribers.

Paging latency

When a news story is posted to the system, pages must be transmitted to the pager gateway within 5 minutes.

Supportability Top of page

Subscriber software

The 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 Constraints Top of page

WebNewsOnLine Look and Feel

The system shall conform with existing WebNewsOnLine web site design standards.

WebNewsOnLine existing system connection

The system shall communicate with the existing WebNewsOnLine web site for the purpose of receiving story content.

Online User Documentation and Help System Requirements Top of page

Each major function provided by the system will have its own online help function.

Purchased Components Top of page

None.

Interfaces Top of page

User Interfaces

See Creative Design documents (references 4, 5, and 6).

Hardware Interfaces

No custom hardware interfaces are required.

Software Interfaces

The system will interconnect with the existing WebNewsOnLine system to receive content.

Communications Interfaces

The system requires no custom communications interfaces.

Licensing Requirements Top of page

No client licenses are required.

Legal, Copyright, and Other Notices Top of page

Copyright statements indicating content ownership shall be included in content as required by policy.

Applicable Standards Top of page

To be defined in subsequent phases.

Copyright  © 1987 - 2001 Rational Software Corporation

Display Rational Unified Process using frames

Rational Unified Process