Zachman Enterprise

framework and TOGAF

Prepared by
Egumar Letemu & Matewos chalchisa

Summited to
Nassir D. /PhD
Assoc. Professor

Contents
1.

Introduction ............................................................................................................................................................................................................. 3

2.

Zachman Framework key features ....................................................................................................................................................................... 3

1.

Matrix Rows ....................................................................................................................................................................................................... 4

2.

Matrix Columns .................................................................................................................................................................................................. 4

3.

How it works ........................................................................................................................................................................................................... 5

4.

The framework into practice ................................................................................................................................................................................... 5

5.

The Framework for the Organization ...................................................................................................................................................................... 6

6.

Weaknesses of Zachman Framework...................................................................................................................................................................... 6

7.

What is TOGAF ...................................................................................................................................................................................................... 7

8.

History of TOGAF .................................................................................................................................................................................................. 7

9.

What was new in TOGAF 9 .................................................................................................................................................................................... 7

1.

Design objectives................................................................................................................................................................................................ 0

2.

New sections....................................................................................................................................................................................................... 0

10. HOW TOGAF......................................................................................................................................................................................................... 0

11. Why TOGAF .......................................................................................................................................................................................................... 1
1.

RESULTING IN:................................................................................................................................................................................................ 2

2.

TOGAF BRIDGES THE GAP: .......................................................................................................................................................................... 2

12. What kind of "architecture" does TOGAF deal with? ............................................................................................................................................ 2

13. References ............................................................................................................................................................................................................... 3

Zachman enterprise framework

1.

Introduction
The Zachman enterprise framework was invented by John Zachman in 1980 for IBM, and
is now in the public domain. The framework borrows from business design principles in
architecture and manufacturing and provides a way of viewing an enterprise and its
information systems from different perspectives, and showing how the components of the
enterprise are related.
In todays complex business environments, many large organizations have great difficulty
responding to change. Part of this difficulty is due to a lack of internal understanding of
the complex structure and components in different areas of the organization, where legacy
information about the business is locked away in the minds of specific employees or
business units, without being made explicit.
The Zachman framework provides a means of classifying an organizations architecture. It
is a proactive business tool, which can be used to model an organizations existing
functions, elements and processes and help manage business change. The framework
draws on Zach mans experience of how change is managed in complex products such as
aero planes and buildings.
Although the framework can be used for information systems architecture (ISA) and is
Widely adopted by systems analysts and database designers
The framework provides a consistent and systematic way of describing an enterprise and
has been employed in many large organizations, such as Volkswagen, General Motors,
Bank of America and Health Canada.

2.

Zachman Framework key features

Some of the features of zachman frame works are Reference model for architecture
frameworks, Supports all architecture domains (column),Supports multiple perspectives
(row),Supports multiple stakeholder views, Not prescriptive about multiple modeling

methods, Enables use of existing (legacy) models, Enables re-use of model artefacts
and Enables a common vocabulary for IT and business people.
Zachman is an implicit process. The row of frame work presents different perspectives
of the enterprise , different views of the enterprise and different roles in the
enterprise.

1.

Matrix Rows
Each row represents a distinct view of the organization, from the perspective of
different audiences. These are ordered in a desired priority sequence.
A row is allocated to each of the following audiences:
1. Planner understands the business scope and can offer a contextual view of the
enterprise.
2. Owner understands the business model and can provide a conceptual view of
the enterprise.
3. Builder - develops the system model and can build a logical view of the
enterprise.
4. Designer produces the technology model and can provide a physical view of
the enterprise.
5. Integrator will understand detailed representations of specific items in the
business, although they will have an out-of-context view of the enterprise.
6. User provides a view of the functioning enterprise, from the perspective of a
user (e.g., an employee, partner or customer).

2.

Matrix Columns
1

What (data) describes the entities involved in each perspective of the enterprise.
Examples include equipment, business objects and system data.

How (functions) shows the functions within each perspective.

Where (networks) shows locations and interconnections within the enterprise.
This includes major business geographical locations, networks and the playing field.
4 Who (people) represents the people within the enterprise and metrics for assessing
their capabilities and performance. The design of the enterprise organization has to do
with the allocation of work and the structure of authority and responsibility.
5 When (time) represents time, or the event relationships that establish performance
criteria. This is useful for designing schedules, the processing architecture, the control
architecture and timing systems.
6 Why (motivation) describes the motivations of the enterprise. This reveals the
enterprise goals, objectives, business plan, knowledge architecture, and reasons for
thinking, doing things and making decisions.
2
3

3.

How it works
The easiest way to understand the Zachman Enterprise architecture framework is to
view it as a classification scheme represented visually as a table or matrix, with
columns and rows. Each cell within the matrix provides a unique model or
representation of the enterprise .into

4.

The framework into practice

A logical point to start would be at the top left of the matrix and work your way down
and across the table. The relevant business information or models used to represent
a specific area of the business may already exist in formalized business plans, project
schedules, system specifications, procedure guides, organization charts and other
corporate documents.
As you go through the rows and columns of the matrix, there will be gaps that need to
be filled, where implicit information known only to a single person or a few experts
needs to be made explicit and available to a wider audience. There may be instances of
overlap or redundancy.

