Datasheet

P1: OTA/XYZ P2: ABC
c01 JWBT191/Bell November 1, 2009 14:39 Printer Name: Yet to Come
Service-Oriented Discovery and Analysis Patterns 17
capacity and consumption planning, inadequate computer resources assignment that influenced
service performance, and/or unsuitable design and architecture implementations. From a return on
investment perspective, the as-is modeling approach can identify the actual cost of a project that
has been launched in the past. This vital information can shape future service-oriented development
initiatives and serve as an essential use case study to improve future projects.
SERVICE-ORIENTED DISCOVERY AND ANALYSIS PATTERNS
By and large, patterns are intrinsic to software development disciplines since they simply offer
solutions. These are proven best practices and a recommended “how to” set of remedies that can
be applied to resolving problems. They are also conceived of as repeatable methods that have been
road-tested and applied to rectify similar software development problems.
Design patterns are perhaps the most well-known guiding solutions that originated in mod-
ern computing times both to assist with understanding a problem and, most important, to offer
avenues of implementation that developers and architects can employ. Moreover, these patterns are
positioned to help alleviate challenges on different levels of software implementation: Some are de-
vised to provide improved source code algorithms, others address application architectural issues,
and several tackle enterprise architecture solutions.
The service-oriented discovery and analysis patterns introduce a wide range of repeatable
solutions that not only address design and architecture challenges but also represent a new breed of
patterns affiliated with the process of implementation. The processes of service identification and
inspection, of discovery, of categorization, and of course of analysis and modeling can be lever-
aged by a practitioner to devise superior solutions to organizational concerns. These how-to best
practices and policies are accompanied by what-not-to-do recommendations, often referred to as
anti-patterns. Service-oriented discovery and analysis anti-patterns are also necessary to foster ser-
vice reuse, consolidation, loose coupling, and business agility.
The five different discovery and analysis pattern categories that are illustrated in Ex-
hibit 1.8 can help carve the analysis proposition that architects, developers, modelers, analysts, and
EXHIBIT 1.8 SERVICE-ORIENTED DISCOVERY AND
ANALYSIS PATTERNS