Datasheet

P1: OTA/XYZ P2: ABC
c01 JWBT191/Bell November 1, 2009 14:39 Printer Name: Yet to Come
Service-Oriented Discovery Endeavor 9
communication language between business and IT organizations and help establish an organiza-
tional glossary that consists of concepts that can be reused across the enterprise. Finally, from a
project initiation and management perspective, the service conceptualization phase also contributes
to scoping a project and setting its timeline boundaries.
Post-Proposition Discovery Iteration: Discover after Solution Proposition. The service discovery
process should persist after a solution to an organizational problem has been proposed. But at this
stage a different service identification approach should be applied. This new discovery iteration calls
for ascertaining service capabilities and functionality that meet business requirements or technical
specifications to satisfy consumers’ imperatives. In other words, at this stage in a service life cycle,
focus on discovery of services that are derived from business requirements and/or technical speci-
fications. Once discovered, these offered service solutions, often referred to as candidate services,
should be subject for design and architecture in the next iteration, which is discussed in the sections
that follow.
Design-Time Discovery Iteration: Discover during Service Design and Architecture. Once the
candidate services have been introduced, the service design and architecture phase continues. The
design venture not only focuses on firming up a service’s internal composition, it is also about
addressing external environment challenges, such as service integration, message exchange mech-
anisms, and service interoperability. During this ongoing effort, new services can be identified to
complement the previous service conceptualization and service proposition efforts that are discussed
in the preceding sections. These newly discovered services offer capabilities to enable a wide range
of solutions, such as data transformation, mediation, security, user interface, implementation of
business logic, and more.
Again, during the service design and architecture stage, the opportunities for service discov-
ery are vast and crucial to the solution because of the technological concerns that require more atten-
tion at this stage. Finally, to document the design and architecture phase and depict the discovered
services, architects, developers, analysts, modelers, and managers deliver design and architecture
blueprints and modeling artifacts (also widely known as technical specifications).
Construction-Time Discovery Iteration: Discover during Service Construction. The service con-
struction stage again introduces ample opportunities for service discovery. This service development
initiative is typically pursued by developers, architects, and technical managers by following design
and architecture blueprints and adhering to organizational best practices and standards. Obviously,
design artifacts are the driving aspects of service construction, but the developer may come across
scenarios that call for the establishment of new services to fill in the gaps of the technical specifica-
tions that were previously delivered. To comply with enterprise best practices, again, the developer
may find additional service identification opportunities. For example, to promote loose coupling
standards, a bulky service should be broken up into finer-grained new services to carry out business
or technical missions.
Refactoring is another development practice that characteristically introduces additional op-
portunities for service discovery. This is an exercise that is pursued to optimize, stylized, and mod-
ularize the source code to boost service performance and reusability factors. The developer is then
commissioned not only to enhance operations and service interfaces; source code componentization
is also required to group functionality in a logical manner. This effort to bundle logic into distinct
executables typically leads to the identification of new services.
Run-Time Discovery Iteration: Discover after Service Deployment. Finally, while a service op-
erates in a production environment, additional service discovery opportunities may arise. Here the
deployment and configuration of services and their adaptability to a functioning service ecosys-
tem is road-tested. This may call for the optimization of service integration and collaboration