Nature, levels, and framework of Architecture Governance

Governing is not managing

ISO/IEC 38500, as quoted by the Study Guide, sees governance as a system that directs and controls the present and future state. TOGAF describes it as a decision-making process with a clear structure of relationships, serving stated goals while taking transparency and fairness toward all parties into account.

The boundary with management lies in fiduciary responsibility and sustainability: management organizes execution, governance makes sure business is conducted properly. The emphasis is not on visible control or rigid rule enforcement, but on effective use of resources to sustain strategic objectives.

In practice, defining governance means stating, for each type of decision, who is responsible, who is involved, and who is accountable.

What Architecture Governance covers

In the TOGAF definitions, Architecture Governance is the practice that monitors and directs architecture-related work to deliver the desired outcomes while respecting principles, standards, and roadmaps. It applies to Enterprise Architectures and other architectures, across the whole enterprise. It spans four areas:

• controls on the creation and monitoring of components and activities, so that architectures are introduced, implemented, and evolve in a managed way;
• compliance with internal and external standards and with regulatory obligations;
• support for the management of these activities;
• accountability to internal and external stakeholders.

A hierarchy of governance

Architecture Governance does not work in isolation. It takes its place in a hierarchy where corporate, technology, IT, and architecture governance coexist, each with its own disciplines and processes. Each domain may also exist at several geographic scales: global, regional, and local.

For the exam, do not confuse these governance tiers with the four architecture domains (Business, Data, Application, Technology) or with architecture levels (strategic, segment, capability).

The framework: process, content, context

The TOGAF Architecture Governance Framework distinguishes processes, the governed content (standards, contracts, assessments, regulatory requirements), and context. This separation allows a new regulation or standard to be introduced without reworking the processes. Records of governance activity are kept in the Governance Repository within the Architecture Repository. The key processes are the following:

• Policy Management and Take-On: register, validate, ratify, and publish any new or updated content;
• Compliance: assess how projects and solutions comply;
• Dispensation: handle requests for temporary deviation;
• Monitoring and Reporting: track performance and report on it;
• Business Control: ensure business policies are respected;
• Environment Management: manage the repository, tools, and access supporting governance.