TOGAF Architecture Framework Quiz

TOGAF: The Open Group Architecture Framework

• TOGAF is a framework, detailed method, and supporting tools for developing enterprise architecture
• Free for use by any organization for developing their own enterprise architecture
• Provides a structured approach with various phases, enabling consistent approach across organization
• Supports different architecture types (Technology, Application, Data, Business) in version 8.1.
• Version 7 of TOGAF only covered technology architecture.

TOGAF Components

• Architecture Development Method (ADM): A structured method for developing architecture.
• Enterprise Continuum: A repository of reusable building blocks
• Various levels - from highly generic to specific.
• Components - Foundation, Common System, Industry, Organization.

ADM (Architecture Development Method) Phases

• Iterative process across different phases and within phases.
• Defined objectives, approach, inputs, steps and outputs for each phase.
• Focus on Architecture Vision, Business Architecture, Information System Architecture, Technology Architecture, Opportunities and Solutions, Migration Planning, Implementation Governance and Architecture Change Management.
• Each iteration considers the scope and needs within the Enterprise Continuum.
• Preliminary phase: Ensuring all stakeholders are committed, defining architectural principles and assumptions, listing responsibilities, defining frameworks and methods.
• Phase A (Architecture Vision): Validating business principles, defining the scope, identifying stakeholders, defining key business requirements and constraints, securing formal approval .
• Phase B (Business Architecture): Describing the current baseline, developing a target architecture, analyzing gaps between baseline & target.
• Phase C (Information System Architecture): Defining data types and sources, Defining data entities,Defining application systems.
• Phase D (Technology Architecture): Developing technology architecture as base for implementation
• Phase E (Opportunities and Solutions): Evaluating implementation options, identifying change parameters, determining work packages, generating implementation strategy.
• Phase F (Migration Planning): Sorting implementation projects by priority, generating a detailed implementation plan.
• Phase G (Implementation Governance): Developing recommendations, performing appropriate governance functions.
• Phase H (Architecture Change Management): Continual monitoring, determining need for evolution of architecture cycle.

ADM Architecture Requirements Management

• Requirements management is a dynamic process, not just a static set of requirements
• Requirements for enterprise architecture, including subsequent changes, are identified, stored, and fed into the relevant ADM phases.
• Market conditions and legislation can alter requirements.

Enterprise Continuum

• A dynamic repository of reusable building blocks (ready & organization-specific) used within the architectural approach.
• Contains work in progress and previous work done
• Guided by reference models and other patterns
• Ranging from highly generic (Foundation Architecture) to highly specific (Organizational Architecture) across common system, industry and organizational. The movement to organization-specific.
• Relationship to the Solutions Continuum where you specify architecture building blocks, then implement via solution building blocks
• Steps are in a continuous fashion, going from left to right, top to bottom.

About the Enterprise Continuum Components

• Foundation Architecture: Building blocks and standards for a complete computing environment (e.g., technical reference model, standards information base)
• Common System Architecture: Detailed problem domain; incomplete in covering full information systems functionality, providing examples for network architecture.
• Industry Architectures: Pre-built architectures designed for specific industries, often including pre-built data models and business processes.