|This is the central page for the OOI CI Release 1 IOC Review. The IOC (Initial Operating Capability Review) is the third milestone in the spiral development process (see CI System Engineering Methodology), ending the Construction spiral phase.|
This is the central page for the OOI CI Release 1 IOC Review. The IOC (Initial Operating Capability Review) is the third milestone in the spiral development process (see CI System Engineering Methodology and CI System Life Cycle Plan). This review ends the Construction spiral phase for this release.
The IOC review brings together a board of representative reviewers to assess the adequate achievement of the IOC milestone, a prerequisite to moving the project into the Transition spiral phase. The scope of this review is the IOC for the first of four releases of the OOI CI.
This page and all materials will remain as a reference throughout the program.
Through collaborative constructive review and critique of contrustion plans and development efforts, determine whether activities associated with the Construction phase are adequately complete and that the subsystems under review are sufficiently completed to progress to the transition phase.
The IOC success criteria against which the outcome of the Construction phase is evaluated are:
- Is the integrated and verified release mature and stable enough for deployment?
- Is the documentation sufficient to inform and train the user communities?
- Are remaining defects going to detract from the success of the next iteration?
- Do the stakeholders believe that the release is ready to transition to its user communities?
The materials of the review including all presentations will be made available from this section.
- R1 Product Description
- R1 Functional Design Specification
- R1 Functional Detail Specification
- ITV Strategy
- Integration and Verification Plan
- Integration Procedures
- Verification Procedures
- UX Test Plan
- LCA Review Pages (all the presentations and deliverables from previous review)
- LCO Review Pages (all the presentations and deliverables from previous review)
- http://www.oceanobservatories.org/spaces/download/attachments/21205028/2010-02-25_CI+Task+List.xls?version=1Transition Plan
- Biweekly Task Reports
During the meeting, collaborative notes are taken on several Etherpad sessions. These pages capture the material in the Etherpads.
- Note-taking etherpad
- Lessons To Be Learned
Subsequent to the review, the review panel compiles a review report addressing findings, open issues and a recommendation about proceeding into the transition phase of CI development. This publicly relevant parts of the report, and any OOI CI team responses, are made available here.
May 25, 2011
See agenda for more details.
UCSD La Jolla Campus, Atkinson Hall
San Diego CA
IOC is being presented in a WebEx, so no travel is necessary.
If you have any questions or concerns about the meeting, please contact Paul Dean (firstname.lastname@example.org) or Rita Bauer (email@example.com) at UCSD.
Assistant Program Coordinator
Scripps Institution of Oceanography
9500 Gilman Drive.
La Jolla, CA 92093-0436
Telephone: 858-822-0878 / Fax: 858-822-4633
Special Projects Coordinator
Scripps Institution of Oceanography
Institute of Geophysics and Planetary Physics
9500 Gilman Drive
La Jolla, CA 92093-0225
Telephone: 858-822-2946 / Fax: 858-822-3372
The transition phase begins upon successful completion of the IOC. Activities carried out during transition include beta testing to validate the release against user requirements, deployment into the appropriate CyberPoPs throughout the system of systems, and training of users and operators. The transition phase concludes when the deployed baseline becomes operational.
The core goals of the transition phase are:
- Deploying the integrated and verified release into the system of systems
- Achieving stakeholder concurrence that the deployment baseline is complete and consistent with use scenarios and concepts of operations
- Achieving the final product baseline
Essential activities during the transition phase include:
- Validation against user requirements
- Integration of construction increments into the deployment baseline
- Bug fixes
- Deployment-specific engineering
- Training of users and operators
The CI System Engineer is responsible for deployment during the transition phase, and is assisted by the Operations Manager and the Operations Team. The transition phase of each release coincides with the OOI pre-commissioning phase as defined in the CI Transition to Operations Plan and Figure 5. At completion, the CI System Engineer convenes the Product Release milestone review. Upon successful completion of the milestone, the release is transitioned to an operational state and becomes the responsibility of the Operations Manager.