Figure 11-2 shows an implementation workflow, giving an overview of all activities. Figure 11-2. An implementation workflow
The main work to Structure the Implementation Model is done early in the elaboration phase. The goal is to ensure that the implementation model is organized in such a way as to make the development of components and the build process as conflict-free as possible. A well-organized model will prevent configuration management problems and will allow the product to be built up from successively larger integration builds. For each iteration, you would do the following:
Implementation is tied closely to design, and there are clear tracing links from design elements to implementation elements (for example, classes to code). Round-trip engineering, which is possible only with the use of certain programming languages and tools, such as Rational Rose, and for some types of applications, will allow a close tie between design and implementation. The person acting alternately as the designer and the implementer can either modify the design model and regenerate the corresponding code or modify the implementation code and then alter the design to match the modification. This closes a gap in the process and helps prevent errors in translating the design or a design's getting out of sync with the implementation and therefore not being trusted by the implementers. For information about integration test and system tests, see Chapter 12, The Test Discipline. Chapter 13, The Configuration and Change Management Discipline, discusses the activity of building the product. |