Overview of togaf

transcript

April 13, 2023 Overview of TOGAF - Kirk Keller, University of Missouri Division of IT, Enterprise Architect - kellerki@missouri.edu

Overview of TOGAFKirk Keller, DoIT Enterprise Architect

Purpose of this presentation

• Executive summary of TOGAF• Only covers the main parts of the TOGAF framework• Meant to be a first presentation to introduce people to TOGAF• The figures you’ll see are from TOGAF 9.1• HTML version of TOGAF 9.1 can be found here:• http://pubs.opengroup.org/architecture/togaf9-doc/arch/index.html

TOGAF is not a recipe (it’s an inventory)

• The Open Group Architecture Framework (TOGAF)• A framework for enterprise architecture• TOGAF provides a high-level ‘inventory’ of:

• Architecture development processes and content• What’s needed to classify and manage EA content• What’s needed to establish an EA capability

• As an organization develops EA capabilities, it can look to TOGAF to identify gaps in development.• Do we have all the processes in place?• What information are we capturing and using?• What are we doing with the information we capture?• Who is deciding what is being done where?

TOGAF provides common ground

• TOGAF is a popular framework • 25,000 TOGAF Certified individuals as of Sept. 3,

2013• Includes people at Oracle, Cisco, IBM, BP, etc.

• Organizations can more easily rally around a commonly understood terms• Many vendors in EA space understand TOGAF

• Many have solutions tailored to TOGAF terminology

• TOGAF provides a measuring stick on EA completeness

Parts of TOGAF• Essential parts of EA:

• capture business needs to direct IT

• develop new services to enhance business capabilities

• provide information to business vital to setting future business vision.

• TOGAF describes these parts• starting with processes &

content

Architecture development method (part II)• Describes the phases any architecture

change may go through.• Some architecture work may only use some

phases at certain points in time.• Architecture work may focus on:

• capturing the strategic focus of a change.• understanding one or more levels of

architecture for a solution• planning how a change will occur• implementing a plan

• TOGAF describes these phases and their associated activities.

Architecture content framework (part IV)• Architecture work creates

artifacts to capture content.• These may be:

• Diagrams of business processes• Standards that govern• Gaps showing what we have and

what we need

• TOGAF organizes what these artifacts may be and what information they should contain.

EA: managing content

• EA work is not done when content is created• Daily operations update

content• Content informs

business of current state• TOGAF explains this

continuum of content and what tools can help manage it.

Enterprise continuum and tools (part V)

• Findings of EA should provide content we use daily.• Content is generalized to act as future

templates.• Templates are adapted for specific

use.• Reusable content guides and speeds

future planning.• Mapped solutions inform business of

current state• TOGAF suggests how this content

should be classified and what tools could be used

EA: capability

• EA processes and products are useless without capacity to create and use them.• Setting goals on capacity

helps level-set expectations of EA• A well-supported EA effort

ensures meeting of business vision.• TOGAF explains what is

needed for capacity.

Architecture capability framework (part VII)

• To do EA, there are critical capabilities you must have in place.• Skills and knowledge• Roles and responsibilities• Architecture repository for content• Essential connections to

project/portfolio mgmt.• Governance bodies

• TOGAF explains these capabilities

TOGAF = Inventory of EA

• Adoption of TOGAF saves time by providing a framework of what it takes to establish EA capabilities in an organization.

Overview of togaf

Technology