Artifact: Integration Build Plan

Integration Build Plan	The integration build plan provides a detailed plan for integration within an iteration.
Role:	Integrator
Templates:	HTML Others
Examples:	Integration Build Plan, from the Course Registration System Elaboration Construction Integration Build Plan, from the Collegiate Sports Paging System (e-business)
Purpose Timing Responsibility Tailoring

Input to Activities:

Identify Targets of Test

Integrate System

Integrate Subsystem

Plan System Integration

Plan Subsystem Integration

Output from Activities:

Plan System Integration

Plan Subsystem Integration

Purpose

The purpose of the Integration Build Plan is to define the order in which the components and subsystems should be implemented, which builds to create when integrating the system, and how they are to be assessed.

Timing

As soon as it has been decided which use cases are to be implemented, the Integration Build Plan is planned in the current iteration. It is modified as needed during the iteration.

Responsibility

An integrator is responsible for authoring the Integration Build Plan, and keeping it up-to-date. For each build, the test designer will contribute descriptions of the test cases, test procedures and test scripts to be used to assess the build. These may be supplied as references to material contained in other test artifacts.

Tailoring

You should adjust the outline of the Integration Build Plan to suit the nature of your project. For example, if the system is large, there may be a case for having subsidiary plans for each subsystem. The formality and extent of the test material contained or referenced from the Integration Build Plan will vary depending on the significance of the build. Obviously the final build of an iteration will be formally assessed against all the evaluation criteria described in the Iteration Plan.