What is the rationale behind the generation model? Is such an initiative too large to
handle? The answer is ???Yes.??? A generation is akin to iterating on the entire SOA project. Once
a single iteration has been completed, the project is started from the beginning to perfect the
yielding artifacts or to produce a new set of project deliverables. This requires detailed planning,
large amounts of resources, and an extended budget. Hence, this approach is recommended for
smaller service-oriented projects but not for long-lasting initiatives. In large-scale iterations it is
possible to lose sight of management activities and in many cases the quality of service life cycle
deliverables may be compromised.
Can a generation be made up of internal iterations? Can a generation include, for example,
a discipline-level or a design-time season-level iteration? A service-oriented life cycle generation
model does not preclude the planning of intergeneration activities. If a generation is pursued in
an SOA project, internal iterations may be required to further enhance the service life cycle
deliverables. Thus, a possible choice is to plan a hierarchical iteration model for SOA projects.
This should be an integral part of the service life cycle strategy. Exhibit 3.17 illustrates this
concept: Multiple-level iterations are applied to a service life cycle.
Finally, what about the continuous disciplines? Does an iteration model include continuous
activities? Continuous discipline activities are iterative in nature and thus do not require repeatable
execution cycles.
Pages:
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136