The first iteration (C1) of the Construction Phase developed the Beta software for Release 1 (R1.0). The second iteration (C2) of the Construction Phase will implement the remaining components for Release 1 and will fix the defects discovered in the Beta Release. The final output of this iteration will be the R1.0 software.

1.2 Scope

This C2 Iteration Plan applies to the C-Registration System project being developed by Wylie College Information Systems for Wylie College. This document will be used by the Project Manager and by the project team.

1.3 Definitions, Acronyms and Abbreviations

See the Glossary [3].

1.4 References

Applicable references are:

Course Registration System Vision Document, WyIT387, V1.0, Wylie College IT.
Course Registration System Stakeholder Requests Document, WyIT389, V1.0, 1998, Wylie College IT.
Course Registration System Glossary, WyIT406, V1.0, 1998, Wylie College IT.
Course Registration System Construction Phase Schedule, V1.0, 1999, Wylie College IT.
Course Registration System Software Development Plan, WyIT418, V2.0, 1999, Wylie College IT.
Course Registration System C2 Test Plan, WyIT501, V1.0, 1999, Wylie College IT.
Course Registration System Supplementary Specification, WyIT400, V1.0, 1999, Wylie College IT.

1.5 Overview

This document provides the detailed schedule for this iteration including all milestones. It also describes the required resources (staffing, financial, and equipment), expected status of use cases, and evaluation criteria for completion of the iteration.

2. Plan

The second iteration (C2) of the Construction Phase will address all defect logs and user feedback received from the Beta Release. C2 will also implement remaining use cases, classes, and components that did not make it into the Beta Release. C2 will result in fully operational software for Release 1 (R1.0).

The duration of the second iteration (C2) is approximately one month.

The primary use cases that form Release 1.0 are:

Logon
Close Registration
Register for Courses
Interface to Course Catalog Database
Interface to Finance System
Maintain Student Information
Maintain Professor Information

Iteration Activities

The following table illustrates the high level activities for C2 with their planned start and end dates.

Activity	Start Date	End Date
Analysis & Design (Remaining R1 use cases & defects)	April 16, 1999	April 26, 1999
Implementation (R1 & Beta defects)	April 16, 1999	May 6, 1999
Test (R1 & Beta defects)	April 16, 1999	May 12, 1999
Environment	April 13, 1999	May 14, 1999
Management	April 13, 1999	May 14, 1999

Iteration Schedule

The detailed schedule showing all tasks and the assigned responsibilities is contained in the following schedule [4]:

Task Name	Start	Finish	Resource Names
Milestones	Mon 3/15/99	Thu 6/17/99
Start Construction Iteration 1	Mon 3/15/99	Mon 3/15/99
R1 Beta Milestone (Beta Software Ready)	Mon 4/12/99	Mon 4/12/99
Start Construction Iteration 2	Mon 4/12/99	Mon 4/12/99
Initial Operational Capability Milestone (Release 1.0)	Fri 5/14/99	Fri 5/14/99
Start Construction Iteration 3	Fri 5/14/99	Fri 5/14/99
Second Operational Capability Milestone (Release 2.0)	Thu 6/17/99	Thu 6/17/99


