As I am building out an Office of Enterprise Architecture, I often hear and get the question, “what is Enterprise Architecture?”. We see this industry wide across the world. We EA bloggers have compiled and distilled definitions for the past few years. Below are some links that show this:
- The Enterprise Architecture Definition Collection One, Two & Three
- Aggregates of Open Group and Gartner
- IT Architecture is not Enterprise Architecture
So when I think through the answer the response is always a bit complex. I think through who I am talking to and their level of knowledge in this domain and then directly to how I am going to describe. I think through the categories of activities, the Who, What, When, Where and Why decomposition and abstractions.
I then got to the point where I think to myself, why am I going through this painful exercise every other day. Isn’t there a great representation of of the Enterprise Architecture space. So naturally, I went to one of the greatest tools in an EA’s arsenal, Google. I went through blogs, articles, analyst materials and even EA frameworks. There wasn’t anything that could be my go to reference for facilitating the conversation.
So, I guess that means I have to create it, huh? That’s exactly what I did. So how did I go about it? I certainly wasn’t going to start with trying to come up with a cohesive definition that everyone would debate. Instead, I decided that I was going to take another approach.
A capability driven approach is what needs to be taken in this case. Instead of a generic definition, let’s define the space by talking about the capabilities that comprise Enterprise Architecture. This will provide the breadth and organization to describing the domain.
So what is meant by a capability? Often times this term is used in the Business Capability context. But if you is those same principles for the design of a business capability you can define a capability as:
- Abstraction of processes, activities, people and technology
- Used to provide a level of breadth without losing organization or intent
- Remove the complexities of the “lines”
- To only be the starting point, not the end to facilitate a higher level conversation about a specific domain/area
The Enterprise Architecture Capability Model (EACM)
In first draft this is what I have come up with as being representative of the Enterprise Architecture Domain. It shows the level one and two level capabilities. There will need to be more work on the level three capabilities. This is where it will get real interesting.
A great way to get people on board with the space would be as simple as using this a a quick reference. Printing it out am laminating it for cube/office walls. It has most certainly help me in my conversations.
It would be interesting to get all of your thoughts on this.