Functional requirements, nonfunctional requirements, and technical
specification documents are normally delivered and inspected at the end of the planning stage to
determine whether the design stage can begin.
Typical SDLC stages serve as demarcation mechanisms to help slice project timelines
into related sets of activities. For example, in the planning stage, one simply plans the project
and assigns resources, whereas in the design stage, one designs and builds the architecture for
the system. Furthermore, this project staging method can be helpful with governing development
projects and supporting production environments. Exhibit 2.6 illustrates this approach, which
characteristically slices the life cycle timeline into a number of stages, each of which must be
executed chronologically during a product??™s life cycle. In this exhibit, the planning stage should
be implemented before the design stage. Such a structured and demarcated timeline is adequate
for many product development and support initiatives. For service-oriented projects, however, this
arrangement can hamper business agility and limit essential service metamorphosis capabilities.
Life Cycle Unpredictable Business and Technology Events. How can the service life cycle
be structured and planned to tackle unpredictable business and technology events? Can such
circumstances harm business execution and affect the enterprise??™s bottom-line productivity and
profitability? Absolutely.
Pages:
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92