The architecture conceptualization process is all
about identifying technological abstractions. It is about establishing an organizational common
vocabulary that can be reused in similar service-oriented problem-solving initiatives. It is also
about discovering common attributes of future or existing technological environment constituents.
Hence, it is required to establish an organizational architecture taxonomy that addresses enterprise
concerns. This catalog should become a common directory of recognized problems and proposed
solutions. But the architectural concepts to be identified are not the solutions themselves. They
are merely reference points to a technical implementation that either exists or is due for construction.
That is, think of an architectural abstraction as a conceptual machine that is powered by the
fundamental attributes and functionality of a given technological environment.
BOTTOM-UP AND TOP-DOWN MODELING CONCEPTUAL ARCHITECTURE MODELING. Organizational
architectural abstractions can be derived from two major sources: New architectural
concepts are established because of a newly launched project, or technological abstractions are
derived based on the existing technological operating environment. These approaches can be
simultaneously or separately employed to provide a solution. Consider the following top-down
and bottom-up approaches to architecture conceptualization:
Top-Down Architecture Conceptualization.
Pages:
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580