As a technical communicator your role would be to ensure the information you gather
is comprehensive, reliable and appropriately categorized. At the same time, the
business objective in this would be to gain a better understanding of the organizations
architecture, with the goal of managing change and reducing redundancies and
overlaps.
The information could be stored in a database or other file management system
that allows easy retrieval. The categories of the matrix will help the enterprise not
only to clearly categorize information, but also to easily retrieve relevant
information.

5.

The Framework for the Organization

The Zachman enterprise framework can be viewed as a tool for creating knowledge
and clarifying thinking, and as an aid in analysis and decision-making. It is a strategic
information asset that can help shape an organization. The benefits include:
Readily available documentation for the enterprise
Ability to unify and integrate business processes and date across the enterprise
Increased business agility by lowering the complexity barrier
Reduced solution delivery time and development costs by maximizing reuse of
enterprise models
Ability to create and maintain a common vision of the future shared by both the
business and IT communities.

6.

Weaknesses of Zachman Framework

Although the Zachman Framework is amongst the most popular
Frameworks of architectures in the field of Enterprise Architecture but it have some
drawbacks which researchers have shown concern for in the past. The Zachman
Framework is very generic and can over simplify some of the enterprise issues such
as its business performance and behavior, although it takes into consideration

decision support systems, analytical processing and data exploration. Some

researchers have argued in the past that it is not an easy task to build up
architectures using the Zachman Framework for architecture. Since the framework is
firmly constrained using rigorous formal rules which govern the frameworks integrity
some difficulties appear in building up architectures if a full coverage on the
framework is intended.
Fatolahi and Shams (2006) have summarized these difficulties in three
Major problems:
A lack of methodology covering all the aspects of the framework.
A lack of repository storing the framework in accordance with the integrity
rules.
Lack of a popular modeling notation for all of the frameworks columns. Leon
Kappelman, Professor and Director of Information Systems Research Center,
College of Business, University of North Texas, pointed out that IT lives in
the lower left-hand corner of the Zachman Framework, but enterprise
management is at the upper-right corner, this communication gap needs to
be closed to have a real alignment in the Information Age.

TOGAF Best Fit Architectural Style Why and How?

7.

What is TOGAF

The Open Group Architecture Framework is a framework a detailed method and a set of supporting tools for
developing enterprise architecture for use within that organisation
TOGAF is developed and maintained by members of The Open Group, working with the architecture forum.

8.

History of TOGAF

TOGAF was introduced since 1994 the US Department of Defence gave their Technical Architecture Framework for
Information Management (TAFIM) to TOGAF for development. In 1995 TOGAF version 1 was released and currently
version 9 in use which was released 2009.

9.

What was new in TOGAF 9

1.

Evolution not revolution

No change to the top level processes
Interoperability between TOGAF 8 and 9
Stronger links to business
Strategic Planning & Deployment decisions
Easier to use
A More formal meta-model
More guidelines and techniques

2.

Design objectives

New sections

Architecture Planning
Content Framework and Metamodeling
Capability Based Planning
Business Transformation Readiness
Architecture Repository
Stakeholder Management
Security
SO

10. HOW TOGAF

1. TOGAF provides a common sense, practical, prudent, and effective method of developing
IT architecture. In addition to this TOGAF specifically does consists of two main parts:
A. The TOGAF Architecture Development Method (ADM), which explains how to derive
an organization-specific IT architecture that addresses business requirements.
The ADM provides:
A reliable, proven way of developing the architecture
Architecture views which enable the architect to ensure that a complex set of
requirements are adequately addressed
A worked example and linkages to practical case studies
Tools for architecture development
B. The TOGAF Foundation Architecture -- an architecture of generic services and functions
that provides a foundation on which specific architectures and architectural building
blocks can be built. This Foundation Architecture includes:
C. The TOGAF Standards Information Base (SIB), a database of open industry standards
that can be used to define the particular services and other components of an
organization-specific architecture
1. Organizations wishing to reduce the time, cost, and risk of implementing
multi-vendor solutions that integrate within and between enterprises need
The Open Group as their key partner.
The Open Group brings together the buyers and suppliers of information systems
world-wide, and enables them to work together, both to ensure that information
technology solutions meet the needs of customers, and to make it easier to integrate
information technology across the enterprise.

The Open Group Architectural Framework is a key enabler in this task.

Yes, TOGAF itself is freely available. But how much will you spend on developing
or updating your technical architecture using TOGAF? And how much will you spend
on procurements based on that architecture?
The price of Open Group membership is insignificant in comparison with these amounts.
In addition to the general benefits of membership, as a member of The Open Group you
will be eligible to participate in The Open Group Architecture Program, which is the
development program within which TOGAF is evolved, and in which TOGAF users come
together to exchange information and feedback.
Members of the Architecture Program gain:

Immediate access to the fruits of the current year's TOGAF work program (not publicly
available until publication of the next edition of the TOGAF document) - in effect, the
latest information on TOGAF, as opposed to information that is up to a year old
Exchange of experience with other customer and vendor organizations involved in IT
architecture in general, and networking with architects using TOGAF in significant
architecture development projects around the world.
Peer review of specific architecture case study material

