View Source

{expand: Table Of Contents}
{toc}
{expand}

h1. Overview

This release 3 Integration plan and report sets forth the plans, integration elements, and detailed integration points that will be performed throughout the life of the release 3 development cycle. This document is continuously updated and is a communication point for subsystem development leads and is a guideline of activities for the leads and the integration team. Additionally, results are reported for each integration element forming the integration report.


h3. System Specifications

* Release 3 Product Information:
** Release 3 Product Specification
** [Release 3 Product Description |Product Description Release 3]
** [Release 3 Use Cases]
* Release 3 Service Specification:
** [EA|http://ooici.net/eaexport/ion/r3/] \- ION R3 System specification
** [Service List|syseng:CIAD OV Services] \- Specification pages for services
** [Architecture|syseng:Architecture and Design] \- Documentation for ION architecture
* R3 Deployment Configuration
** [Release 3 Deployment Configuration|syseng:CIAD SV Release 2 Deployment]

h3. Continuous Integration

Release 3 is driven from a continuous integration philosophy. This means that every change to the code base causes a build to execute tests to verify that nothing has been broken. Any failed test causes an immediate notification to be sent to the appropriate team(s) to investigate. The intent is that at any point in time the product is in a correct working order.

The following guidelines are used for continuous integration:
* There are defined and automated integration procedures owned by the integration team (the buildbot execution)
* Integration should involve integrating into a running system
* Continuously add integration tests (non trivial number) to the integration package
* Integration is the job of all team members, not just the integration team


h1. Release 3 Elaboration Phase Integration Plan and Report

This section identifies the end-to-end integration activities and plan for the development and integration teams during the elaboration phase of release 3. It also describes and reports the results of the integration element.

{expand: Elaboration Phase Integration Plan and Report}

h2. List of Release 3 Elaboration Integration Elements

Integration elements identify areas where integration needs to be performed to verify different components/subsystems/functionality is working together correctly. These integration elements are specifically for Release 3 Elaboration and worked on during the identified R3 elaboration integration points/timeframes listed in the integration points section.

h3. R3E1 Integration Elements

* To be specified

h3. R3E2 Integration Elements

* To be specified


h2. Release 3 Elaboration Integration Points

Integration points are intended to be a progression of integration elements starting with smaller, easier elements building up to more complex and wide ranging elements. Each iteration has its own identified integration points with defined integration elements. This section identifies the Release 3 Elaboration Integration Points and the integration elements attempted and/or accomplished during the assigned period.

{metadata:R3E1 Integration Points}
h3. R3E1 Integration Points

h4. Integration Point One (week 2 & 3 of iteration : TBD)
* To be specified

h4. Integration Point Two (week 4, 5, & 6 of iteration : TBD)

* To be specified

h4. Integration Point Three (week 7 and 8 of iteration: TBD)

* To be specified
{metadata}

{metadata:R3E2 Integration Points}
h3. R3E2 Integration Points

h4. Integration Point One (week 2 & 3 of iteration : TBD)

* To be specified


h4. Integration Point Two (week 4, 5, and 6 of iteration : TBD)

* To be specified


h4. Integration Point Three (week 7 and 8 of iteration : TBD)

* To be specified
{metadata}


{expand}

h1. Release 3 Construction Phase Integration Plan and Report

This section identifies the end-to-end integration activities and plan for the development and integration teams during the construction phase of release 3. It also reports the results of each integration element.

{expand: Construction Phase Integration Plan and Report}

h2. Release 3 Construction Integration Points

Integration points are intended to be a progression of integration elements starting with smaller, easier elements building up to more complex and wide ranging elements. Each iteration has its own identified integration points with defined integration elements. This section identifies the Release 3 Construction Integration Points and the integration elements attempted and/or accomplished during the assigned period.

h3. R3C1 Integration Points


{metadata:R3C1 Integration Points}
R3C1 is an 8 week iteration, with 2 weeks of design, 5 weeks of dev, and 1 week of wrap-up.

h4. Integration Point One (week 3-6 of iteration : TBD)

* To be specified

h4. Integration Point Two (week 7, and 8 of iteration : TBD)

* To be specified

h4. Integration Point Three (week 9 and 10 of iteration : TBD)

* To be specified
{metadata}


h3. R3C2 Integration Points

{metadata:R3C2 Integration Points}

R2C2 is an 8 week iteration, with 2 weeks of design, 5 weeks of dev, and 1 week of wrap-up.

h4. Integration Point One (week 3 - 6 of iteration : TBD)

* To be specified


h4. Integration Point Two (week 7 - 8 of iteration : TBD)

* To be specified



h4. Integration Point Three (week 9 - 10 of iteration : TBD)

* To be specified
{metadata}



h3. R3C3 Integration Points
{metadata:R3C3 Integration Points}

R3C3 is an 8 week iteration, with 2 weeks of design, 5 weeks of dev, and 1 week of wrap-up.

h4. Integration Point One (week 3 & 4 of iteration development period: TBD)

* To be specified


h4. Integration Point Two (week 5 & 6 of iteration development period : TBD)

* To be specified


h4. Integration Point Three (week 7 & 8 of iteration development period : TBD)

* To be specified

{metadata}

{expand}