Showing all 80 terms
No terms match your search. Try a different keyword or clear the filter.
A
- Application ArchitectureDomain
- A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets. It forms part of Phase C (Information Systems Architecture) of the ADM.
- Architecture BoardGovernance
- A cross-organizational body responsible for overseeing the implementation of architecture governance across the enterprise. It reviews compliance, grants dispensations, and ensures architecture decisions align with strategic direction. The Architecture Board is the primary governance body in TOGAF. Know its responsibilities: approving architectures, issuing compliance decisions, and maintaining the Architecture Repository.
- Architecture ComplianceGovernance
- The adherence of a project or solution to a set of architecture standards and specifications. Compliance levels include irrelevant, consistent, conformant, compliant, tailored, and non-conformant.
- Architecture ContractGovernance
- A joint agreement between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture. Architecture Contracts are produced in Phase G and define the obligations of all parties.
- Architecture ContinuumContinuum
- Part of the Enterprise Continuum, this is a repository of architecture assets representing a spectrum from Foundation Architectures to Organization-Specific Architectures. It classifies reusable building blocks and provides context for the Solutions Continuum. The Architecture Continuum runs left to right from generic to specific: Foundation → Common Systems → Industry → Organization-Specific.
- Architecture Definition Document (ADD)Content
- The primary deliverable describing the Target Architecture in terms of the four architecture domains (Business, Data, Application, Technology). It captures the baseline and target states and the gap analysis between them. The ADD is created in Phases B–D and updated through Phase E. Do not confuse it with the Statement of Architecture Work (the engagement contract) or the Architecture Requirements Specification.
- Architecture DescriptionFoundation
- A work product used to express an architecture, comprising a collection of architectural models and other artifacts that collectively describe the architecture. It corresponds to the IEEE 42010 standard for architecture description.
- Architecture Development Method (ADM)ADM
- The core process of TOGAF — an iterative, phase-based method for developing and maintaining enterprise architecture, comprising a Preliminary Phase, Phase A through Phase H, and a central Requirements Management process. Each phase defines key inputs, steps, and outputs. Requirements Management is NOT a sequential phase — it is a continuous process at the center of the ADM wheel, operating throughout all phases.
- Architecture DomainFoundation
- One of the four primary architecture areas recognized by TOGAF: Business Architecture, Data Architecture, Application Architecture, and Technology Architecture. Collectively they represent the four columns of the TOGAF Content Framework. Know all four domains and their corresponding ADM phases: Business=B, Data+Application=C, Technology=D.
- Architecture FrameworkFoundation
- A foundational structure or set of structures which can be used for developing a broad range of different architectures. TOGAF is an example of an architecture framework, providing method, content, and tools.
- Architecture GovernanceGovernance
- The practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level. It includes the processes, roles, responsibilities, and policies that ensure architectures are developed and used in accordance with agreed principles. TOGAF distinguishes Architecture Governance (enterprise level) from IT Governance (IT services level) and Corporate Governance (corporate accountability). Know the differences.
- Architecture LandscapeRepository
- The architectural representation of assets in use, or planned, by the enterprise at particular points in time. It is organized into three levels: Strategic Architecture, Segment Architecture, and Capability Architecture.
- Architecture PrinciplesFoundation
- A set of general rules and guidelines that inform and guide the way in which an organization fulfils its mission. Each TOGAF principle has five components: name, statement, rationale, implications, and a metrics/measures element. Know the five components of an architecture principle. Principles are defined in the Preliminary Phase and stored in the Architecture Repository.
- Architecture RepositoryRepository
- A holding area for all architectural activity within the enterprise, containing the Architecture Metamodel, Architecture Landscape, Standards Information Base, Reference Library, Governance Log, and the Architecture Capability definition. Know the six classes of architectural information stored in the Architecture Repository — a common exam topic.
- Architecture Requirements SpecificationContent
- A set of quantitative statements that outline what an implementation project must do to comply with the architecture. It provides a measurable basis for conformance testing and is produced alongside the Architecture Definition Document.
- Architecture RoadmapContent
- A plan that identifies a path from the Baseline Architecture to the Target Architecture using a series of Transition Architectures. It lists work packages in a sequenced, prioritized delivery plan and is produced in Phase E.
- Architecture VisionADM
- The key deliverable of Phase A, describing the high-level aspirational view of the Target Architecture and its business value. It includes a high-level description of the Baseline and Target Architectures and is used to gain stakeholder approval to proceed. Phase A produces the Statement of Architecture Work (authorizing the ADM engagement) and the Architecture Vision document (describing what will be achieved).
B
- Baseline ArchitectureContent
- A snapshot of the existing enterprise architecture at a particular point in time, documenting the current state before transition to the Target Architecture. Understanding the baseline is essential for conducting meaningful Gap Analysis.
- Building BlockContent
- A package of functionality defined to meet business needs. Building blocks can be categorized as Architecture Building Blocks (ABBs) — defining capability — or Solution Building Blocks (SBBs) — representing implementations. They should be reusable and replaceable. Know the distinction: ABBs define what is needed (architecture view), SBBs define how it is delivered (solution view).
- Business ArchitectureDomain
- The architecture domain that defines the business strategy, governance, organization, and key business processes. Developed in Phase B of the ADM, it provides the context and motivation for the three technical architecture domains.
- Business CapabilityDomain
- A particular ability that a business may possess or exchange to achieve a specific outcome. Business capabilities are the building blocks of Capability-Based Planning and are used in Phase B to model the business without prescribing implementation.
- Business ScenarioTechnique
- A technique used in TOGAF to understand business requirements by describing a business process, application, or set of applications that can be enabled by the architecture. Business Scenarios help translate stakeholder concerns into architecture requirements.
- Business Transformation Readiness AssessmentTechnique
- An assessment of the enterprise's readiness and ability to absorb and utilize the proposed changes from an architecture initiative. It evaluates factors such as vision, desire, need, business case, funding, and leadership.
C
- Capability-Based PlanningTechnique
- A business planning technique that focuses on the outcomes and capabilities the enterprise requires rather than organizational units or systems. It enables the enterprise to plan architecture increments around the delivery of discrete business capabilities.
- Common Systems ArchitectureContinuum
- The second level of the Architecture Continuum (after Foundation Architecture), comprising architectures that apply to multiple organizations across industries. Examples include technical reference models for security, network, or data management.
- Compliance ReviewGovernance
- A formal review conducted by the architecture team to assess whether a project or solution conforms to the defined architecture. Compliance review results can be: irrelevant, consistent, conformant, compliant, tailored, or non-conformant. Know the six compliance levels and what each means for a project's relationship to the architecture.
- ConcernFoundation
- An interest in the system pertinent to one or more stakeholders. Concerns can relate to the system's function, performance, reliability, security, cost, or any other property. Architecture views are constructed to address stakeholder concerns.
- Configuration Management Database (CMDB)Governance
- A repository used to store information about hardware and software assets (configuration items) and their relationships. In TOGAF, the CMDB may be referenced as a source of baseline architecture data and used to support Implementation Governance.
- ConstraintFoundation
- An external factor that prevents the enterprise from pursuing certain approaches to meet its goals. Unlike Requirements (which describe what the system must do), constraints restrict the solution space from the outset.
- Content MetamodelFoundation
- A formal definition of the types of building blocks, their attributes, and the relationships between them that are used in architectural descriptions. The TOGAF Content Metamodel provides a structured framework for defining architecture content.
D
- Data ArchitectureDomain
- The structure of an organization's logical and physical data assets and data management resources. It is defined in Phase C (Information Systems Architecture) alongside Application Architecture.
- DeliverableContent
- A work product that is contractually specified and reviewed, agreed, and signed off by the stakeholders. In TOGAF, deliverables differ from artifacts (which are not contractually required) and building blocks (which may be re-used components). Know the TOGAF Content Framework distinction: Deliverable (contractual output) > Artifact (architectural work product) > Building Block (packaged functionality).
- DispensationGovernance
- A formally granted permission by the Architecture Board for a project to deviate from established architecture standards for a defined period, with specific conditions. Dispensations are time-limited and must be reviewed at expiry.
- DriverFoundation
- An external or internal condition that motivates an organization to change. Business drivers (such as regulatory changes, market pressures, or technology shifts) provide the justification for architecture change and feed into the Architecture Vision.
E
- Enterprise ArchitectureFoundation
- A coherent whole of principles, methods, and models that are used in the design and realization of an enterprise's organizational structure, business processes, information systems, and IT infrastructure. EA connects business strategy to IT implementation.
- Enterprise ContinuumContinuum
- A view of the Architecture Repository that provides a context for understanding and organizing architectural assets from generic Foundation Architectures to Organization-Specific Architectures. It comprises the Architecture Continuum and the Solutions Continuum. The Enterprise Continuum is NOT a timeline — it is a classification scheme. Moving from left (generic) to right (specific) increases organizational relevance.
- Enterprise TransformationADM
- A fundamental shift in the business and operating model of the enterprise, driven by strategic change. TOGAF supports enterprise transformation through the ADM cycle, Capability-Based Planning, and Transition Architecture planning.
- Enterprise Architecture MaturityTechnique
- A measure of the sophistication and effectiveness of an organization's architecture practice, typically assessed against a maturity model (such as the US DoC ACMM). Higher maturity correlates with more consistent, governed, and value-delivering architecture capability.
F
- Foundation ArchitectureContinuum
- The most generic level of the Architecture Continuum, describing fundamental building blocks and principles applicable to any enterprise. TOGAF's TRM and III-RM are examples of Foundation Architectures and reside at the left end of the Enterprise Continuum.
- Fully CompliantGovernance
- A compliance classification indicating that a project or solution fully meets all the requirements of the relevant architecture and its associated standards. This is the ideal outcome of a Compliance Review conducted in Phase G.
G
- Gap AnalysisTechnique
- A technique used in each of Phases B–D to identify the difference between the Baseline and Target Architectures. Gaps can represent eliminated, added, or changed capabilities, and are used to derive the requirements for Transition Architectures. Gap Analysis is performed in every domain phase (B, C, D) and consolidated in Phase E. Each gap becomes a potential work package or requirement.
- Governance LogRepository
- A component of the Architecture Repository that records governance decisions, compliance review outcomes, dispensations, and waivers. It provides a full audit trail of architecture governance activity.
- Governance FrameworkGovernance
- A structured set of policies, processes, roles, and responsibilities that ensure architecture decisions are made in a consistent, transparent, and accountable manner. TOGAF describes corporate, IT, and architecture governance as distinct but related layers.
I
- III-RM (Integrated Information Infrastructure Reference Model)Continuum
- One of TOGAF's two reference models (alongside the TRM), the III-RM addresses the requirements of the Business Applications layer — focusing on enabling an integrated information infrastructure across distributed systems.
- Implementation Factor AssessmentADM
- An assessment conducted in Phase E to evaluate factors and risks associated with implementing the Architecture Roadmap. It considers implementation constraints, assumptions, and risks across the transition states.
- Implementation GovernanceADM
- Phase G of the ADM, which ensures that implementation projects conform to the defined architecture. Activities include compliance reviews, Architecture Contracts, and oversight of solution delivery against architecture specifications. Phase G (Implementation Governance) does NOT deliver solutions — it governs and monitors solution delivery performed by projects.
- Information Systems ArchitectureDomain
- Phase C of the ADM, comprising the development of both Data Architecture and Application Architecture. It considers how data is structured, stored, and managed, and how applications interact to support business processes.
L
- Logical Architecture ComponentContent
- An Architecture Building Block (ABB) described in functional terms, independent of any specific implementation technology or product. Logical components are mapped to physical components (Solution Building Blocks) during Phase E.
- Lessons LearnedADM
- A record of insights and knowledge gained from completed architecture cycles, captured during Phase H (Architecture Change Management). Lessons Learned are used to improve future ADM iterations and refine the organization's architecture capability.
M
- Migration PlanningADM
- Phase F of the ADM, focused on finalizing the Architecture Roadmap and the Migration Plan by prioritizing the work packages from Phase E. The Migration Plan defines the sequence of implementation projects needed to move from Baseline to Target Architecture. Phase F produces the Migration Plan (prioritized project list) and finalized Architecture Roadmap. Phase E identifies the work packages; Phase F prioritizes and sequences them.
O
- OGEA-103Exam
- The combined TOGAF Enterprise Architecture certification examination offered by The Open Group, covering both Part 1 (Foundation/OGEA-101) and Part 2 (Practitioner/OGEA-102) in a single sitting. Candidates must pass both parts to achieve certification. Part 1 is closed book (40 questions, 60 min, 55% pass). Part 2 is open book (8 scenario questions, 90 min, 60% pass). Both must be passed.
- Open Group Architecture Framework (TOGAF)Foundation
- An enterprise architecture framework developed and maintained by The Open Group, currently at version 10 (TOGAF Standard, 10th Edition / TOGAF Fundamental). It provides a comprehensive approach — method, content, and tools — for designing, planning, implementing, and governing enterprise IT architectures.
- Organizational MapContent
- A representation of the relationships between an organization's units, roles, and locations, used within Business Architecture to understand the organizational context that the architecture must support.
P
- Part 1 Foundation (OGEA-101)Exam
- The Foundation-level TOGAF certification examining knowledge of TOGAF concepts, terminology, and the ADM process. It is a closed-book, 40-question, 60-minute exam with a 55% pass mark. Passing Part 1 is a prerequisite for Part 2.
- Part 2 Practitioner (OGEA-102)Exam
- The Practitioner-level TOGAF certification testing the ability to apply TOGAF in complex enterprise architecture scenarios. It is an open-book exam with 8 scenario-based questions, 90 minutes, and a 60% pass mark. Part 2 scenarios test application of TOGAF, not recall. Understand the rationale behind ADM decisions, not just what the phases are.
- Physical Architecture ComponentContent
- A Solution Building Block (SBB) that represents a specific, named technology or product chosen to fulfil a logical architecture requirement. Physical components appear in the Solutions Continuum and are selected during Phase E of the ADM.
- PrincipleFoundation
- A general rule or guideline, formalized and adopted by the enterprise, that constrains the way the enterprise fulfils its mission. TOGAF prescribes five components for each principle: Name, Statement, Rationale, Implications, and Measures. Principles are set in the Preliminary Phase. The five components (especially Implications) are a frequent Part 1 topic.
R
- Reference ArchitectureContinuum
- A generic, reusable architecture template that provides a common vocabulary and set of guidelines for a particular domain or industry. Reference Architectures reside in the Architecture Continuum between Common Systems and Organization-Specific Architectures.
- Reference LibraryRepository
- A component of the Architecture Repository that holds guidelines, templates, patterns, and other forms of reference material used to accelerate the development of architectures. It stores reusable architecture assets aligned to the Enterprise Continuum.
- Reference ModelContinuum
- An abstract framework or domain-specific ontology consisting of an interlinked set of clearly defined concepts produced by an expert community. TOGAF provides two reference models: the TRM (Technology Reference Model) and the III-RM.
- Request for Architecture WorkADM
- A document sent from sponsoring organization to the architecture organization to trigger the start of an ADM architecture development cycle. It is a key input to Phase A and contains the business context, constraints, and initial scope. The Request for Architecture Work is an input to Phase A. The output that authorizes the work is the Statement of Architecture Work.
- RequirementsContent
- A statement of need that must be met by the architecture or solution. In TOGAF, requirements are managed through the central Requirements Management process that runs continuously throughout the ADM, not within any single phase.
S
- Segment ArchitectureContent
- An architecture developed for a defined part (or segment) of the enterprise, such as a business unit, function, or capability. It provides more detail than a Strategic Architecture and directly addresses the needs of a specific part of the business.
- Solution Building Block (SBB)Content
- A physical, implementation-specific component that realizes an Architecture Building Block (ABB). SBBs represent actual products, systems, or services and reside in the Solutions Continuum.
- Solution ContinuumContinuum
- The implementation counterpart of the Architecture Continuum, containing a repository of reference implementations, industry solutions, and organization-specific deployed solutions. It maps physical solutions to the logical architectures defined in the Architecture Continuum. The Architecture Continuum defines WHAT is needed; the Solutions Continuum defines HOW it is implemented (products, solutions, services).
- StakeholderFoundation
- An individual, team, organization, or class of stakeholders having an interest in a system or the realization of an architecture. Each stakeholder has concerns that the architecture must address, expressed through views and viewpoints.
- Standards Information BaseRepository
- A component of the Architecture Repository that captures the standards, guidelines, and technical specifications that have been adopted by the organization. Standards are classified as approved, emerging, or retiring within the SIB.
- Statement of Architecture WorkContent
- The key deliverable from Phase A that defines the scope and approach for an ADM cycle. It is the engagement contract, formally approved by the sponsoring organization, and authorizes the architecture team to proceed with Phases B–D. Do not confuse the Statement of Architecture Work (the project authorization document from Phase A) with the Architecture Vision (the high-level aspirational description of the Target Architecture).
- Strategic ArchitectureContent
- A summary enterprise-level architecture that provides the strategic direction and vision for the enterprise. It sits at the highest level of the Architecture Landscape and provides the context within which Segment and Capability Architectures are developed.
T
- Tailored Architecture FrameworkADM
- A version of the TOGAF ADM that has been customized for a specific organization by adding or removing steps, integrating with other frameworks (e.g., ITIL, COBIT), or adapting terminology. Tailoring is performed in the Preliminary Phase.
- Target ArchitectureContent
- A description of a future state of the enterprise architecture that the organization wishes to achieve, defined in Phases B–D of the ADM. It contrasts with the Baseline Architecture and the gap between them drives the Architecture Roadmap.
- Technology ArchitectureDomain
- The architecture domain covering the logical software and hardware capabilities required to support the deployment of business, data, and application services. Developed in Phase D of the ADM, it includes technology standards, platforms, and infrastructure.
- Technology Reference Model (TRM)Continuum
- One of TOGAF's two Foundation Architecture reference models, the TRM provides a taxonomy and graphical model of generic platform services. It establishes a common vocabulary for technology architecture and supports the categorization of building blocks. TOGAF has two reference models: TRM (technology services taxonomy) and III-RM (integrated information infrastructure). Know the difference.
- TOGAFFoundation
- The Open Group Architecture Framework — an enterprise architecture framework maintained by The Open Group. TOGAF is structured around four parts: Introduction, the ADM, ADM Guidelines and Techniques, and the Architecture Content Framework (including the Enterprise Continuum).
- Transition ArchitectureContent
- A temporary, intermediate state of the enterprise architecture that must be achieved during the migration from Baseline to Target Architecture. Multiple Transition Architectures may be defined to manage a phased and risk-controlled transformation. Transition Architectures are defined in Phase E and sequenced in Phase F. Each represents a deliverable, usable state of the enterprise — not just a project milestone.
V
- Value StreamDomain
- An end-to-end set of activities that create value for a stakeholder, from the initial trigger to the delivery of that value. In Business Architecture, value streams provide a horizontal view that complements the vertical view of business capabilities.
- ViewFoundation
- A representation of a system from the perspective of a related set of concerns. In TOGAF, views are constructed by applying a Viewpoint to the system model and are used to communicate architecture to specific stakeholders. A View is the result of applying a Viewpoint. One system can have many views (one per stakeholder concern grouping). A Viewpoint is the specification; the View is the instance.
- ViewpointFoundation
- A specification of the conventions for constructing and using a view. A viewpoint establishes the purpose, audience, modeling techniques, and notation for a particular type of architectural view. It is a template, not the view itself.
W
- Work PackageContent
- A set of actions identified to achieve one or more objectives for the business, derived from Gap Analysis and packaged for delivery as a project or programme. Work packages are identified in Phase E and prioritized/sequenced in Phase F to form the Migration Plan. Work packages are the unit of delivery in the Architecture Roadmap. Each work package may map to one or more implementation projects in the Migration Plan.