This approach would also enable assessment of the
service??™s development and operation strategy and the application of adequate remedies to enhance
the service-oriented life cycle road map, if necessary.
The service life cycle progress three-dimensional cube can be placed along the life cycle
timeline at any chosen interval, as depicted in Exhibit 3.11. The best approach would be to position
the cube midstream in a life cycle season to enable accurate assessment of service progress, and
also in close proximity to staged or random events. For example, if a customer profile service is
being designed, scheduled to serve front-end applications before a major software release event,
a progress cube may be placed next to it to gauge the state of the service and its readiness for
this event.
SERVICE LIFE CYCLE ITERATION VIEW
The traditional software development waterfall paradigm advocates working on a task until it is
entirely completed, meaning the planned goals and milestones have been achieved. No repetitions
are encouraged. For example, design activities must conclude before the construction phase begins.
The exit criterion from any development stage is obviously contingent on the required deliverables
and their qualification. The danger inherent in this scenario is that large amounts of time can be
wasted waiting for certain tasks to be completed, while project budgets dwindle and the anxiety
level of the participating teams rises.
Pages:
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130