Togaf Report

7/28/2019 Togaf Report

1/18

Prepared By: Ernest Cunningham

Date Prepared: 8 April 2013

Word Count: 1316

An Introduction to

The Open Group Architecture Framework


2/18

Executive Summary

The Open Group Architecture Framework (TOGAF) is an industry leading enterprisearchitecture (EA) developed by a consortium of global organisations and institutions whoare leaders in their elds.

This document aims to give you an understanding of:

What is TOGAF.

Its origin and future.

How is it used and who uses it.

How it relates to EA.

How it relates to IT.

An Introduction to The Open Group Architecture Framework 1


3/18

What is TOGAF

TOGAF is a comprehensive framework for developing enterprise architecture.

The Open Group (TOG) is a consortium of over 400 organisations operating throughoutthe world. They come from diverse sectors such as hardware and software vendors,training, nancial and education institutions as well as various government departments.

TOG is responsible for business process standard specications and certication.Covering enterprise architecture and management, UNIX specications and standards aswell as various service and security frameworks.


TOG Member Organisations


4/18

What is Enterprise Architecture

EA describes an enterprise current state. This includes:

What, when and how an enterprise does business.

Its governance structure.

The software, hardware, tools used.

The data and business models and analysis of them.

The business vision and goals.

An enterprise is any organisation or part thereof (or multiple organisations) that sharecommon business or operational goals. According to the current TOGAF manual:

TOGAF denes enterprise as any collection of organizations that has acommon set of goals. For example, an enterprise could be a government agency, a whole corporation, a division of a corporation, a single department,or a chain of geographically distant organizations linked together by commonownership.

The term enterprise in the context of enterprise architecture can be used to denoteboth an entire enterprise encompassing all of its information and technology services,processes, and infrastructure and a specic domain within the enterprise. In bothcases, the architecture crosses multiple systems, and multiple functional groups withinthe enterprise. (Open Group (Organization), 2011, p. 5)

The practice of developing EA

TOGAF denes a framework for developing EA. In practice, developing EA helps youexecute change toward your desired business vision and outcomes while reacting tomarket forces in a planned and structured manor.

TOGAF will tell you what to do but not how you do it and provides you with usefulchecklists and meta models



5/18

The Origin and Future of TOGAF

The rst version of TOGAF was released in 1995. It was based on the Technical Architecture Framework for Information Management (TAFIM) developed by the United

States Department of Defence (DoD).

The DoD gave The Open Group explicit permission and encouragement tocreate TOGAF by building on the TAFIM, which itself was the result of many

years of development effort and many millions of dollars of US Government investment. (Open Group (Organization), 2011, p. 3)

TAFIM vs TOGAF

TAFIM provided enterprise-level guidance for the evolution of the DoDTechnical infrastructure. It identies the services, standards, concepts,components, and congurations that can be used to guide the development of technical architectures that meet specic mission requirements. ("TAFIM -Wikipedia, the free encyclopedia", n.d., para. 2)

While TAFIM focussed on the architecture of information systems, TOGAF expanded on itto also include:

Architecture vision.

Business and technology architecture.

Implementation governance.

Architecture change management.

http://en.wikipedia.org/wiki/Requirementshttp://en.wikipedia.org/wiki/Requirementshttp://en.wikipedia.org/wiki/Infrastructurehttp://en.wikipedia.org/wiki/Infrastructure


6/18

TOGAF Development Timeline

Between 1995 - 2001 TOG released a new version each year marking TOGAFmilestones. By v8.0 in 2003, TOGAF had developed into a matured enterprise framework

leading on to less frequent updates.

YEAR VERSION DETAILS

1986 DoD starts developing TAFIM

1995 v1.0 X/Open Architectural Framework proof of concept

1996 v2.0 Proof of application

1997 v3.0 Relevance to practical architectures

1998 v4.0 Enterprise Continuum1999 v5.0 Architecture Requirements

2000 v6.0 Architecture Views

2001 v7.0 Technical Edition

2003 v8.0 Enterprise Edition

2006 v8.1 Enterprise Edition updated

2009 v9 Enterprise Edition updated

2011 v9.1 Enterprise Edition updated

TOGAF Future Direction

Bringing TOGAF to maturity took eight years and eight versions. TOGAF is now in anevolutionary state where its focus is now on adapting to the business world and thechanging needs of EA. One area that is being discussed as a future inclusion is theenhancement of Quality of Service.



7/18

How is it used and who uses it.

As stated earlier in this document, TOGAF is used by enterprise architects to design thearchitecture of an enterprises future state and plan and manage the evolution to its future

state.

TOGAF is based around its Architecture Development Model (ADM).

The ADM can be broken down to to seven areas of concern:

Preliminary Phase

Architecture Vision

Business, Information Systems and Technology Architecture

Solution Selection and Implementation Planning

Governance

Change Management

Requirements Management

TOGAF ADM (Open Group (Organization), 2011, p. 48)



8/18

Preliminary Phase

The Preliminary phase is where you dene what the enterprise does, how it does it, andunderstand the current organisational architectural frameworks.

This Preliminary Phase is about dening where, what, why, who, and how wedo architecture in the enterprise concerned. (Open Group (Organization),

2011, p. 58)



9/18

Architecture Vision

The Architecture Vision phase is about:

Dening the scope.

Identifying stakeholders.

Communicating the Architecture Vision.

Getting approval.

Besides developing an overall Architecture Vision, this phase is about stakeholder buy-in. This is done by identifying and communicating how the new EA aligns with thebusinesses strategic objectives and the benets to be achieved through itsimplementation. This includes benets to the enterprises bottom line and improvementsto future capability.



10/18

Business, Information Systems and Technology Architecture

The Business, Information Systems and Technology Architecture is driven by businessand operational requirements.

