Enterprise Architecture Stack versus Domain

From what I have learned either from the TOGAF or from previous classes we know that enterprise architecture has four domains, Business Architecture, Data and Information Architecture, Application Architecture. When we talk about domain concept it looks like the enterprise architect works in each domain separately. In our organization we started enterprise architecture practice about 2 years ago and we have three domains that are within EA organization, Business and security are outside of the EA and have their own entity and agenda. Even within the EA organization each domain works with its own agenda. Although we all know that each domain should work as the part of the development cycle as described by TOGAF ADM, in reality some of practices just do not follow the methodology.

In this class we start talking about the EA stack, each architecture domain as a layer stacked each other and provide an increasing level of detail about the organization including:

·        Its goals and objectives

·        Its organizational structure and business processes

·        Its data and technology infrastructure

·        Its systems and applications

The layers interact in both directions, both horizontally and vertically where components in one layer can consume and produce services for the layer above and below. Layer provides more dependency concept.

Whether we talk about domain or stack, they are basically the same concept, the key is to understand what is the best practice and methodology.

As I mentioned in the introduction, architecture work should start with architecture vision and understand the business needs and business processes. A good enterprise architecture practice should encompass all layers.