Collegiate Sports Paging System Iteration Assessment Version 1.0 Revision History
Date | Version | Description | Author
--- | --- | --- | ---
November 12, 1999 | 1.0 | Initial version | Context Integration
#### Table of Contents Introduction Iteration Objectives Reached Adherence to Plan Use Cases and Scenarios Implemented Results Relative to Evaluation Criteria Test Results External Changes Occurred Rework Required ### Introduction #### Purpose The objective of the Iteration Assessment is to capture the result of the iteration, the degree to which the evaluation criteria were met, and lessons learned and changes to be done. #### Scope This Iteration Assessment applies to the Elaboration Iteration. The Elaboration Iteration developed the requirements and design for the initial implementation of the Collegiate Sports paging System. The success of the Elaboration Iteration is measured against the evaluation criteria as outlined in the Elaboration Iteration Plan. #### Definitions, Acronyms and Abbreviations See Glossary. #### References CSPS Vision 1.0 CSPS Iteration Plan 1.0 CSPS Design Comps 1.0 CSPS Use Case - Approve Story 1.0 CSPS Use Case - Edit Profile 1.0 CSPS Use Case - Pay Fee With Credit Card 1.0 CSPS Use Case - Print Advertiser Reports 1.0 CSPS Use Case - Provide Advertising Content 1.0 CSPS Use Case - Provide Feedback 1.0 CSPS Use Case - Read Content on Website 1.0 CSPS Use Case - Send Content 1.0 CSPS Use Case - Send Page 1.0 CSPS Use Case - Subscribe 1.0 CSPS Glossary 1.0 ### Iteration Objectives Reached Architectural prototype developed, major risks validated, designs completed for all use cases. ### Adherence to Plan This iteration executed according to plan. ### Use Cases and Scenarios Implemented No new use cases were identified. The following use cases were completed with details uncovered during the design process: Approve Story Edit Profile Pay Fee With Credit Card Print Advertiser Reports Provide Feedback Read Content on Web Site Send Content Send Page Subscribe ### Results Relative to Evaluation Criteria
Criterion | Evaluation
--- | ---
Complete the analysis and design of selected use cases. | All selected use cases designed.
Develop a working architectural prototype. | Prototype available for user evaluation.
Realize risk associated with the architectural design or system performance. | Performance risk under load exposed, plan developed for dealing with load.
Each deliverable developed during the iteration will be peer reviewed and subject to approval from the team. | Peer reviews took place as planned (project documentation contains review summaries).
### Test Results During load testing, results indicate that a multi-tiered pager gateway approach will be needed to handle peak traffic loads. Subscriber, editor, and advertising representatives approved the user interface as designed. ### External Changes Occurred All major alphanumeric pager vendors now offer an email interface for sending alphanumeric pages. ### Rework Required None. Copyright 1987 - 2003 Rational Software Corporation |  |