Enterprise Architecture Framework Comparison: Which Is Right for You?
Why Use an Optimized Enterprise Architecture Framework?
What to Look for in an Enterprise Architecture Framework?
Expected Parts of an Enterprise Architecture Framework
Selecting the Right Off-the-Shelf Frameworks
Enterprise Architecture Framework Selection Infographic
Selecting the Right Enterprise Architecture Framework
Enterprise Architecture Framework Comparison
How to Create an Optimized Enterprise Architecture Framework
Why use an Optimized Enterprise Architecture Framework?
The reason to use an optimized enterprise architecture framework is simple - enterprise architect's are paid to guide effective change, not invent how to do their job.
Optimized enterprise architecture framework will improve productivity and quality
First, a framework will speed up your work
Second, using a framework improves the quality of your work work
There are many different enterprise architecture frameworks. Each is built with different principles. Four of the most commonly used frameworks are TOGAF, Zachman, FEAF, and DoDAF.
We’ve created an enterprise architecture framework comparison to look at the merits of each.
Why start with an Off-the-Shelf Enterprise Architecture Framework?
The reason to start with an off-the-shelf enterprise architecture framework is simple - enterprise architect's are paid to guide effective change, not invent how to do their job.
enterprise architect's are paid to guide effective change, not invent how to do their job
No off-the-shelf framework will be optimized for you. Your enterprise and use case require tweaks. However, you should always start with a standard framework to minimize the burden. Many standard frameworks exist.
With so many different architecture frameworks to choose from, which is the right one for you?
What to look for in an Enterprise Architecture Framework?
With so many different architecture frameworks to choose from, which is the right one for you?
We take a look at your options with this enterprise architecture framework comparison.
When considering a framework look for the scaffolding that:
- exposes all the work your EA Team needs to perform
- provides supporting tools to do the work
- directly enables your enterprise architecture use case
No off-the-shelf framework will be optimized for you. Your enterprise and use case require tweaks. However, you should always start with a standard framework to minimize the burden. Many standard frameworks exist. We classify them as comprehensive, industry, or domain frameworks.
Expected Parts of an Enterprise Architecture Framework
We expect to see tools and method optimized for the use case.
- Tools
- Analytic Models
- Viewpoint Library
- Reference Architecture
- Architecture Specifications
- Deliverables
- Method
- Architecture Development Method
- Transition to Implementation
- Implementation Governance
- Enterprise Architecture Work Management
Enterprise Architecture Framework Elements Applicability to EA Use Cases
Enterprise Architecture Use Case |
||||
Strategy |
Portfolio |
Project |
Solution Delivery |
|
Tools |
||||
| Analytic Models | Required | Critical | Helpful | Optional |
| Viewpoint Library | Required | Required | Helpful | Helpful |
| Reference Architecture | Optional | Required | Required | Critical |
| Architecture Specifications | Optional | Optional | Optional | Optional |
| Deliverables | Helpful | Helpful | Helpful | Helpful |
Method |
||||
| Architecture Development Method | Helpful | Helpful | Helpful | Helpful |
| Transition to Implementation | Optional | Required | Required | Optional |
| Implementation Governance | Helpful | Required | Required | Required |
| Enterprise Architecture Work Management | Helpful | Helpful | Helpful | Helpful |
Selecting the Right Enterprise Architecture Framework
It is unlikely you will start with a single enterprise architecture framework. To select the the right enterprise architecture frameworks to start with answer the questions in the infographic to the right.
We'll use a metaphor of a shopping basket.
Do you need an Architecture Development Method?
Yes, add the TOGAF Framework to your starting set of frameworks.
No, move to the next question with an empty basket.
What is your Industry?
There are specific enterprise architecture frameworks for:
Banking, add BIAN to your basket.
The BIAN Reference Architectures will take a central role in your optimized enterprise architecture framework.
Telecommunications, add eTOM to your basket.
The eTOM Reference Architectures will take a central role in your optimized enterprise architecture framework.
Defence, if you are architecting defense operations or a defence solution add DODAF.
However, if you are working on the enterprise architecture of a defence contractor do not put TOGAF in your basket. Your product division will use DODAF for the products.
Note: You may look to one of the DODAF Family, DNDAF in Canada, MPDAF in the UK, etc. All are derivatives of DODAF and focused on long-lived systems integration.
Government, add FEAF or IndEA you your basket. Also get a copy of the guide to establishing an EA capability in the government.
The FEAF and IndEA government reference architectures will likely take a central role in your optimized enterprise architecture framework. However the use case questions may cause you to put these back on the shelf. FEAF and IndEA are optimized for the portfolio use case and are very IT-centric.
What is your General EA Use Case?
There are specific enterprise architecture frameworks for:
Strategy,
Portfolio,
Project,
Solution Delivery,
Do You Have a Focusing Enterprise Architecture Use Case?
IT Change(Modernization, Cloud, Portfolio Rationalization),
Acquisition Integration,
Interoperability,
Digital Transformation,
Is Information Security an Issue?
Yes, add the SABSA Framework to your starting set of frameworks.
With the contents of your basket you might waht to jump down to How to Create an Optimized Enterprise Architecture Framework
Enterprise Architecture Capability Reference Architecture
Download the Enterprise Architecture Capability Reference Architecture. It is the foundation of building a solid enterprise architecture team.
Your Enterprise Architecture Capability model is central to an optimized enterprise architecture capability framework.
Enterprise Architecture Framework Comparison
The Open Group Architectural Framework (TOGAF)
TOGAF is the most widely used enterprise architecture framework and accounts for over 80 percent of framework selections. Although TOGAF is common, it is often implemented very lightly.
TOGAF is a comprehensive framework.
TOGAF Framework |
||
| Tools | ||
| Analytic Models | Limited
|
|
| Practitioner's Guide | ||
| Architecture Specifications | Limited | |
| Deliverables | Topical list | |
| Method | ||
| Architecture Development Method | Comprehensive Architecture Development Method is generic method covering many enterprise architecture use cases.
Specific how-to methods include:
|
|
| Transition to Implementation | Phase E (Opportunities & Solutions) and Phase F (Implementation Planning) in Comprehensive Architecture Development Method | |
| Implementation Governance | Phase G (Implementation Governance) in Comprehensive Architecture Development Method | |
| Enterprise Architecture Work Management | Missing | |
The Zachman Framework
The Zachman Framework is a schema that focuses on six questions (why, how, what, who, where, and when) and five perspectives: (planner, owner, designer, implementer, and subcontractor). The ways these focuses interconnect and come together give a powerful insight into how a business operates.
By understanding how each point connects to the others, you create a powerful framework that allows you to streamline and optimize your operations.
However, as an EA Framework Zachman is quite limited.
Zachman Framework |
||
| Tools | ||
| Analytic Models | Missing | |
| Viewpoint Library | This is the core of the Zachman Framework | |
| Reference Architecture | Missing | |
| Architecture Specifications | Missing | |
| Deliverables | Missing | |
| Method | ||
| Architecture Development Method | Missing | |
| Transition to Implementation | Missing | |
| Implementation Governance | Missing | |
| Enterprise Architecture Work Management | Missing | |
Federal Enterprise Architectural Framework (FEAF)
FEAF, an enterprise architecture framework created by the US Federal Government. it is designed around portfolio planning.
It aims to provide five reference models.
These five reference models: performance, business, data, application, and infrastructure drive a portfolio analysis.
FEAF is an industry framework.
FEAF Framework |
||
| Tools | ||
| Analytic Models | Missing | |
| Viewpoint Library | Missing | |
| Reference Architecture | Core of FEAF
|
|
| Architecture Specifications | Limited use of concept | |
| Deliverables | Limited to completing the reference material | |
| Method | ||
| Architecture Development Method | Limited to completing the reference material. Silent on analysis or use. | |
| Transition to Implementation | Limited. While the reference models are deeply aligned to portfolio analysis how to perform the portfolio analysis is not included. | |
| Implementation Governance | Missing | |
| Enterprise Architecture Work Management | Missing | |
BIAN
BIAN, an enterprise architecture framework developed by Banking Industry Architecture Network. it is designed around portfolio planning.
BIAN is an industry framework.
BIAN Framework |
||
| Tools | ||
| Analytic Models | Missing | |
| Viewpoint Library | Missing | |
| Reference Architecture | Core of FEAF
|
|
| Architecture Specifications | Limited use of concept | |
| Deliverables | Limited to completing the reference material | |
| Method | ||
| Architecture Development Method | Limited to completing the reference material. Silent on analysis or use. | |
| Transition to Implementation | Limited. While the reference models are deeply aligned to portfolio analysis how to perform the portfolio analysis is not included. | |
| Implementation Governance | Missing | |
| Enterprise Architecture Work Management | Missing | |
Department of Defense Architecture Framework (DoDAF)
The DoDAF enterprise architecture framework was developed by the US Department of Defense to address interoperability. It provides tabular, structural and graphical means.
DODAF's architecture views form the core, and are focused on how a complex system works together. The DoDaF framework starts with clearly defined operational views, then creates specific work products products that describe how a complex system of systems fits together.
DODAF is an industry framework.
DODAF Framework |
||
| Tools | ||
| Analytic Models | Missing | |
| Viewpoint Library | Comprehensive
End-to-end viewpoint library that highlights the purpose of a complex system, parts of the system, and how the system interoperates. It is very well suited to interoperability of long-lives components. |
|
| Reference Architecture | Missing | |
| Architecture Specifications | Limited Several of the Viewpoint focus on interoperability standards and specifications |
|
| Deliverables | Limited | |
| Method | ||
| Architecture Development Method | Limited to completing the reference material. Silent on analysis or use. | |
| Transition to Implementation | Missing | |
| Implementation Governance | Missing | |
| Enterprise Architecture Work Management | Missing | |
How to Create an Optimized Enterprise Architecture Framework
Conclusion: Enterprise Architecture Frameworks
The complicated nature of business means there will be lots of different enterprise architecture frameworks that offer value. When choosing a framework to learn or implement, it’s often a good idea to choose a holistic approach.
Every framework has some areas where it excels and others where it has slight blind spots, and this is why the more you learn the different frameworks, the more innovative solutions you will be able to come up with.
As a starting point, it’s hard to beat the TOGAF framework. The industry standard approach is replacing the specific tools and keeping the architecture development method. This makes it a natural starting point for would-be enterprise architects.