Workflow Detail: Integrate
the System
|
The purpose of this workflow detail is to integrate implementation subsystems to create a new consistent version of the overall system. | |||||||||||||||||||||||||
|
| ||||||||||||||||||||||||
Description
The integrator integrates the system, in accordance with the integration build plan, by adding the delivered implementation subsystems into the system integration workspace and creating builds. Each build is then integration tested by a tester. After the last increment, the build can be completely system tested by a tester.
Related Information
This section provides links to additional information related to this workflow detail.
Timing
Starts in Elaboration phase, recurs through Construction and Transition phases.
Optionality
Required (however, in smaller systems, there may not be separate integration of subsystems)
How to Staff
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.
Work Guidelines
Integration work is typically automated to a large degree, with manual effort required when the build breaks. A frequent strategy is to perform automated nightly builds and some automated testing (usually at the unit level), allowing for frequent feedback from the build process.
