final zachman and togaf enterprise framework

7/24/2019 Final Zachman and TOGAF Enterprise Framework

http://slidepdf.com/reader/full/final-zachman-and-togaf-enterprise-framework 1/12

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, andis now in the public domain. The framework borrows from business design principles inarchitecture and manufacturing and provides a way of viewing an enterprise and itsinformation systems from different perspectives, and showing how the components of the

enterprise are related.In today‟s complex business environments, many large organizations have great difficultyresponding to change. Part of this difficulty is due to a lack of internal understanding ofthe 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 orbusiness units, without being made explicit.

The Zachman framework provides a means of classifying an organization‟s architecture. Itis a proactive business tool, which can be used to model an organization‟s existingfunctions, elements and processes and help manage business change. The frameworkdraws on Zach man‟s experience of how change is managed in complex products such asaero 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 andhas 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 architectureframeworks, 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 artefactsand Enables a common vocabulary for IT and business people.Zachman is an implicit process. The row of frame work presents different perspectivesof the enterprise , different views of the enterprise and different roles in theenterprise.

1. Matrix Rows

Each row represents a distinct view of the organization, from the perspective ofdifferent 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 theenterprise.

2. Owner – understands the business model and can provide a conceptual view ofthe enterprise.

3. Builder - develops the system model and can build a logical view of theenterprise.

4. Designer – produces the technology model and can provide a physical view ofthe enterprise.

5.

Integrator – will understand detailed representations of specific items in thebusiness, 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 auser (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.



2 How (functions) shows the functions within each perspective.3 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 dowith the allocation of work and the structure of authority and responsibility.

5 When (time) represents time, or the event relationships that establish performancecriteria. This is useful for designing schedules, the processing architecture, the controlarchitecture and timing systems.

6 Why (motivation) describes the motivations of the enterprise. This reveals the

enterprise goals, objectives, business plan, knowledge architecture, and reasons forthinking, doing things and making decisions.

3. How it works

The easiest way to understand the Zachman Enterprise architecture framework is toview it as a classification scheme represented visually as a table or matrix, withcolumns and rows. Each cell within the matrix provides a unique model orrepresentation 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 downand across the table. The relevant business information or „models‟ used to representa specific area of the business may already exist in formalized business plans, projectschedules, system specifications, procedure guides, organization charts and othercorporate documents.

As you go through the rows and columns of the matrix, there will be gaps that need tobe 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 ofoverlap or redundancy.



As a technical communicator your role would be to ensure the information you gatheris comprehensive, reliable and appropriately categorized. At the same time, thebusiness objective in this would be to gain a better understanding of the organization‟s architecture, with the goal of managing change and reducing redundancies andoverlaps.

The information could be stored in a database or other file management systemthat allows easy retrieval. The categories of the matrix will help the enterprise notonly to clearly categorize information, but also to easily retrieve relevantinformation.

5. The Framework for the Organization

The Zachman enterprise framework can be viewed as a tool for creating knowledgeand clarifying thinking, and as an aid in analysis and decision-making. It is a strategicinformation 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 ofenterprise models

• Ability to create and maintain a common vision of the future shared by both thebusiness and IT communities.

6. Weaknesses of Zachman Framework

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



decision support systems, analytical processing and data exploration. Someresearchers have argued in the past that it is not an easy task to build uparchitectures using the Zachman Framework for architecture. Since the framework isfirmly constrained using rigorous formal rules which govern the framework‟s integritysome difficulties appear in building up architectures if a full coverage on theframework is intended.Fatolahi and Shams (2006) have summarized these difficulties in threeMajor 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 framework‟s columns. Leon

Kappelman, Professor and Director of Information Systems Research Center,College of Business, University of North Texas, pointed out that IT lives inthe lower left-hand corner of the Zachman Framework, but enterprisemanagement is at the upper-right corner, this communication gap needs tobe 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 organisationTOGAF 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 forInformation Management (TAFIM) to TOGAF for development. In 1995 TOGAF version 1 was released and currentlyversion 9 in use which was released 2009.

9. What was new in TOGAF 9



1. Design objectives

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. New sections

Architecture Planning

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

Security SO

0. 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 derivean 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 buildingblocks can be built. This Foundation Architecture includes:

C. The TOGAF Standards Information Base (SIB), a database of open industry standardsthat can be used to define the particular services and other components of anorganization-specific architecture

1. Organizations wishing to reduce the time, cost, and risk of implementingmulti-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 systemsworld-wide, and enables them to work together, both to ensure that informationtechnology solutions meet the needs of customers, and to make it easier to integrateinformation technology across the enterprise.



a g e

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 developingor 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 youwill 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 cometogether to exchange information and feedback.

embers of the Architecture Program gain:

Immediate access to the fruits of the current year's TOGAF work program (not publiclyavailable until publication of the next edition of the TOGAF document) - in effect, thelatest information on TOGAF, as opposed to information that is up to a year oldExchange of experience with other customer and vendor organizations involved in ITarchitecture in general, and networking with architects using TOGAF in significantarchitecture development projects around the world.

Peer review of specific architecture case study material

1. 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 largeenterprises grow as they go. They may have then brought or merged with othercompanies and now have a global presence. This introduce new challenges withinformation required to go further and faster which is not easy to co-ordinate. This hassome 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.It‟s about getting instant boundary less information which means it‟s about getting the right information, to the right people, in the right place, at the right time and in the

right format. It‟s 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



a g e

It covers your regulatory and compliance concerns ensuring your business isfit 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

1. RESULTING IN:

A focused workforce improved performance reduced overheads increased capability and Newopportunities.

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?

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

There are several kinds of architecture within the world of Information Technology, so it isimportant to be clear about what kind of architecture TOGAF is aimed at supporting – andwhat it is not.

There are four types of architecture that are commonly accepted as subsets of an overallEnterprise 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 anInformation 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 thebusiness goals are properly understood by the IT architect, and reflected in the ITarchitecture 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 relationshipsto the core business processes of the organization. There are several significant synergiesbetween this type of architecture and a TOGAF-designed IT architecture:

The applications will use the services of a TOGAF-designed technical architectureto achieve essential system-wide features such as interoperability, security, andmanageability of the overall IT environment;



a g e

In some cases, specialized services used by the applications will need to be designedinto 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 ofperformance

The IT architecture will typically need to support the integration of different applicationarchitectures, 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 dataderived from two or more applications. The business processes that each applicationarchitecture supports are also often independent.

A data architecture - this describes the structure of an organization's logical andphysical data assets and data management resources.

The data architecture needs to be understood by the IT architect, to ensure that thestorage 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.

3. References

John Zachman, 1987, The Zachman Framework forEnterprise 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-Framework-

for-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

http://www.opengroup.org/architecture/togaf9--%E2%80%90doc/arch/;The



http://weblogs.asp.net/ahoffman/archive/2004/10/21/Reference_3A00_-What-is-the-Zachman-Framework-for-Enterprise-Architecture_3F00_.aspx







http://apps.adcom.uci.edu/EnterpriseArch/Zachman/





http://www.mega.com/index.asp/l/en/wp/mega_zachman



















a g e

final zachman and togaf enterprise framework

Documents