You are on page 1of 1

Good e-Learning Resources :: www.goodelearning.

com/downloads

TOGAF Poster Series #48


TOGAF and Other Architecture Frameworks
by Roger Evernden

TOGAF is intended for use with any other architecture framework, and its documentation repeatedly
states that TOGAF should be customized to meet organization-specific needs. But pre-defined architecture
frameworks like TOGAF are not designed in a way that makes it easy to reconfigure their content to your
specific needs! How do you combine elements from two or more frameworks? Our poster explains!
EA is a complex subject. A framework is a thinking & management tool, used to make sense of this complexity & manage changes
to architectures. TOGAF itself is really a framework of frameworks rather than a single framework. This is because it is
impossible to visualize the complexity of EA in a single diagram or framework there would be too many dimensions or factors to
consider them all at the same time!
An architecture framework establishes a common practice
for using, creating, interpreting, and analyzing architecture
descriptions within a particular domain of application or
stakeholder community. ISO/IEC/IEEE 42010 formalizes a
framework as a set of predefined, interconnected viewpoints.
[Source: ISO/IEC/IEEE 42010 standard]

But pre-defined frameworks like TOGAF, the Zachman


Framework, Information FrameWork (IFW), or the Department
of Defence Architecture Framework (DoDAF) are all very
different! We need a simple way to identify the factors we
need from each framework, & then combine them to create
several relevant checklists or frameworks.

Combining TOGAF with other architecture frameworks is like comparing apples with oranges it is hard to see the similarities,
overlaps or differences.
We need a common set of fundamental factors a meta-framework that makes it easy to deconstruct pre-defined frameworks
(such as TOGAF or Zachman) and combine the elements that we need to create a set of multiple integrated architecture
frameworks (MIAF) that are designed to work together.
GOVERNANCE FW.

PROCESS

PRESENTATION

RESPONSABILITY

EVOLUTION

UNDERSTANDING

PROCESS

CONTENT FW.
CATEGORIES

ROADMAP FW.
CATEGORIES

EVOLUTION

KNOWLEDGE

TOGAF & other


Architecture Frameworks

Meta-framework of
fundamental factors in EA

Lets look at one factor:


Categories. TOGAF has
four high-level domains
(business, data, application
& technology), which
are further divided into
topics such as Motivation,
Function, & Platform
Services. This can be found
in the Content Framework
and metamodel. Similar
subject areas or categories
can be found in the Zachman
Framework. We then
deconstruct them into a
combined set of categories.

@goodelearning

/goodelearning

STAKEHOLDER FW.
CATEGORIES

RESPONSABILITY

UNDERSTANDING

CATEGORIES

METAMODEL FW.
META LEVELS

META LEVELS

RESPONSABILITY

CATEGORIES
(subject areas)

DEVELOPEMENT FW.

PROCESS

CATEGORIES

Multiple Integrated Architecture


Frameworks tailored to needs

CATEGORIES
(subject areas)
Organisation
Motivation
Capability
Responsibility
Location
Business
Distribution
Function
Process
Data
Application
Technology
Technology Components
Platform Services

/company/good-e-learning

We now have a common


hierarchical checklist of all
domains and sub-domains
in scope. This standard
list can then be used to
create tailored architecture
frameworks for our specific
needs. Categories are also
easily be combined with
other factors to create other
frameworks.

Free Resource Library


www.goodelearning.com

Good e-Learning 2015. ArchiMate, The Open Group and TOGAF are registered trademarks of the Open Group in the United States and other countries
Source: The eight fundamental factors in EA Information First, Roger & Elaine Evernden, Butterworth Heinemann, 2003

You might also like