Workflow Detail:
|
The purpose of this workflow detail is to plan the integration of the system for the current iteration. | |||||||||||||||||||||
|
|
Planning the integration is focussed on which implementation subsystems should be implemented, and the order in which the implementation subsystems should be integrated in the current iteration.
This section provides links to additional information related to this workflow detail.
Starts in Elaboration phase, recurs through Construction and Transition phases.
Recommended, especially for larger systems.
Integration is typically carried out by a single person (for a small project on which the build process in simple) or a small team (for a large project on which the build process is complex). The integrators need experience in software build management, configuration management, and experience in the programming language in which the components to be integrated are written. Because integration often involves a high degree of automation, expertise in operating system shell or scripting languages and tools like 'make' (on Unix) is also essential.
Planning the integration process should be done early, at least in rough form, when the architecture is baselined. As the architecture and design evolve, the integration plan should be examined and updated to ensure that the build plan does not become obsolete by changes in the architecture or the design.
Rational Unified Process
|