Activity: Integrate Subsystem

Purpose To integrate the components in an implementation subsystem, then deliver the implementation subsystem for system integration.
Steps To integrate a subsystem you perform the following steps: Integrate Components After each increment, a build is created and integration tested. When the final increment has passed the tests successfully, then: Deliver the Implementation Subsystem
Input Artifacts: Component Integration Build Plan Implementation Subsystem	Resulting Artifacts: Build Implementation Subsystem
Role: Integrator

Workflow Details:

Implementation

Integrate Each Subsystem

Integrate Components

Subsystem integration proceeds according to the Artifact: Integration Build Plan, in which the order of component and subsystem integration has been planned. If a subsystem is large, a subsidiary Integration Build Plan may have been created specifically for the subsystem.

It is recommended that you integrate the implemented classes (components) incrementally bottom-up in the compilation-dependency hierarchy. At each increment you add one, or a few components to the system.

If two or more implementers are working in parallel on the same subsystem, their work is integrated through a subsystem integration workspace, into which the implementers deliver components from their private development workspaces, and from which the integrator will construct builds.

If a team of several individuals works in parallel on the same subsystem, it is important that the team members share their results frequently, not waiting until late in the process to integrate the team's work.

Deliver the Implementation Subsystem

After the final increment, when the implementation subsystem is ready and the associated build has been integration tested, the implementation subsystem is delivered into the system integration workspace.