TOGAF Overview and Architecture Development Method

TOGAF: The Open Group Architecture Framework

• TOGAF is a detailed framework and supporting tools for developing enterprise architecture.
• It's freely usable by any organization.
• TOGAF covers various architecture domains: Technology, Application, Data, and Business.
• TOGAF 8.1 covers more domains compared to TOGAF 7.

TOGAF Components

• Architecture Development Method (ADM)
• Enterprise Continuum
• Resource Base

ADM (Architecture Development Method)

• A phased approach to developing architecture.
• Iterative and adaptable across phases and within phases.
• Key points for ADM adoption: Business circumstances, integration with other frameworks.
• Iterations of ADM decisions include scope and what should be included in the Enterprise Continuum.

Scoping

• Scoping is crucial for each architectural activity due to limitations in time, resources, and budget.
• Scoping dimensions: enterprise scope (horizontal), architecture domains and vertical scope (level of detail).
• Scoping decisions should create value to the enterprise.

ADM Phases

• Each phase of ADM has defined objectives, approach, inputs, steps, and outputs.
• The preliminary phase involves commitment of all stakeholders, defining principles, listing individuals and roles, and outlining methodology and evaluation.
• Phase A, Architecture Vision: Validating business principles, defining scope, identifying stakeholders, key requirements, and securing formal approval.
• Phase B, Business Architecture: Describing current and target business architecture using modeling tools like UML and analyzing gaps.
• Phase C, Information System Architecture: Developing data and application architectures, defining data types and entities, and application system capabilities.
• Phase D, Technology Architecture: Developing a technology architecture that supports implementation.
• Phase E, Opportunities and Solutions: Evaluating and selecting implementation solutions, and defining a migration plan.
• Phase F, Migration Planning: Prioritizing and detailing implementation projects, and creating detailed implementation plan.
• Phase G, Implementation Governance: Creating project recommendations, and performing effective governance.
• Phase H, Architecture Change Management: Monitoring ongoing developments and changes to determine whether to initiate a new architecture evolution cycle.

ADM Architecture Requirements Management

• A dynamic process to manage enterprise architecture requirements continuously.
• Changes (like market shifts) are actively collected, stored, and used in ADM phases.

Enterprise Continuum

• A repository of reusable building blocks for enterprise architecture.
• Contains work-in-progress and previous work done in the organization.
• Includes reference models and patterns.
• May include pre-built solutions for common systems or industry-specific scenarios.
• Used to build or reuse architectures moving between generic and more specific.
• It has levels, from highly generic to highly specific architectures.
• It includes Foundation, Common System, Industry, and Organizational architectures that link to Solutions Continuum (Products, Systems, Industry, and Organization solutions).

About the Enterprise Continuum components

• Foundation Architecture: Basic building blocks and standards for a complete computing environment.
• Common System Architecture: Addresses a particular problem domain.
• Industry Architectures: Pre-built, industry-specific solutions.