TOGAF Certified E2

8/3/2019 TOGAF Certified E2

1/12

TOGAF Certified E.2

Architecture Governance


2/12

Purpose:

The purpose of this chapter is to help you understand how to apply ArchitectureGovernance in development of an enterprise architecture.

KLP Reference:47-*, 50-*

Learning Outcome:

The Candidate must be able to:1. Explain how Architecture Governance fits within the ADM cycle2. Discuss the key success factors for putting Architecture Governanceinto practice (KLP 50.3-1)3. Discuss the factors that should be considered when setting up an ArchitectureBoard (KLP 47.3-1)

4. Explain how to operate an Architecture Board (KLP 47.4-1) (There is expectedto be some overlap with the Learning Unit covering Phase G.)

5/1/2012 TOGAF Certified E.2


3/12


Learning Outcome 1:

How Architecture Governance fits within the ADM cycle.

Definition of Architecture Governance by TOGAF:

The practice and orientation by which enterprise architectures and otherarchitectures are managed and controlled at an enterprise-wide level. It isconcerned with change processes (design governance) and operation of productsystems (operational governance).


4/12


Architecture Governance: Overview

Architecture governance is the practice and orientation by which enterprisearchitectures and other architectures are managed and controlled at anenterprise-wide level.

It includes the following: Implementing a system of controls over the creation and monitoring of all

architectural components and activities, to ensure the effective

introduction, implementation, and evolution of architectures within theorganization.

Implementing a system to ensure compliance with internal and externalstandards and regulatory obligations

Establishing processes that support effective management of the aboveprocesses within agreed parameters

Developing practices that ensure accountability to a clearly identifiedstakeholder community, both inside and outside the organization


5/12


Architecture Governance Framework:

Overview

Describes a conceptual and organizational framework for architecture governance.Architecture governance needs to be supported by an Architecture GovernanceFramework.

It is intended to assist in identifying effective processes and organizational structures,so that the business responsibilities associated with architecture governance can beelucidated, communicated, and managed effectively.


6/12


Architecture Governance Framework Conceptual Structure


7/12


Process - Required to identify, manage, audit, and disseminate all informationrelated to architecture management, contracts, and implementation

Policy Management and Take-OnAll architecture amendments, contracts, and supporting information must come undergovernance through a formal process in order to register, validate, ratify, manage, and publishnew or updated content. These processes will ensure the orderly integration with existinggovernance content such that all relevant parties, documents, contracts, and supportinginformation are managed and audited.ComplianceCompliance assessments against Service Level Agreements (SLAs), Operational LevelAgreements (OLAs), standards, and regulatory requirements will be implemented on an ongoing

basis to ensure stability, conformance, and performance monitoring. These assessments will bereviewed and either accepted or rejected depending on the criteria defined within thegovernance framework.DispensationA Compliance Assessment can be rejected where the subject area (design, operational, servicelevel, or technology) are not compliant. In this case the subject area can:1. Be adjusted or realigned in order to meet the compliance requirements2. Request a dispensationWhere a Compliance Assessment is rejected, an alternate route to meeting interim conformance

is provided through dispensations. These are granted for a given time period and set of identifiedservice and operational criteria that must be enforced during the lifespan of the dispensation.Dispensations are not granted indefinitely, but are used as a mechanism to ensure that servicelevels and operational levels are met while providing a level of flexibility in their implementationand timing. The time-bound nature of dispensations ensures that they are a major trigger in thecompliance cycle.

Continued


8/12


Monitoring and Reporting

Performance management is required to ensure that both the operational andservice elements are managed against an agreed set of criteria. This will includemonitoring against service and operational-level agreements, feedback foradjustment, and reporting. Internal management information will be considered inEnvironment Management.

Business Control

Business Control relates to the processes invoked to ensure compliance with theorganizations business policies.

Environment ManagementThis identifies all the services required to ensure that the repository-basedenvironment under pinning the governance framework is effective and efficient. Thisincludes the physical and logical repository management, access, communication,training, and accreditation of all users. All architecture artifacts, service

agreements, contracts, and supporting information must come under governancethrough a for mal process in order to register, validate, ratify, manage, and publishnew or updated content. These processes will ensure the orderly integration withexisting governance content such that all relevant parties, documents, contracts,and supporting information are managed and audited


9/12


Related phases in ADM Cycle

Preliminary Phase: Decisions aremade on how to govern theArchitecture Framework, and how tointegrate it with the existinggovernance and support models forthe organization. Decisions are alsotaken as to the type of governancerepository characteristics required.

Migration Planning(Phase F):TheImplementation Governance Model producedensures that a project transitioning intoimplementation smoothly transitions into theappropriate Architecture Governance forPhase G.

Implementation Governance(Phase G): Includes production of theArchitecture Contract which featuresprominently in Architecture Governanceas a means to ensure compliance anddrive change. Periodic compliancereviews of projects are held to review

progress and ensure that the designand implementation are in-line with thestrategic and architectural objectives.Risk monitoring should also occur inthis phase.

Architecture Change Management (PhaseH): Manages the governance process andframework for the architecture. This includesscheduling and holding meetings of theArchitecture Board. The purpose of thesemeetings is to decide how to handle requestsfor change to the architecture. These canarise either from issues found in the originalarchitecture definition and requirements, or

from external factors such as businessstrategy changes and new technologyopportunities. The Architecture Board shouldalso ensure that the ADM is being appliedcorrectly to ensure that all considerations aremade and all required deliverables areproduced.


10/12


Operational Benefits

Links IT processes, resources, and information to organizational strategies andobjectives.

Integrates and institutionalizes IT best practices.

Aligns with industry frameworks such as COBIT (planning and organizing,acquiring and implementing, delivering and supporting, and monitoring ITperformance).

Enables the organization to take full advantage of its information, infrastructure,and hardware and software assets.

Protects the underlying digital assets of the organization.

Supports regulatory and best practice requirements such as auditability, security,

responsibility, and accountability

Promotes visible risk management


11/12


Architecture Governance ScopeApplicable to complete life cycle of Business and IT System

Architecture Governance Framework is integral to the Enterprise Continuum, andmanages all content relevant both to the architectures themselves and toarchitecture governance processes.


12/12


Learning Outcome 2:

Key success factors for putting Architecture Governance into practice

Establishment and operation of best practices for submission, adoption, re-use,reporting, and retirement of architecture policies, procedures, roles, skills,organizational structures, and support services

Establishment of correct organizational responsibilities and structures to supportArchitecture Governance processes and reporting requirements.

Integration of tools and processes to facilitate take-up of processes (bothprocedural and cultural).

Management of criteria for control of Architecture Governance processes,dispensations, compliance assessments, Service Level Agreements (SLAs), andOperational Level Agreements (OLAs).

Meeting internal and external requirements for effectiveness, efficiency,confidentiality, integrity, availability, compliance, and reliability of ArchitectureGovernance-related information, services, and processes.

TOGAF Certified E2

Documents