Online Collegiate Paging System Iteration Plan Version 2.0 Revision History
Date | Version | Description | Author
--- | --- | --- | ---
October 6, 1999 | 1.0 | Initial version | Context Integration
October 27, 1999 | 2.0 | Updated at start of Elaboration | Context Integration
##### Table of Contents Introduction Plan Resources Use Cases Evaluation Criteria Iteration Plan ### Introduction #### Purpose This Iteration Plan describes the detailed plans for the Elaboration Iteration of the Collegiate Sports Paging System Project. During this iteration, the design of the system will be defined and the high level plan for execution of the full project will be refined. #### Scope The Elaboration Iteration Plan applies to the Collegiate Sports Paging System project being developed by Context Integration for WebNewsOnLine. This document will be used by the Project Manager and by the project team. #### Definitions, Acronyms and Abbreviations See Glossary document. #### References CSPS Iteration Plan 1.0.doc ### Plan The Elaboration Iteration will complete the analysis of requirements. The analysis and design for all use cases will be completed. The architectural prototype will be developed to test the feasibility and performance of the architecture that is required for Release 1.0. #### Iteration Tasks The following table illustrates the tasks with their planned start and end dates.
Task | Start | End
--- | --- | ---
ELABORATION | Mon 10/25/99 | Fri 11/26/99
Begin Elaboration | Mon 10/25/99 | Tue 10/26/99
Elaboration Kick-off | Tue 10/26/99 | Fri 10/29/99
Add tasks to project plan for specific project technology using ContextWISE cartridges | Fri 10/29/99 | Fri 10/29/99
Elaboration Kick-off Meeting | Tue 10/26/99 | Thu 10/28/99
Prepare for Elaboration Kick-off Meeting | Tue 10/26/99 | Tue 10/26/99
Hold Elaboration Kick-off Meeting | Tue 10/26/99 | Thu 10/28/99
Quality Assurance Plan created, reviewed, and signed off | Tue 10/26/99 | Tue 10/26/99
Elaboration Kick-off Completed | Thu 10/28/99 | Thu 10/28/99
Initial Web User Interface Prototypes & Style Guides | Fri 10/29/99 | Tue 11/2/99
Creative Brief updated, reviewed, and signed off | Fri 10/29/99 | Fri 10/29/99
Web design components created | Fri 10/29/99 | Tue 11/2/99
Web UI technical elements created | Fri 10/29/99 | Mon 11/1/99
Initial User Interface Prototype created, reviewed, and signed off | Fri 10/29/99 | Fri 10/29/99
Initial Report Prototype created, reviewed, and signed off | Fri 10/29/99 | Fri 10/29/99
User Interface Style Guide created, reviewed, and signed off | Fri 10/29/99 | Fri 10/29/99
Reports Style Guide created, reviewed, and signed off | Fri 10/29/99 | Fri 10/29/99
Update Software Project Log | Fri 10/29/99 | Mon 11/1/99
Initial Prototype & Style Guide Completed | Mon 11/1/99 | Mon 11/1/99
Documentation/Specifications, Help & Training Materials | Tue 11/2/99 | Fri 11/5/99
Determine Documentation/Specification/Help & Training Material Requirements | Tue 11/2/99 | Thu 11/4/99
Draft Initial User Manual/Specification/Help | Thu 11/4/99 | Fri 11/5/99
Draft Documentation Completed | Tue 11/2/99 | Tue 11/2/99
Detailed requirements development | Tue 11/2/99 | Thu 11/4/99
Complete Elaboration Use Case Model | Wed 11/3/99 | Wed 11/3/99
Use-Case-Model Survey created, reviewed, and signed off | Wed 11/3/99 | Wed 11/3/99
Supplementary Specifications updated, reviewed and baselined | Tue 11/2/99 | Tue 11/2/99
Project Glossary updated, reviewed, and signed off | Tue 11/2/99 | Wed 11/3/99
Site Map & Use-Case Navigation Mapping updated, reviewed, and signed off | Tue 11/2/99 | Wed 11/3/99
Content Plan updated, reviewed, and signed off (if applicable) | Tue 11/2/99 | Wed 11/3/99
Detailed user-interface prototype created, reviewed, and signed off | Tue 11/2/99 | Wed 11/3/99
Detailed reports prototype created, reviewed, and signed off | Tue 11/2/99 | Wed 11/3/99
User Manual/Specification/Help and Training created, reviewed, and signed off | Wed 11/3/99 | Wed 11/3/99
Obtain Sign-off | Wed 11/3/99 | Thu 11/4/99
Detailed requirements development complete | Thu 11/4/99 | Thu 11/4/99
Plans revised and updated | Thu 11/4/99 | Fri 11/5/99
Iterative Delivery Project Plan updated, reviewed, and signed off | Thu 11/4/99 | Thu 11/4/99
Software Development Plan created, reviewed, and signed off | Thu 11/4/99 | Thu 11/4/99
Knowledge Transfer Plan & Schedule updated, reviewed, and signed off | Thu 11/4/99 | Thu 11/4/99
Project estimates updated (accurate to +65%, -40%) | Thu 11/4/99 | Thu 11/4/99
Revise Business Case | Thu 11/4/99 | Thu 11/4/99
Reduce documentation staff (unless other significant documentation products will be produced) | Thu 11/4/99 | Thu 11/4/99
Documentation staff reduced after completing User Manual/Specification/Help (unless other significant documentation products will be produced) | Thu 11/4/99 | Fri 11/5/99
Elaboration Requirements Checkpoint | Fri 11/5/99 | Mon 11/8/99
Prepare for, and hold, Elaboration Requirements Checkpoint meeting | Fri 11/5/99 | Mon 11/8/99
Have team, including client project manager, complete the work release sign-off form | Mon 11/8/99 | Mon 11/8/99
Elaboration Checkpoint Review and Go/No Go Decision | Mon 11/8/99 | Mon 11/8/99
Elaboration Requirements & Plan Revisions Completed | Mon 11/8/99 | Mon 11/8/99
Architecture | Mon 11/8/99 | Wed 11/24/99
Do Technical Reviews | Mon 11/8/99 | Mon 11/8/99
Technical Reviews 1 | Mon 11/8/99 | Mon 11/8/99
Technical Reviews 2 | Mon 11/8/99 | Mon 11/8/99
Architectural Analysis | Mon 11/8/99 | Mon 11/15/99
Define Modeling Conventions | Mon 11/8/99 | Tue 11/9/99
Define the High Level Organization of Subsystems | Tue 11/9/99 | Wed 11/10/99
Identify Analysis Mechanisms | Wed 11/10/99 | Wed 11/10/99
Identify Key Concepts | Wed 11/10/99 | Thu 11/11/99
Create Use-Case Realizations | Thu 11/11/99 | Fri 11/12/99
Review the Results | Fri 11/12/99 | Mon 11/15/99
Architectural Analysis Completed | Mon 11/15/99 | Mon 11/15/99
Architectural Design | Mon 11/15/99 | Wed 11/17/99
Identify Design Mechanisms | Mon 11/15/99 | Mon 11/15/99
Identify Design Classes and Subsystems | Mon 11/15/99 | Mon 11/15/99
Identify Interfaces | Mon 11/15/99 | Mon 11/15/99
Identify Reuse Opportunities | Mon 11/15/99 | Tue 11/16/99
Reverse-engineer components and databases | Tue 11/16/99 | Tue 11/16/99
Define the Low-level Organization of Subsystems | Tue 11/16/99 | Wed 11/17/99
Include Architecturally Significant Model Elements in the Logical View | Wed 11/17/99 | Wed 11/17/99
Check-points: Design Model | Wed 11/17/99 | Wed 11/17/99
Architectural Design Completed | Wed 11/17/99 | Wed 11/17/99
Describe Concurrency (if applicable) | Wed 11/17/99 | Mon 11/22/99
Define Concurrency Requirements | Wed 11/17/99 | Thu 11/18/99
Identify Processes | Thu 11/18/99 | Thu 11/18/99
Identify Process Lifecycles | Thu 11/18/99 | Thu 11/18/99
Identify Inter-Process Communication Mechanisms | Thu 11/18/99 | Fri 11/19/99
Allocate Inter-Process Coordination Resources | Fri 11/19/99 | Fri 11/19/99
Map Processes onto the Implementation Environment | Fri 11/19/99 | Fri 11/19/99
Distribute Model Elements Among Processes | Fri 11/19/99 | Mon 11/22/99
Concurrency Documented | Mon 11/22/99 | Mon 11/22/99
Use-Case Analysis | Mon 11/8/99 | Thu 11/11/99
Supplement the Descriptions of the Use Cases | Mon 11/8/99 | Mon 11/8/99
For each use case find classes from use case behavior | Tue 11/9/99 | Tue 11/9/99
For each use case distribute use case behavior to classes | Tue 11/9/99 | Tue 11/9/99
For each resulting class Describe Responsibilities | Wed 11/10/99 | Wed 11/10/99
For each resulting class Describe Attributes & Associations | Wed 11/10/99 | Wed 11/10/99
For each resulting class Qualify Analysis Mechanisms | Wed 11/10/99 | Wed 11/10/99
Unify Analysis Classes | Wed 11/10/99 | Thu 11/11/99
Evaluate the Results | Thu 11/11/99 | Thu 11/11/99
Use-Case Analysis Complete | Thu 11/11/99 | Thu 11/11/99
Use-Case Design | Thu 11/11/99 | Fri 11/12/99
Describe Interactions Between Design Objects | Thu 11/11/99 | Thu 11/11/99
Simplify Sequence Diagrams using Subsystems (optional) | Thu 11/11/99 | Thu 11/11/99
Describe Persistence-related behavior | Thu 11/11/99 | Thu 11/11/99
Refine the Flow of Events Description | Thu 11/11/99 | Thu 11/11/99
Unify Classes and Subsystems | Thu 11/11/99 | Thu 11/11/99
Evaluate the Results | Thu 11/11/99 | Fri 11/12/99
Use-Case Design Completed | Fri 11/12/99 | Fri 11/12/99
Class Design (optional) | Fri 11/12/99 | Wed 11/17/99
Create Initial Design Classes | Fri 11/12/99 | Fri 11/12/99
Identify Persistent Classes | Fri 11/12/99 | Fri 11/12/99
Define Class Visibility | Fri 11/12/99 | Mon 11/15/99
Define Operations | Mon 11/15/99 | Mon 11/15/99
Define Methods | Mon 11/15/99 | Mon 11/15/99
Define States | Mon 11/15/99 | Mon 11/15/99
Define Attributes | Mon 11/15/99 | Tue 11/16/99
Define Dependencies | Tue 11/16/99 | Tue 11/16/99
Define Associations | Tue 11/16/99 | Tue 11/16/99
Define Generalizations | Tue 11/16/99 | Tue 11/16/99
Handle Non-Functional Requirements in General | Tue 11/16/99 | Wed 11/17/99
Evaluate the Results | Wed 11/17/99 | Wed 11/17/99
Class Design Completed | Wed 11/17/99 | Wed 11/17/99
Design Database | Wed 11/17/99 | Mon 11/22/99
Map Persistent Design Classes to the Data Model | Wed 11/17/99 | Wed 11/17/99
Optimize the Data Model for Performance | Wed 11/17/99 | Thu 11/18/99
Optimize Data Access | Thu 11/18/99 | Fri 11/19/99
Define Storage Characteristics | Fri 11/19/99 | Fri 11/19/99
Define Reference Tables | Fri 11/19/99 | Fri 11/19/99
Define Data and Referential Integrity Enforcement Rules | Fri 11/19/99 | Fri 11/19/99
Distribute Class Behavior to the Database | Fri 11/19/99 | Mon 11/22/99
Review the Results | Mon 11/22/99 | Mon 11/22/99
Database Design Complete | Mon 11/22/99 | Mon 11/22/99
Review the Design | Mon 11/22/99 | Mon 11/22/99
Design Model Survey updated, reviewed, and signed off | Mon 11/22/99 | Mon 11/22/99
Use-Case-Model-Realization Report created, reviewed, and signed off | Mon 11/22/99 | Mon 11/22/99
Software Architecture document created, reviewed, and signed off | Mon 11/22/99 | Mon 11/22/99
Create Architecture Prototype(s) | Mon 11/22/99 | Tue 11/23/99
Deployment Diagram (for hw and network) created, reviewed, and signed off | Mon 11/22/99 | Mon 11/22/99
Architecture test cases created, reviewed, and signed off | Mon 11/8/99 | Thu 11/11/99
Prepare for Architecture Checkpoint | Tue 11/23/99 | Tue 11/23/99
Hold Architecture Checkpoint meeting | Tue 11/23/99 | Wed 11/24/99
Architecture complete | Wed 11/24/99 | Wed 11/24/99
Security | Mon 10/25/99 | Tue 10/26/99
Web Security Plan created, reviewed, and signed off | Mon 10/25/99 | Tue 10/26/99
Transition Planning | Mon 11/8/99 | Tue 11/9/99
Initial Contingency and Disaster Recovery Plan created, reviewed, and signed off | Mon 11/8/99 | Mon 11/8/99
Change Management Assessment | Mon 11/8/99 | Tue 11/9/99
Hold change management assessment session | Mon 11/8/99 | Tue 11/9/99
Change Management Assessment created, reviewed, and signed-off | Mon 11/8/99 | Tue 11/9/99
Quality Assurance & Test Planning | Mon 11/8/99 | Tue 11/9/99
Software Test Plan created, reviewed, and signed off | Mon 11/8/99 | Mon 11/8/99
Software Test Cases for Construction-Iteration 1 created, reviewed, and signed off | Mon 11/8/99 | Tue 11/9/99
Elaboration Wrap-up | Wed 11/24/99 | Fri 11/26/99
Conduct Quality Check Meeting with Client | Wed 11/24/99 | Wed 11/24/99
Hold Context Lessons Learned Meeting | Wed 11/24/99 | Wed 11/24/99
Validate/Invalidate Assumption from Elaboration proposal | Wed 11/24/99 | Wed 11/24/99
Iterative Delivery Project Plan updated, reviewed, and signed off | Wed 11/24/99 | Wed 11/24/99
Software Development Plan updated, reviewed, and signed off | Wed 11/24/99 | Thu 11/25/99
Knowledge Transfer Plan updated, reviewed, and signed off | Thu 11/25/99 | Thu 11/25/99
Design Guidelines created, reviewed, and signed off | Wed 11/24/99 | Wed 11/24/99
User Manual/Specification/Help updated | Wed 11/24/99 | Wed 11/24/99
Project estimates updated (accurate to +40%, -5%) | Thu 11/25/99 | Thu 11/25/99
Software Project Log updated | Thu 11/25/99 | Thu 11/25/99
Obtain Sign-off | Thu 11/25/99 | Thu 11/25/99
Have team, including client project manager, complete the work release sign-off form | Thu 11/25/99 | Thu 11/25/99
Elaboration Checkpoint Review and Go/No Go Decision | Thu 11/25/99 | Thu 11/25/99
Move appropriate deliverables from Project Homepage to IAN Artifacts | Thu 11/25/99 | Fri 11/26/99
Elaboration Complete | Fri 11/26/99 | Fri 11/26/99
The following deliverables or artifacts will be generated and reviewed during the Elaboration Iteration:
Artifact Set | Deliverable | Responsible Owner
--- | --- | ---
Business Modeling Set | Glossary (expand & update) | Brian Egler
Requirements Set | Vision Document (update) Use Case Specifications (update) Supplementary Specification (update) Use Case Model and Model Survey (update) User-Interface Prototype (forms only) | Brian Egler Brian Egler Ed Post Ken Perch Mark Grimes
Design Set | Analysis Model (Logical View) Design Model (Logical, Component & Process Views) Software Architecture Document | Ken Perch Ken Perch Ken Perch
Implementation Set | Integration Build Plan Architectural Prototype - Software Baseline Test Drivers, Stubs, Data, & Scripts Test Procedures Test Evaluation Report | Mary Durham Ken Perch Mike Hunziker Chris Curvey Mary Durham
Management Set | Iteration Plan Project Plan (update) Project Schedule (update) Project Risk List (update) Status Assessment Iteration Assessment Test Plan | Mary Durham Mary Durham Mary Durham Mary Durham Mary Durham Mary Durham Mary Durham
Standards and Guidelines | Design Guidelines User-Interface Guidelines | Ken Perch Mark Grimes
### Resources #### Staffing The project staffing for this iteration can be viewed as follows: #### Financial Resources The budget for this iteration is $180,000. WebNewsOnLine has secured this funding. ### Use Cases Use cases to be developed during this iteration are: Approve Story Edit Profile Pay Fee With Credit Card Print Advertiser Reports Provide Feedback Read Content on Web Site Send Content Send Page Subscribe ### Evaluation Criteria The primary goal of this iteration is to complete the analysis and design of selected use cases and to develop a working architectural prototype. Risk associated with the architectural design or system performance will be realized by the end of the iteration. Each deliverable developed during the iteration will be peer reviewed and subject to approval from the team. The internal project team and the Subscriber, Advertiser, and Editor representatives will review the User-Interface Prototype and the Architectural Prototype. Copyright 1987 - 2003 Rational Software Corporation |  |