11. Why TOGAF

There are creating things that every enterprise wants to expand their capabilities;
want to increase their efficiency; want to overtake the competition, streamline and
cut unnecessary costs. Quite simple TOGAF helps you to do just that many large
enterprises grow as they go. They may have then brought or merged with other
companies and now have a global presence. This introduce new challenges with
information required to go further and faster which is not easy to co-ordinate. This has
some meant that their capabilities are fragmented duplicated or going in the wrong direction.
With a lots of legacy systems, performing disjointed tasks around different departments,
locations and organizations.
TOGAF changes that successfully and seamlessly by taking everything in the right direction.
Its about getting instant boundary less information which means its about getting the
right information, to the right people, in the right place, at the right time and in the
right format. Its about getting what you need when you need it (security).
It plans the journey to take you to new operating capabilities.
It helps you to work with in realistic timescales and increase your capabilities in
line with your priorities and needs.
It gives you a clearer picture of high value outcomes and potentially high risks

1|P age

1.

It covers your regulatory and compliance concerns ensuring your business is

fit for purpose
It gives you a series of packaged, building BLOCKS that you can re-use and
re-shape however you need to
It gives you a set of tools and techniques to ensure that your solutions do this
job that you need them to

RESULTING IN:
A focused workforce improved performance reduced overheads increased capability and New
opportunities.

2.

TOGAF BRIDGES THE GAP:

Allowing you to see how day to day operations and ongoing projects are working towards
delivering the goal of where you need to be in N years time.
Where do you need to be in N years time?

12. What kind of "architecture" does TOGAF deal with?

There are several kinds of architecture within the world of Information Technology, so it is
important to be clear about what kind of architecture TOGAF is aimed at supporting and
what it is not.
There are four types of architecture that are commonly accepted as subsets of an overall
Enterprise Architecture:
business architecture;
data/information architecture;
application (systems) architecture; and

Information Technology (IT) architecture.

Basically, TOGAF is designed to support the last of these - the development of an
Information Technology (IT) architecture. It also addresses those parts of the business,
data and application architectures that impact on the development of the IT architecture.
Its main focus is on the software infrastructure intended to support the deployment of core,
mission-critical applications. This type of software is sometimes referred to as "middleware",
and the architecture as a "technical architecture".
The other types of architecture have close ties with a TOGAF-developed IT architecture:
A business (or business process) architecture - this defines the business
strategy, governance, organisation, and key business processes.
The IT architecture needs to closely reflect the business goals of the organization.
Indeed, specific techniques (business scenarios) should be used to ensure that the
business goals are properly understood by the IT architect, and reflected in the IT
architecture developed using TOGAF. TOGAF itself covers the development of a
business architecture to the extent needed to guide the development of the IT architecture.
An applications architecture - this kind of architecture provides a blueprint for the
individual application systems to be deployed, their interactions, and their relationships
to the core business processes of the organization. There are several significant synergies
between this type of architecture and a TOGAF-designed IT architecture:
The applications will use the services of a TOGAF-designed technical architecture
to achieve essential system-wide features such as interoperability, security, and
manageability of the overall IT environment;
2|P age

 In some cases, specialized services used by the applications will need to be designed
into the underlying infrastructure.
In other cases, software that most organizations would consider to be in the
applications space is required to be built into the infrastructure, for reasons of efficiency of
performance
The IT architecture will typically need to support the integration of different application
architectures, if the latter have developed over time independently from one another.
In many enterprises, little attention has been paid in the past to the need to exchange
information between applications, or to reliably create new information from data
derived from two or more applications. The business processes that each application
architecture supports are also often independent.
A data architecture - this describes the structure of an organization's logical and
physical data assets and data management resources.
The data architecture needs to be understood by the IT architect, to ensure that the
storage and access requirements can be supported effectively.
The IT architecture needs to take into account the data and its required movements,
to ensure that the infrastructure services (e.g., directory) can support them.
The IT architecture will also generate requirements on the data architecture,
e.g., to ensure that required data movements are supported.

13. References

3|P age

John Zachman, 1987, The Zachman Framework for

Enterprise Architecture.
The Open Group:TOGAF Enterprise Edition.Version
8.1.1:
The Open Group:TOGAF Version 9.1; available at
http://www.opengroup.org/architecture/togaf9--
doc/arch/;The Open Group, 2011.

Stan Loche, 2003, The Zachman Enterprise

Architecture, Metadata Systems Software Inc.

Alex Hoffman: What is the Zachman Framework for

Enterprise Architecture?
http://weblogs.asp.net/ahoffman/archive/2004/10/21/
Reference_3A00_- What-is-the-Zachman-Frameworkfor-Enterprise-Architecture_3F00_.aspx
Zachman Framework Applied to Administrative
Computing Services:
http://apps.adcom.uci.edu/EnterpriseArch/Zachman/
Zachman Framework Implementation:
http://www.mega.com/index.asp/l/en/wp/mega_zachm
an

4|P age