This high-level observation would be vital to upcoming service construction,
deployment, and integration activities. This artifact is called the ???transaction directory
diagram.??? This index merely presents the crucial process element of the problem to be solved
350 Ch. 16 Service-Oriented Logical Architecture Principles
without drilling down too deeply into the details, and it even avoids depicting process workflow
and the sequence of the activities.
So what are the major benefits of a transaction directory? The behavioral perspective of
a logical architecture can assist in streamlining the various processes executed by technological
assets. The high-level transaction directory can reveal redundant service functionality, identify
unnecessary activities, and even contribute to asset consolidation. Imagine a scenario in which two
different service clusters offer customer profile functionality. Would one of them not be subject
to elimination? Take, for example, anther instance in which automated auto insurance services
are preliminarily offered by a legacy application. But the same offerings are also provided by a
recently constructed Web service. Should this case be further investigated to propose a solution
that reconciles the operating environment?
To identify the major contributors to an organizational solution, construct a transaction
directory diagram that depicts the various asset participants next to their process responsibilities.
Pages:
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602