The service-oriented design model supports the notion of these well-accepted industry
fundamental design perspectives. But the service-oriented design paradigm must present a distinct
approach to solving organizational problems. It is a holistic approach that incorporates all
available software assets in an organization. These are legacy software components, applications,
services, and even middleware. This design approach also includes intangible assets, such as conceptual
services, or even just ideas. For this exercise, we conceive of all the participating software
assets as services. Furthermore, the design paradigm presented here advocates a loosely coupled
service ecosystem landscape that can span multiple lines of business, organizations, and platforms.
It also addresses interoperability challenges resulting from service structure and service association
complexities. Consider the three major service-oriented design model perspectives (depicted
in Exhibit P.1) that can facilitate a design solution for future architecture, construction, deployment,
and production activities: service relationship, design composition structure, and service
transaction.
Service Relationship
Service Transaction
Design Composition
Structure
EXHIBIT P.1 SERVICE-ORIENTED DESIGN MODEL PERSPECTIVES
Service-Oriented Logical Design General Model 231
SERVICE-ORIENTED LOGICAL DESIGN RELATIONSHIP. The service-oriented design phase starts
with the identification of a logical service relationship (elaborated on in Chapter 12).
Pages:
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402