Construction Phase	Mon 3/15/99	Thu 6/17/99
Iteration C1 - Develop Release 1 Beta	Mon 3/15/99	Mon 4/12/99
Analysis & Design (Refine)	Tue 3/16/99	Thu 3/25/99
Refine Architecture	Mon 3/22/99	Thu 3/25/99	Architect
Prioritized Subsystem Design	Tue 3/16/99	Wed 3/17/99
Subsystem Design - Subsystem ss-fx	Tue 3/16/99	Wed 3/17/99	Designer
Subsystem Design - Subsystem ss-cr	Tue 3/16/99	Wed 3/17/99	Designer
Prioritized Class Design	Tue 3/16/99	Wed 3/17/99
Class Design - Class C-brx	Tue 3/16/99	Wed 3/17/99	Designer
Class Design - Class C-abx	Tue 3/16/99	Wed 3/17/99	Designer
Class Design - Class C-twe	Tue 3/16/99	Wed 3/17/99	Designer
Class Design - Class C-tui	Tue 3/16/99	Wed 3/17/99	Designer
Prioritized Use-Case Design	Thu 3/18/99	Fri 3/19/99
Design Use-Case uc-hev	Thu 3/18/99	Fri 3/19/99	Designer
Design Use-Case uc-mrk	Thu 3/18/99	Fri 3/19/99	Designer
Database Design	Mon 3/22/99	Tue 3/23/99	Database Designer
Review the Design	Wed 3/24/99	Thu 3/25/99	Design Reviewer
Implementation (Beta)	Tue 3/16/99	Tue 4/6/99
Plan System Integration	Tue 3/16/99	Wed 3/17/99	System Integrator
Plan Subsystem Integration	Thu 3/18/99	Fri 3/19/99	Implementer
Implement Prioritized Components	Mon 3/22/99	Tue 3/23/99
Implement Component c-uic	Mon 3/22/99	Tue 3/23/99	Implementer
Implement Component c-uib	Mon 3/22/99	Tue 3/23/99	Implementer
Implement Component c-iln	Mon 3/22/99	Tue 3/23/99	Implementer
Implement Component c-oie	Mon 3/22/99	Tue 3/23/99	Implementer
Implement Component c-wes	Mon 3/22/99	Tue 3/23/99	Implementer
Implement Component c-kkm	Mon 3/22/99	Tue 3/23/99	Implementer
Fix Defects	Mon 3/22/99	Wed 3/24/99	Implementer
Review Code	Thu 3/25/99	Fri 3/26/99	Code Reviewer
Perform Unit Tests	Thu 3/25/99	Mon 3/29/99	Implementer
Integrate Subsystem	Tue 3/30/99	Thu 4/1/99	Implementer
Integrate System	Fri 4/2/99	Tue 4/6/99	System Integrator
Test (Interfaces & Integrated Function)	Tue 3/16/99	Thu 4/8/99
Plan Test (Integration & System)	Tue 3/16/99	Tue 3/16/99	Test Designer
Design Test (Integration & System)	Wed 3/17/99	Wed 3/17/99	Test Designer
Implement Test	Thu 3/18/99	Thu 3/18/99	Test Designer
Design Test Packages and Classes	Fri 3/19/99	Fri 3/19/99	Designer
Implement Test Components and Subsystems	Mon 3/22/99	Mon 3/22/99	Implementer
Execute Integration Tests	Fri 4/2/99	Fri 4/2/99	Integration Tester
Execute System Test	Wed 4/7/99	Wed 4/7/99	System Tester
Execute Performance Tests	Tue 3/23/99	Tue 3/23/99	Performance Tester
Evaluate Test	Thu 4/8/99	Thu 4/8/99	Test Designer
Management	Mon 3/15/99	Mon 4/12/99
Develop Iteration Plan	Mon 3/15/99	Mon 3/15/99	Project Manager
Staff Project	Tue 3/16/99	Tue 3/16/99	Project Manager
Revisit Risk List	Mon 3/15/99	Mon 3/29/99	Project Manager
Evaluate the Iteration	Fri 4/9/99	Fri 4/9/99	Project Manager
Update Project Plan	Mon 4/12/99	Mon 4/12/99	Project Manager
Iteration C2 - Develop Release 1	Tue 4/13/99	Fri 5/14/99
Analysis & Design (Refine)	Fri 4/16/99	Mon 4/26/99
Refine Architecture	Mon 4/26/99	Mon 4/26/99	Architect
Prioritized Subsystem Design	Fri 4/16/99	Mon 4/19/99	Designer
Subsystem Design - Subsystem ss-inf	Fri 4/16/99	Mon 4/19/99
Subsystem Design - Subsystem ss-ext	Fri 4/16/99	Mon 4/19/99
Prioritized Class Design	Fri 4/16/99	Mon 4/19/99
Class Design - Class C-imn	Fri 4/16/99	Mon 4/19/99	Designer
Class Design - Class C-ppl	Fri 4/16/99	Mon 4/19/99	Designer
Class Design - Class C-pnh	Fri 4/16/99	Mon 4/19/99	Designer
Class Design - Class C-ujn	Fri 4/16/99	Mon 4/19/99	Designer
Prioritized Use-Case Design	Tue 4/20/99	Wed 4/21/99	Designer
Design Use-Case uc-wsx	Tue 4/20/99	Wed 4/21/99	Designer
Design Use-Case uc-vbc	Tue 4/20/99	Wed 4/21/99	Designer
Database Design	Thu 4/22/99	Thu 4/22/99	Database Designer
Review the Design	Fri 4/23/99	Mon 4/26/99	Design Reviewer
Implementation (Effective Production)	Fri 4/16/99	Thu 5/6/99
Plan System Integration	Fri 4/16/99	Mon 4/19/99	System Integrator
Plan Subsystem Integration	Tue 4/20/99	Wed 4/21/99	Implementer
Implement Prioritized Components	Thu 4/22/99	Fri 4/23/99
Implement Component c-red	Thu 4/22/99	Fri 4/23/99	Implementer
Implement Component c-art	Thu 4/22/99	Fri 4/23/99	Implementer
Implement Component c-had	Thu 4/22/99	Fri 4/23/99	Implementer
Implement Component c-unv	Thu 4/22/99	Fri 4/23/99	Implementer
Implement Component c-tak	Thu 4/22/99	Fri 4/23/99	Implementer
Implement Component c-fin	Thu 4/22/99	Fri 4/23/99	Implementer
Fix Defects	Thu 4/22/99	Fri 4/23/99	Implementer
Review Code	Mon 4/26/99	Wed 4/28/99	Code Reviewer
Perform Unit Tests	Mon 4/26/99	Wed 4/28/99	Implementer
Integrate Subsystem	Thu 4/29/99	Mon 5/3/99	Implementer
Integrate System	Tue 5/4/99	Thu 5/6/99	System Integrator
Test (Interfaces & Integrated Function)	Fri 4/16/99	Wed 5/12/99
Plan Test (Integration & System)	Fri 4/16/99	Mon 4/19/99	Test Designer
Design Test (Integration & System)	Tue 4/20/99	Wed 4/21/99	Test Designer
Implement Test	Thu 4/22/99	Mon 4/26/99	Test Designer
Design Test Packages and Classes	Tue 4/27/99	Thu 4/29/99	Designer
Implement Test Components and Subsystems	Fri 4/30/99	Tue 5/4/99	Implementer
Execute Integration Tests	Wed 5/5/99	Fri 5/7/99	Integration Tester
Execute System Test	Fri 5/7/99	Tue 5/11/99	System Tester
Execute Performance Tests	Wed 5/5/99	Fri 5/7/99	Performance Tester
Evaluate Test	Wed 5/12/99	Wed 5/12/99	Test Designer
Management	Tue 4/13/99	Fri 5/14/99
Develop Iteration Plan	Tue 4/13/99	Thu 4/15/99	Project Manager
Staff Project	Fri 4/16/99	Fri 4/16/99	Project Manager
Revisit Risk List	Tue 4/13/99	Tue 4/27/99	Project Manager
Evaluate the Iteration	Thu 5/13/99	Thu 5/13/99	Project Manager
Update Project Plan	Fri 5/14/99	Fri 5/14/99	Project Manager
Iteration C3 - Develop Release 2.0	Mon 5/17/99	Thu 6/17/99
Analysis & Design (Refine)	Wed 5/19/99	Wed 5/26/99
Refine Architecture	Tue 5/25/99	Wed 5/26/99	Architect
Prioritized Subsystem Design	Wed 5/19/99	Thu 5/20/99	Designer
Subsystem Design - Subsystem ss-new	Wed 5/19/99	Thu 5/20/99
Prioritized Class Design	Wed 5/19/99	Thu 5/20/99
Class Design - Class C-vad	Wed 5/19/99	Thu 5/20/99	Designer
Class Design - Class C-jud	Wed 5/19/99	Thu 5/20/99	Designer
Class Design - Class C-pol	Wed 5/19/99	Thu 5/20/99	Designer
Class Design - Class C-pat	Wed 5/19/99	Thu 5/20/99	Designer
Prioritized Use-Case Design	Fri 5/21/99	Mon 5/24/99	Designer
Design Use-Case uc-cad	Fri 5/21/99	Mon 5/24/99	Designer
Database Design	Tue 5/25/99	Tue 5/25/99	Database Designer
Review the Design	Wed 5/26/99	Wed 5/26/99	Design Reviewer
Implementation (Effective Production)	Wed 5/19/99	Wed 6/9/99
Plan System Integration	Wed 5/19/99	Thu 5/20/99	System Integrator
Plan Subsystem Integration	Fri 5/21/99	Mon 5/24/99	Implementer
Implement Prioritized Components	Tue 5/25/99	Wed 5/26/99
Implement Component c-rad	Tue 5/25/99	Wed 5/26/99	Implementer
Implement Component c-bpp	Tue 5/25/99	Wed 5/26/99	Implementer
Implement Component c-puj	Tue 5/25/99	Wed 5/26/99	Implementer
Implement Component c-hbn	Tue 5/25/99	Wed 5/26/99	Implementer
Implement Component c-cdd	Tue 5/25/99	Wed 5/26/99	Implementer
Implement Component c-fer	Tue 5/25/99	Wed 5/26/99	Implementer
Fix Defects	Tue 5/25/99	Thu 5/27/99	Implementer
Review Code	Fri 5/28/99	Mon 5/31/99	Code Reviewer
Perform Unit Tests	Fri 5/28/99	Tue 6/1/99	Implementer
Integrate Subsystem	Wed 6/2/99	Fri 6/4/99	Implementer
Integrate System	Mon 6/7/99	Wed 6/9/99	System Integrator
Test (Interfaces & Integrated Function)	Wed 5/19/99	Tue 6/15/99
Plan Test (Integration & System)	Wed 5/19/99	Thu 5/20/99	Test Designer
Design Test (Integration & System)	Fri 5/21/99	Mon 5/24/99	Test Designer
Implement Test	Tue 5/25/99	Thu 5/27/99	Test Designer
Design Test Packages and Classes	Fri 5/28/99	Mon 5/31/99	Designer
Implement Test Components and Subsystems	Tue 6/1/99	Wed 6/2/99	Implementer
Execute Integration Tests	Mon 6/7/99	Wed 6/9/99	Integration Tester
Execute System Test	Thu 6/10/99	Mon 6/14/99	System Tester
Execute Performance Tests	Thu 6/3/99	Mon 6/7/99	Performance Tester
Evaluate Test	Tue 6/15/99	Tue 6/15/99	Test Designer
Management	Mon 5/17/99	Thu 6/17/99
Develop Iteration Plan	Mon 5/17/99	Tue 5/18/99	Project Manager
Staff Project	Wed 5/19/99	Wed 5/19/99	Project Manager
Revisit Risk List	Mon 5/17/99	Mon 5/31/99	Project Manager
Evaluate the Iteration	Wed 6/16/99	Wed 6/16/99	Project Manager
Update Project Plan	Thu 6/17/99	Thu 6/17/99	Project Manager

