Enterprise Architecture and Stack

After the last weeks online class discussion and trying to understand the relationship between Enterprise Architecture and the concept behind stacking, in my opinion stacking is the backbone to a sound enterprise architecture within an organization.

I visualize these stacks as the 4 stacks of your favorite pancakes (coconut flavor for me).
These 4 stacks need to be well placed on top of each other so that they are both pleasing to the eye (presentation/ well planned and organized) and interconnected with each other in order to maintain consistency throughout. These 4 stacks  as mentioned in my previous post are very important to the organization as a whole, with the new security layer that is becoming popular day after day. I treat this fifth layer as the cherry or strawberry on the top of my 4 pancake layers.

Stack of Pancakes depicting the Architectural Layers

Every layer is important, and all of them stacked together make a well organized and an efficient enterprise. When i compare these layers to my organization, i find that there is a lot of work that needs to be done on smoothing the business layer. Since a lot of data and technology within my organization depends on the requirements generated by the business, there is a lot of miscommunication that takes place. The result is insufficient data that carries over to the other layers within the org, such as Data, Technology, and ultimately effecting the application in itself.

I stumbled across a blog that also paints a picture of a relationship between EA and stack. ref: https://dalbanger.wordpress.com/2014/01/20/back-to-basics-the-enterprise-architecture-ea-simplified/

Although the blog talks about what its core audience is, that is limited to CIO, CTO, SA, etc, in my opinion the relationship between the enterprise layer and the stack is something that needs to be understood by every employee working in every layer of the organization, in order to ensure a consistent viewpoint flowing down the layers. (Analogy: just like the maple syrup flows through the different layers when poured from the top of the pancake, and if there are irregularities or gaps in one of the pancake layers, the syrup doesn't completely flow to the bottom of the pancake.). These holes or irregularities i used in my analogy reflect the various gaps we find time to time in our various architectural layers. These gaps need to be filled, so as to maintain the consistency throughout the EA system.

The blogger also talks about every layer being dependent on each other, that i agree with completely. I also believe that every architectural layer is dependent on the previous layer and if one of the layer has irregularities then it can effect the following dependent layers, in other words a domino effect can take place. That is why it is very important to strengthen every layer from top to the bottom in an enterprise. I also like the way the blogger used the stacking approach in the form of time frames; from Current, Target and the transitional (gaps).

As the architecture is defined within an organization, it is very essential to understand the current state of the enterprise, where the enterprise sees itself in 5 years from now (future/ target state), and what are the gaps that need to be filled during this process. This kind of reminds me of the maturity analysis tool that we used in previous classes, that help in listing down these gaps for an enterprise. A very powerful tool in my opinion.