By
???architectural preferences??? we mean service-oriented asset reusability considerations, interoperability
requirements, loose coupling best practices, and even fostering software asset consolidation. For
example, the trading order service should be integrated with the equity trading domain. But at the
same time the trading order service can also be integrated with the fixed-income domain to increase
reusability and to avoid operation redundancy on the part of the involved domains.
Service-Oriented Business Integration Diagram 213
Granularity Alignment. Services and domains should be integrated because of their similar
business level of detail. Coarse-grained services should be aligned with larger-scope business
domains, and vice versa; domains that present a smaller business scope should be integrated with
fine-grained services. For example, the fine-grained small-business accounts profile service should
be integrated with the small-business accounts profile domain that provides a narrow business
execution solution. Conversely, the coarse-grained accounts service should be aligned with the
accounts domain, which represents a wider remedy scope. Therefore, the rule of thumb suggests
that the alignment process should match business priorities and business granularity and should
differentiate between strategic and tactical business initiatives.
INTEGRATION WITH BUSINESS ARCHITECTURE CONTEXTUAL PERSPECTIVES.
Pages:
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382