PDF OGEA-101 Study Guide

• A-Architecture Repository: This is a part of the Architecture Metamodel that contains artifacts structured according to the metamodel. It includes the Architecture Landscape which is adopted by the enterprise and governed by certain standards and practices.
• B-Governing Board: The Governing Board ensures visibility and escalation, meaning it oversees and manages the capability of the architecture landscape. It plays a crucial role in governance.
• C-Enterprise Capability: This refers to how well an enterprise can execute its mission, meet business objectives or satisfy its stakeholders’ needs and expectations. It’s influenced by both internal factors (like resources, processes) and external ones (like market trends).

References: TOGAF Version 9.1, Chapter 34: 1

Ensuring compliance with internal and external standards and regulatory obligations is one of the activities included as part of Architecture Governance. Architecture Governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It involves establishing processes, roles, responsibilities, policies, and standards to ensure that architectures are aligned with the enterprise’s strategy and objectives, and meet the quality and performance requirements. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.6 Architecture Governance.

The TOGAF standard divides Enterprise Architecture into four primary architecture domains: business, data, application, and technology. These domains represent different aspects of an enterprise and how they relate to each other. The business domain defines the business strategy, governance, organization, and key business processes. The data domain describes the structure of the logical and physical data assets and data management resources. The application domain provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes. The technology domain describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. Other domains, such as motivation, security, or governance, may span across these four primary domains. References:

• The TOGAF Standard, Version 9.2 - Core Concepts
• Domains - The Open Group
• TOGAF® Standard — Introduction - Definitions - The Open Group
• The TOGAF Standard, Version 9.2 - Definitions - The Open Group
• TOGAF and the history of enterprise architecture | Enable Architect

When considering agile development, Architecture to Support Project will identify what products the enterprise needs, the boundary of the products, and what constraints a product owner has. This defines the enterprise’s backlog. A backlog is a list of features or tasks that need to be done to deliver a product or service. It is prioritized by the product owner based on the value and urgency of each item. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.5 Architecture to Support Project.