Environment	Mon 3/15/99	Thu 6/17/99
Support the Development	Mon 3/15/99	Thu 6/17/99

Iteration Deliverables

The following deliverables will be generated and reviewed during the second iteration (C2) of the Construction Phase:

Process	Deliverable	Responsible Owner
Design Set	Analysis Model (update) Design Model (update) Software Architecture Document (update)	Sue Gamble Beth MacDonald Steve Johnson
Implementation Set	Integration Build Plan R1.0 Software Baseline Test Drivers, Stubs, Data, & Scripts Test Evaluation Report	Kerry Stone Phil Johnson Simon Jones Carol Smith
Management Set	C2 Iteration Plan Project Plan (update) Project Schedule (update) Project Risk List (update) Status Assessment Iteration Assessment Test Plan	Rick Bell Rick Bell Rick Bell Rick Bell Rick Bell Rick Bell Kerry Stone

Process

Deliverable

Responsible Owner

Design Set

Analysis Model (update)

Design Model (update)

Software Architecture Document (update)

Sue Gamble

Beth MacDonald

Steve Johnson

Implementation Set

Integration Build Plan

R1.0 Software Baseline

Test Drivers, Stubs, Data, & Scripts

Test Evaluation Report

Kerry Stone

Phil Johnson

Simon Jones

