Artifact: Integration Build Plan
 Integration Build Plan |
The integration build plan provides a detailed plan for integration within an iteration. |
| Worker: | System Integrator |
| Template: | Word template |
Purpose
The purpose of the Integration Build Plan is to define the order in which the components and subsystems should be implemented, and which builds to create when integrating the system.
The following people will use the Integration Build Plan:
- Implementers, to plan the order in which to implement classes, and what and when to deliver to system integration.
- System integrator, as their planning tool.
- Test designer, to plan the tests for the iteration.
Brief Outline
1. Objectives
A brief description of the purpose of the Integration Build Plan.
2. Scope
A brief description of what the Integration Build Plan applies to; what is affected or influenced by this document.
3. References
A list of related or referenced documents.
4. Subsystems
State which subsystems to implement in this iteration. Also state the preferred order in which the subsystems should be implemented to be ready in time for integration.
5. Builds
The integration (in the iteration) is divided into a number of increments, each resulting in a build, which is integration-tested. This section should specify which builds to create and which subsystems should be part of each build.
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
A system integrator is responsible for authoring the integration build plan, and keeping it up-to-date.
Tailoring
You should adjust the outline of the Integration Build Plan to suit the nature of your project.
