Datasheet

P1: OTA/XYZ P2: ABC
c01 JWBT191/Bell November 1, 2009 14:39 Printer Name: Yet to Come
Service-Oriented Discovery and Analysis Proposition 11
2. Front-to-Back (105). This service discovery track calls for discovering services by study-
ing user interface deliverables, such as presentation layer logic, content rendering mecha-
nisms, page layouts, and field validation mechanisms.
3. Back-to-Front (123). This service identification course takes into consideration data arti-
facts, such as data schemas, entity diagrams, and data structures.
4. Bottom-Up (145). This approach for service discovery capitalizes on existing technologies,
architectures, and business processes to derive services.
5. Meet-in-the-Middle (165). Finally, this track for service identification shifts the focus to
the environment where services operate and the various facilities that link services to each
other, such as integration mechanisms, orchestration capabilities, and message exchange
platforms.
SERVICE-ORIENTED DISCOVERY AND ANALYSIS PROPOSITION
The service analysis and discovery processes discussed hitherto elaborate on the approach and the
road map that each effort is driven by. As the reader may recall, the analysis venture is a study,
devised to explain the nature of a problem, assess a proposed solution, and certify services for pro-
duction. In contrast, the discovery endeavor pinpoints new or existing services that offer capabilities
to alleviate an organizational concern. These discovery and analysis initiatives take place in differ-
ent stages of a service life cycle. Their yielding deliverables are distinct, yet they are interconnected
because of the inherent dependency between the two processes. Therefore, the service-oriented
discovery and analysis discipline as a whole combines these initiatives and calls for an analysis
proposition delivery. This is a chief milestone in the service-oriented life cycle because the yielded
services and their hosting environments are the enduring units of analysis for service life cycle
stages.
ANALYSIS PROPOSITION. As discussed, the final product of the service-oriented discovery and
analysis is an analysis proposition. This is an offer, typically delivered to the business and IT orga-
nizations for study and approval. Once endorsed, these analysis findings and recommendations are
utilized in the various service life cycle stages, such as conceptualization, design and architecture,
construction, and operations. So what does the analysis proposition consist of? An analysis propo-
sition does not constitute formal and final design and architecture blueprints; those are provided
during the design and architecture service life cycle stage. In contrast, the analysis proposition is
merely an examination of service internal and external constructs, an assessment of feasibility, and
recommendations for impending service implementations.
Therefore, the chief deliverable is an analysis modeling diagram that illustrates a proposal
for a solution in which services, their corresponding consumers, and their hosting environments
are identified and modeled for a solution. The term “modeled” pertains to modeling efforts that are
conducted by analysts, architects, modelers, developers, and managers employing an analysis mod-
eling language and notation. Furthermore, this proposition characteristically includes recommended
service internal and external design and architecture, such as service structures, distribution of ser-
vices, integration of services, and a model for binding contracts. To read more about the modeling
language and its notation, refer to the Service-Oriented Discovery and Analysis Modeling section
later in this chapter and to Chapters 14 through 22.
The sections that follow depict the three major deliverables of the service-oriented discovery
and analysis proposition (illustrated in Exhibit 1.5). These include the ultimate artifacts that the
practitioner should consider delivering:
1. Proposing an enhanced solution
2. Proposing an alternative solution
3. Proposing a new solution