SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 288 | Next

Michael Bell

"Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture"

This case obviously conveys the reusability aspects of overlapped sections
and the effectiveness of the intersection analysis operation, by which it facilitates the discovery
of shared services.
Service-Oriented Analysis Modeling Operations 165
General
Ledger
Service
Cluster
(COBOL-
mainframe)
CL1 CL2 CL3
Accounts
Payable
Service
Cluster
(J2EE)
Records
Lookup
Composite
Service
Customer
Records
Lookup
Atomic
Service
Monthly
Statements
Composite
Service
Vendor
Records
Lookup
Atomic
Service
Cash Flow
Report
Atomic
Service
CO1 CO2 A1
A2 A3
Accounts
Receivable
Service
Cluster
(.NET)
EXHIBIT 8.10 USE CASE G: INTEROPERABILITY AND REUSABILITY STRATEGY
USE CASE G: INTEROPERABILITY AND REUSABILITY STRATEGY. Exhibit 8.10 identifies reusability
opportunities created by the intersection of three major accounting service clusters, each of
which operates in a different technological environment. The accounts payable service cluster
(CL1) is empowered by a J2EE platform, whereas the accounts receivable cluster (CL2) is supported
by a .NET framework. The third entity, the general ledger service cluster, is hosted in a
mainframe environment. Note that these intersecting clusters also yield an overlapping section
that is composed of three services that can commonly be utilized by these clusters. These are
the records lookup composite service (CO1), which aggregates the vendor records (A2) lookup
and the customer records (A3) lookup atomic services.


Pages:
276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300