The business architecture perspectives that are employed in this process, either contextual
or structural , are the reference points for service alignment activities. But to eloquently
and visually convey an integration scheme, a service-oriented business language that depicts this
alignment process is needed. What are the fundamental properties of such a means of communication?
How can this business architecture activity be communicated to the rest of the enterprise?
And what roles do services play in the big-picture scenario?
To create a virtual world of the business integration environment, the integration discipline
offers a modeling method to match service-oriented software assets and business domains. This
goal should be attained by comparing their functional capabilities and business level of detail,
business value, and business compatibility. Thus, the final artifact of this alignment process should
yield a service-oriented business integration diagram that depicts the various participating business
domains and their corresponding aligned services.
During multiple service life cycles, a practitioner should iterate on the service-oriented
business integration process until the business and technology organizations and their initiatives
have been properly aligned. Periodically, the integration modeling diagrams should be updated
to reflect the progression of services, and more importantly, the business requirements that may
evolve in the light of market trends.
Pages:
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379