Enterprise Architecture Stack, an interesting version.

Source: www.thesoftwaregorilla.com

http://www.thesoftwaregorilla.com/2010/05/what-is-enterprise-architecture/

One of the things I like about Enterprise Architecture is the fact that while it has been around for a number of years there is no official standard.  Because of this the field is still open for interpretation and discussion, which generates multiple ideas about what makes up EA.

This link is to a blog that discusses the author's idea of an EA stack.  It has similarities to other versions but some interesting differences.

I found it interesting that he separated out information and data architecture.  Typically these are covered in the same layer of the stack.  He breaks it out this way.

Information architecture is the process of understanding what information the business needs, how to go about delivering it, and ensuring that nothing is lost. 

...data architecture is all about understanding the nature of the data in an organization, what operates on it, and how it is stored.

I think maybe in a data-centric or data heavy organization I could see this breakdown as one might be more on the physical aspects of the data and the other more on understanding what data is actually needed in the environment.  Most organizations would probably benefit from this being a single layer in the stack to ensure that there is a clear understanding of all aspects of data by looking at it through a single lens.

Another interesting part of this version of the stack is the Specialty architecture layer.  This covers a broad range of technologies in use right now.  While most of the stack is at the 10,000 foot level, this layer brings it much closer to ground level as it looks at specific groups of technologies and how they relate to the EA process.  I do have to wonder why security was not included at this level or at any level in this stack.

I also found it interesting that the author includes data, application, and infrastructure architecture as business processes, I would personally have included them more on the technology side.  It could be the fact that he has the low level specialty architecture stack which is very much technology focused, so there needed to be more balance on the business side of the stack.

Again, this is what I like about the EA field,  As a student and practitioner of EA there is no "right" way to do things, so I could take parts that I like from this EA stack and incorporate those into my own version of what that perfect EA stack might look like.