togaf simplified - part 7 - architecture capability framework · togaf simplified - part 7 ......

1

Click here to load reader

Upload: nguyendien

Post on 16-Oct-2018

267 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: TOGAF Simplified - Part 7 - Architecture Capability Framework · TOGAF Simplified - Part 7 ... TOGAF Simplified, that gives you a short, quick reminder of each section of the TOGAF

Good e-Learning Resources : : www.goodelearning.com/downloads

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

@goodelearning /goodelearning /company/good-e-learning

THERE ARE 8 CHAPTERS IN PART 7CHAPTER 45 is an Introduction to and overview of Part VII: Architecture Capability Framework

CHAPTER 46 gives guidelines on Establishing an Architecture Capability using the ADM

How to establish and operate an Enterprise Architecture Board is covered in CHAPTER 47While ensuring that projects have Architecture Compliance is in CHAPTER 48

Defining and using Architecture Contracts is CHAPTER 49And Architecture Governance is in CHAPTER 50

CHAPTER 51 describes how to use Architecture Maturity Models to evaluate and quantify your EA maturity

CHAPTER 52 provides a set of role, skill, and experience norms in the Architecture Skills Framework

DEVELOPING ARCHITECTURE CAPABILITYFigure 45-1 shows the overall structure for a mature TOGAF Architecture Capability Framework, and Chapter 46 uses the ADM to provide a step-by-step guide on how this might be established.The Architecture Board is a cross-organization body that oversees the implementation of a successful architecture governance strategy. Its Role, Responsibilities, Set up, and Operation and explained in Chapter 47.

CONTRACTS (CHAPTER 49)TOGAF explains the role, and then describes the typical content of three kinds of Architecture Contracts:• Statement of Architecture Work – created

as a deliverable in Phase A of the ADM• Contract between Architecture Design and

Development Partners - at the beginning of Phase G (Implementation Governance)

• Contract between Architecting Function and Business Users - at the end of Phase G

COMPLIANCETOGAF gives definitions of the terms “conformant” and “compliant”, and provides levels of architecture conformance. It goes on to describe the purpose, timing, and common scenarios for Architecture Compliance Reviews (section 48.3). After this is it gives an overview of, and describes the roles and steps in, the Architecture Compliance Review Process. 48.5 Architecture Compliance Review Checklists provides a range of questions that may be used, relating to various aspects of the architecture – such as Hardware and Operating Systems, Software Services and Middleware, and Applications. Finally there are a few Architecture Compliance Review Guidelines.

MATURITY MODELS (CHAPTER 51)The overview and background sections explain why maturity models are useful in EA, before describing the US Department of Commerce (DoC) enterprise Architecture Capability Maturity Model (ACMM). This consists of 6 maturity levels: None (0), Initial (1), Under Development (2), Defined (3), Managed (4), and Measured (5).There is an example based on the 9 EA elements: architecture process; architecture development; business linkage; senior management involvement; operating unit participation; architecture communication; IT security; architecture governance; and IT investment and acquisition strategy.

SKILLS FRAMEWORK (CHAPTER 52)TOGAF explains the need and goals for a skills framework. It then describes a set of EA Roles and Skill Categories. There are 7 categories: Generic Skills; Business Skills & Methods; EA Skills; Program or Project Management Skills; IT General Knowledge Skills; Technical IT Skills; and Legal Environment. These are shown in example skill tables, against 4 proficiency levels: Background, Awareness, Knowledge, and Expert.

GOVERNANCE (CHAPTER 50)An introduction explains the need to link EA governance with governance of other enterprise-wide disciplines. It also talks about the nature and characteristics of governance.The bulk of this chapter introduces an Architecture Governance Framework (section 50.2) – explaining the overall conceptual structure and the key components of a typical organizational structure (shown in Figure 50-2).

TOGAF® Poster Series #82TOGAF Simplified - Part 7 - Architecture Capability Framework

In this poster we summarise the key points from Part V of the TOGAF documentation. It is part of a series, TOGAF Simplified, that gives you a short, quick reminder of each section of the TOGAF documentation.

Governance Environment

Develop

Enterprise Continuum

Implement Deploy

CEO/CTO

Programm Management

Offi ce

Service Management

Architecture Board

Architecture Board

Architecture Board

Architecture Board

Architecture Board

Architecture Board

Architecture Board

Architecture Board

Architecture BoardArchitecture BoardArchitecture Board

Architecture BoardArchitecture BoardImplementationProjects

Architecture BoardArchitecture BoardOperationalSystems

Chief Architect

Enterprise Architects

Diff usion

Guidance

Stewardship

MonitoringRiskManagement

ChangeConformance

Alig

nmen

t

Alig

nmen

t

Figure 50-2: Architecture Governance Framework - Organizational StructureFigure 45-1: Mature Architecture Capability

Governance Bodies

Architecture Repository

Enterprise Continuum (used to classify inputs to and outputs from the Repository)

Skilled Resources PoolProject/Portfolio

Governance

Projects/Portfolios

Professional Development

Skills

Skills Knowledge

Improves Improves

Direct

Part

icip

ate

inPa

rtic

ipat

e in

Business Capability for Architecture(operating at a level of maturity)

Measuringsuccess

Re-using building blocks and complying with standards

Populating the Repository

Sett

ing

prio

rity

and

focu

s

Del

iver

ing

alig

ned

solu

tion

s

Setting priority and focus

Possess

Assigned

Requires

Requires

Possess

Roles and Responsabilities

(both generic and specifi c to a

particular project)

Contract Business Operations

Projects/portfolios governed

against their contracts