Datasheet

P1: OTA/XYZ P2: ABC
c01 JWBT191/Bell November 1, 2009 14:39 Printer Name: Yet to Come
6 Ch. 1 Introduction
EXHIBIT 1.2 SERVICE-ORIENTED ANALYSIS ROAD MAP
Look above the Box. A practitioner should also look above the solution box to study the overarch-
ing governance standards and policies that influence service design and architecture. This analysis
effort should also focus on understanding documented and undocumented business processes and
exploring the manner by which they can be translated to service capabilities. To synchronize these
processes and harmonize transactions, it is time to start planning an orchestration model for gov-
erning business activities across the organization. Another goal that should be attained by looking
above the solution box is to get acquainted with the organizational service life cycle stages and
comprehend the various transformations that a service must undergo. Among these metamorphosis
activities is broadening service capabilities and functionality. This can be fulfilled by embarking
on an analysis effort to help practitioners generalize and abstract services beyond their existing
boundaries.
Look below theBox. The quest for a solution to an organizational concern should carry on by look-
ing below the solution box. The term “below” identifies another perspective that must be inspected
to ensure a thorough analysis process, during which the fundamental aspects of service design and
architecture are scrutinized and justified. One of the leading practices that should be exercised when
looking below the solution box is separation of concerns. This is an investigation effort that focuses
on breaking up organizational problems into manageable units of analysis to enable loosely coupled
solutions that ultimately are carried out by services.
Another important analysis activity that should take place when pursuing the below-the-
box direction is the evaluation of service granularity. This exercise fosters a balanced construction
of services across the organization by standardizing an allowable service size and the magnitude of
their operations. In other words, striking a balance between fine-grained and coarse-grained services
by limiting their growth or contraction is the art of granularity analysis. This policy eventually
promotes service decomposition activities that boost reuse, nimbleness, and software elasticity.