TOGAF EA Practitioner flashcards
TOGAF EA Practitioner · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Architecture Governance
- The disciplined, transparent, and accountable control of architecture creation, maintenance, and monitoring, exercised at corporate, IT, and technology levels, providing security, quality, and confidence in architecture decisions.
- Architecture Board
- A cross-organizational body of senior architects and executives that approves architecture, resolves conflicts between projects, monitors compliance, and sponsors the architecture program; typically chaired by the CIO or Chief Architect.
- Architecture Principles
- Formal, few, and stable statements of intent, each recorded with name, statement, rationale, and implications, agreed by the enterprise, which govern how architecture decisions are made.
- Architecture Compliance Review
- A structured governance technique that evaluates a project against architecture specifications using checklists and a scoring model, producing a review report with dispositions such as conformant, conformant with conditions, or non-conformant.
- Statement of Architecture Work
- The approved contract between the architecture function and the sponsor defining scope, method, deliverables, constraints, risks, and acceptance criteria for an architecture engagement; the key output of Phase A.
- Architecture Vision
- An executive summary describing the baseline and target architectures and the business value they deliver, enabling stakeholder consensus and authorizing the Statement of Architecture Work before detailed modeling begins.
- Stakeholder Map
- A catalog of stakeholders with their concerns, interests, influence, and power/interest classification, used to plan architecture engagement, select views, and produce the communications plan in Phase A.
- Business Capability Map
- A business architecture view showing the capabilities the enterprise needs, organized hierarchically and independent of organizational structure, used for heat-mapping and to plan capability-based increments.
- Value Stream Map
- A business architecture model of the value-adding sequences that deliver outcomes to customers, with each stage mapped to the business capabilities it requires, giving a stable, customer-centric view of the business.
- Organization Map
- A business architecture diagram showing the decomposition of organizational units, their locations, and their relationships, used with functions and capabilities to describe how the enterprise is structured.
- Application Communication Diagram
- An information systems view modeling applications and the interfaces and messages exchanged between them, used to assess dependencies, integration complexity, and the effect of application changes.
- Data Entity/Data Component Catalog
- A Phase C inventory of data entities, their attributes and relationships, and the logical data components that hold them, forming the core description of the Data Architecture.
- Application/Function Matrix
- A Phase C matrix mapping business functions to the applications that support them, revealing overlap, redundancy, gaps in application coverage, and candidates for rationalization.
- Platform Decomposition Diagram
- A technology architecture view that decomposes a platform into its technology components and identifies which applications depend on each component, supporting impact and redundancy analysis.
- Environments and Locations Diagram
- A technology architecture view showing which technology services are deployed in which environment, such as development, test, or production, and at which location, including users and technologies affected.
- Technical Reference Model
- TOGAF's reference taxonomy and nomenclature of technology services and standards, used to model the Technology Architecture and to organize the standards recorded in the Standards Information Base.
- Transition Architecture
- A formally described intermediate state of the enterprise, between the baseline and the target, that delivers business value at a defined point in the implementation and migration plan.
- Implementation and Migration Strategy
- The chosen overall approach to delivering the target architecture: Greenfield for a new build, Revolutionary for single-step replacement, or Evolutionary for incremental delivery, selected on risk, cost, and value.
- Consolidated Gaps Solutions Dependencies Matrix
- A Phase E and F summary table listing architecture gaps, the solutions or work packages that address them, and the dependencies between those work packages, used to group work into projects.
- Implementation Factor Assessment and Deduction Matrix
- A Phase F table listing factors that affect implementation, such as dependencies, risks, and costs, together with their impact and the deductions that determine how work packages are organized.
- Project Prioritization
- The Phase F ranking of work packages and projects using criteria including business value, technical risk, cost, and dependency, often plotted on a business-value versus technical-risk grid.
- Implementation and Migration Plan
- The Phase F deliverable specifying the work packages, transition architectures, milestones, resources, and dependencies that will move the enterprise from baseline to target over time.
- Architecture Contract
- An agreement between the architecture function and an implementation project stating deliverables, conformance requirements, acceptance criteria, and roles, used to govern development and deployment in Phase G.
- Compliance Assessment
- A Phase G activity comparing project work products with the architecture specification and recording, for each area reviewed, whether the project is conformant, partially conformant, or non-conformant.
- Implementation Governance
- The Phase G discipline in which the architecture function oversees solution development and deployment, ensuring projects conform to the target architecture through contracts, compliance reviews, and change control.
- Simplification Change
- A category of architecture change that reduces complexity without altering architectural scope, handled directly by change management without re-entering the full ADM cycle.
- Incremental Change
- A category of architecture change that adds or extends capabilities within existing architectural boundaries, typically handled by re-entering the ADM at a later phase such as Phase B, C, or D.
- Re-Architecting Change
- A category of architecture change that fundamentally alters the scope or approach of the architecture, requiring re-entry into the ADM, usually starting again at Phase A.
- Business Scenario
- A technique describing a business problem in terms of environment, actors and roles, desired outcome, and success measures, used to derive and validate architecture requirements.
- Requirements Impact Assessment
- A process that assesses each change in requirements, identifies its effect on the architecture, and determines which ADM phase must be re-entered to act on it.
- Architecture Requirements Specification
- A document containing the requirements the architecture must satisfy, with measurable acceptance criteria, maintained centrally throughout the ADM and used by later phases and compliance reviews.
- Business Transformation Readiness Assessment
- A technique that scores readiness factors on maturity, readiness, and difficulty, and records the risk of not addressing each factor, to judge whether the enterprise can absorb the planned transformation.