Carol Smith

Management Set

C2 Iteration Plan

Project Plan (update)

Project Schedule (update)

Project Risk List (update)

Status Assessment

Iteration Assessment

Test Plan

Rick Bell

Kerry Stone

3. Resources

Resources

Equipment & Facilities Resources

The C2 Iteration requires the following computer equipment:

- 18 PCs (Microsoft Windows 95 , Microsoft Office, Rational Rose, Rational RequisitePro)

- 20 Monitors

- 3 Printers (2 Laser, 1 Color)

- Access to the Wylie College Server.

This equipment is already in place at Wylie College Information Systems. Equipment required exclusively for Test will be detailed in the Test Plan.

Office space needs to be setup for the 2 new hires.

4. Use Cases

No new use cases will be developed for the C2 Iteration as the previous iteration (C1) to produce the Beta brought in the remaining Release 1.0 use cases. However, the following existing use cases require extensive rework:

1. Close Registration

2. Interface to Course Catalog Database

3. Interface to Finance System

5. Evaluation Criteria

The primary goal of the C2 Iteration of the Construction Phase is to complete the software baseline for Release 1 (R1.0). The R1.0 baseline must be available for the Deployment Team no later than May 20^th, 1999.

In addition, the following criteria must be met prior to completion of the C2 Iteration:

- All critical, high, and medium priority defects discovered in the Beta Release (from C1 Iteration) must be resolved.

- All user feedback from the Beta Release must be evaluated. All feedback classified as "major" must be resolved.

- All use cases and requirements targeted for Release 1 must be implemented and tested.

- All timing, performance, and quality requirements, as specified in the Supplementary Specification [7], must be met.

- The Tests, as defined in the Test Plan [6], must be executed.

- All test results must be reviewed.

- The senior management team and the Wylie College representative must approve the release of the R1.0 software baseline.