Each architecture addresses specic areas of the enterprises requirements:

Business Architecture

Requirements dened by the enterprise strategy, governance, operational,and key business processes of the aspired future state. The decisions hereare used to identify the requirements of the Information Systems and

Technology Architectures. Therefor, this is the rst architecture to bedened.

Information Systems Architecture

Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprises Information Systems Architecture will enable the Business Architecture and the Architecture Vision... (Open Group (Organization), 2011, p. 94)

What data to collect, the tools/applications used, how data is stored andmanipulated to meet the business architecture requirements.



11/18

Technology Architecture

The software and hardware used in the enterprise to meet the businessarchitecture requirements.

Solution Selection and Implementation Planning

This phase is about getting into specics:

Generating an Architectural roadmap (planning for change).

Create the project implementation plans

Plan specic projects based on requirements.

Identifying the appropriate technologies. Cost benet analysis.

The process requires the architect to always be reviewing the plans and decisions againstthe architecture vision and requirements.



12/18

Implementation Governance

Implementation governance runs parallel to development and implementation of the EA.

Its purpose is to ensure:

Specic projects continue to t the EA requirements.

Budgets are tracked.

Issue resolution processes are documented

Roles and responsibilities are well dened.

Conform to the enterprises governance structures and guidelines.

It is here that all the information for successful management of the var ious implementation projects is brought together. Note that, in parallel with PhaseG, there is the execution of an organizational-specic development process,where the actual development happens. (Open Group (Organization), 2011,

p. 150)



13/18

Change Management

The goal of an architecture change management process is to ensure that the

architecture achieves its original target business value. This includes managing changes to the architecture in a cohesive and architected way.(Open Group (Organization), 2011, p. 158)

Change management documents how to decide if a change supports the originalarchitecture and requirements or whether there is need to formally initiate a newarchitecture evolution cycle. (Open Group (Organization), 2011, p. 158)



14/18

Requirements Management

Requirements management is not a phase itself. It is in-fact the process of managingrequirements throughout the ADM lifecycle.

TOGAF suggests a meta-model for documenting and storing requirements information ina requirements repository. The repository is not a static set of requirements, but exibleand helps drive each phase of the ADM model.

As indicated by the Requirements Management circle at the center of the ADM graphic, the ADM is continuously driven by the requirements management process. (Open Group (Organization), 2011, p. 168)



15/18

Relevance in New Zealand

Equinox IT (http://www.equinox.co.nz) is the only local company delivering TOGAF 9certication training in New Zealand. They conduct regular 3 day training seminars in

Wellington and Auckland.Soltius (http://www.soltius.co.nz) is a SAP provider in New Zealand and is TOGAF 9certied. They actively use the TOGAF methodology when accessing their clients needs.

Although no other examples of TOGAF relevancy in New Zealand could be found, it wouldbe unwise to assume that TOGAF is not used by many enterprise architects hereconsidering its wide acceptance globally.

http://www.soltius.co.nz/http://www.soltius.co.nz/http://www.equinox.co.nz/http://www.equinox.co.nz/


16/18

How it relates to EA

According to an Infosys report between 2006 and 2009, 32% of companies consultedstated TOGAF was their preferred EA framework. ("Survey shows TOGAF driving business

change strategy - Computer Business Review", 2009)

"Survey shows TOGAF driving business change strategy - Computer Business Review"goes on to note that just like ITIL is the standard for operations standard for service levelmanagement, TOGAF has become a standard for architecting technology and businesschange.

TOGAF was developed and is maintained by some of the largest companies and mostinuential institutions globally in a broad range of sectors. Put simply, TOGAF is widelyaccepted, respected and implemented globally by the EA community. It is as relevant toEA as ITL is to IT service management.



17/18

How it relates to IT

TOGAF is an IT driven methodology. Although TOGAFs whole model is base aroundenterprise change and not specically IT, it advocates the use of IT to enable change.

Although each phase has some IT specic requirements (such as tools used to managechange), the Information Systems Architecture and Technology Architecture phasesdirectly address the hardware, software and data systems to be used to support theBusiness Architecture.

Although the TOGAF manual specically states to not think of TOGAF as a softwaredevelopment methodology, it bears striking familiarity to how software architects (SA)design software solutions. TOGAF ADM could easily be summed up as dening scope,requirements, design and implement and support phases. This close close assimilationsurely helps with SA buy-in and promotes a level of understanding of the EA processes.



18/18

References

Open Group (Organization) (2011). TOGAF Version 9.1. Zaltbommel: Van HarenPublishing.

The Open Group Architecture Framework - Wikipedia, the free encyclopedia. (n.d.).Retrieved May 23, 2013, from http://en.wikipedia.org/wiki/

The_Open_Group_Architecture_Framework#History

TAFIM - Wikipedia, the free encyclopedia. (n.d.). Retrieved May 23, 2013, from http:// en.wikipedia.org/wiki/TAFIM

Survey shows TOGAF driving business change strategy - Computer Business Review.(2009, March 11). Retrieved May 20, 2013, from http://www.cbronline.com/news/ survey_shows_togaf_driving_business_change_strategy_110309
http://en.wikipedia.org/wiki/TAFIMhttp://en.wikipedia.org/wiki/TAFIMhttp://en.wikipedia.org/wiki/TAFIMhttp://en.wikipedia.org/wiki/TAFIMhttp://en.wikipedia.org/wiki/The_Open_Group_Architecture_Framework#Historyhttp://en.wikipedia.org/wiki/The_Open_Group_Architecture_Framework#Historyhttp://en.wikipedia.org/wiki/The_Open_Group_Architecture_Framework#Historyhttp://en.wikipedia.org/wiki/The_Open_Group_Architecture_Framework#History

Togaf Report

Documents

Togaf Report