An Enterprise Architecture is only as good as the decision-making framework established around it. This decision-making framework is called governance framework.
An Enterprise Architecture must be supported by a strong governance framework to ensure the successful development, implementation, and sustainment of the architecture.
The governance framework depends on:
- clear authority structure; and
- the right participants
The image given below illustrates the organization structure of the TOGAF architecture governance framework. It describes all parties involved and their responsibilities in the governance environment. Generally, the CIO or CTO leads the architecture governance practice, providing stewardship to the teams responsible for developing, implementing, and deploying the Enterprise Architecture.
The box marked as `Develop’ represents the Enterprise Architecture team responsible for developing the Enterprise Architecture. The Enterprise Architecture team comprises the chief architect, enterprise architects and domain architects. Domain architects imply business architects, application architects, data architects, and technical architects. The Architecture Board provides guidance to the architects to develop the Enterprise Architecture.
The Architecture Board acts as the approving and controlling authority for the following:
Consistency between sub-architectures
- Identifying re-usable components
- Flexibility of enterprise architecture; to meet business needs and utilize new technologies
- Enforcement of Architecture Compliance
- Improving the maturity level of architecture discipline within the organization
- Ensuring that the discipline of architecture-based development is adopted
- Providing the basis for all decision-making with regard to changes to the architectures, and
- Supporting a visible escalation capability for out-of-bounds decisions
The box marked as `Implement` is the Enterprise Architecture team responsible for implementing the Enterprise Architecture. It comprises the Project Management Office or PMO and implementation project teams. The Architecture Board provides implementation related guidance to the PMO. Several implementation projects can arise from one Enterprise Architecture project. The PMO manages all these implementation projects. The implementation projects have to conform to the Enterprise Architecture proposed by the enterprise architects.
The box marked as `Deploy` is the Enterprise Architecture team responsible for deploying and monitoring the Enterprise Architecture. Each of the implementation projects produces one or more solutions that are operational systems to be deployed in production environment. The service management team deploys and monitors the operational systems.
The Enterprise Continuum is the logical view of the Architecture Repository that provides methods for classifying architecture and solution artefacts as they evolve from generic foundation architectures to organization-specific architectures. The architectural models, solutions, processes, regulatory requirements, authority structures, organizational standards, Service Level Agreements or SLAs, and Operational Level Agreements or OLAs are stored and retrieved from the Enterprise Continuum.