Abstraction levels in Architecture Modeling

This week, I intend to reflect not only on my readings in this week but on elements from last week readings as well. This week will be dedicated the architecture modeling in its three abstraction levels:

• ·       Conceptual
• ·       Logical
• ·       Implementation (Physical)

Conceptual modeling of future architecture, as discussed last week, is used to simplify the complex nature of the enterprise. Conceptual Process Topologies, Conceptual Process Patterns, Conceptual Information Patterns and conceptual application architectures reflect the high level business perspective of the enterprise components, how they deliver value and how they will be used. In Zackman’s words, this is the owner’s perspective of the enterprise.

Going into much detailed modeling, comes the logical level, or what Zackman Framework calls: the designer’s perspective. Models in this level describe the systems of the organization, ensuring they fulfill the owner’s expectations. A detailed business process flow describes the “Procure to Pay” end to end business process is an example of an artifact created in this level.  An Enterprise Technical Architecture (ETA) Component catalog is another artifact in this level, it describes the general class of technology products used in the enterprise along with their associated domains, patterns and services.

Implementation Level modeling is the least abstract representation and is very detailed. In this level, specific products, software application processes and data representations are developed. The technology models of this level describe the specific technologies used to support the systems and the business in the enterprise. An example of artifacts in this level are physical data models. Models in this view reflect the Builder‘s perspective.

Aside from multiple views modeling, this week readings covered Gartner practice in developing Enterprise Technical Architecture (ETA).  The standards and guidance presented in the case is simple yet very informative to its audience.  It is grouped into a ready-to-use combinations for common solution problems.  I guess Gartner did a great job in this part.

That’s all for now, see you next week !