So how can an architectural concept describe a technological environment??™s needs? How
can an architectural abstraction depict technological component requirements? An architectural
concept is a language that can be employed to illustrate a technological environment structure
and its essential operating elements. The rules engine concept, for example, is an architectural
generalization that illustrates a technical requirement for a central rule processing component.
But it does not point to any particular rules engine product; it merely describes a business
decision-making functionality. The credit verifier concept is another example of an architectural
requirement. This term abstracts the credit verification process that can be vital to loan and
insurance institutions.
Architectural Concept Origins. Where does an architectural concept originate from? There are
typically two major driving forces behind the establishment of an architectural abstraction. First,
consider the artifacts of the logical design solutions that were delivered during the service-oriented
design phase (Part Five). These come in handy now. They are the service relationship, logical
design composition, and transaction diagrams. Second, an architectural concept can also be derived
from existing technological environment imperatives. These are technical configurations, overall
integration structure, and supporting service-oriented assets such as middleware products, services,
and legacy applications.
Pages:
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550