Enterprise Architecture

3.

Enterprise Architecture Frameworks

3.1.

Framework Fundamentals

3.1.1.

Purpose of EA Frameworks

3.1.1.1.

Common Vocabulary Establishment

3.1.1.2.

Process Structure Provision

3.1.1.3.

Deliverable Definition

3.1.1.4.

Consistency Enablement

3.1.1.5.

Best Practice Codification

3.1.2.

Framework Selection Criteria

3.1.2.1.

Organizational Fit

3.1.2.2.

Industry Alignment

3.1.2.3.

Complexity Management

3.1.2.4.

Tool Support Availability

3.1.3.

Framework Customization

3.1.3.1.

Tailoring Approaches

3.1.3.2.

Organizational Adaptation

3.1.3.3.

Process Integration

3.1.3.4.

Cultural Considerations

3.2.

The Open Group Architecture Framework

3.2.1.

3.2.1.1.

Framework Structure

3.2.1.2.

Core Components

3.2.1.3.

Certification Program

3.2.1.4.

Community and Governance

3.2.2.

Architecture Development Method

3.2.2.1.

3.2.2.1.1.

Iterative Approach

3.2.2.1.2.

Phase Relationships

3.2.2.1.3.

Customization Guidelines

3.2.2.2.

Preliminary Phase

3.2.2.2.1.

Architecture Capability Establishment

3.2.2.2.2.

Organizational Readiness

3.2.2.2.3.

Architecture Principles Definition

3.2.2.2.4.

Framework Tailoring

3.2.2.3.

Phase A - Architecture Vision

3.2.2.3.1.

Stakeholder Management

3.2.2.3.2.

Business Scenario Development

3.2.2.3.3.

Architecture Vision Creation

3.2.2.3.4.

Statement of Architecture Work

3.2.2.4.

Phase B - Business Architecture

3.2.2.4.1.

Business Architecture Development

3.2.2.4.2.

Business Scenario Analysis

3.2.2.4.3.

Gap Analysis Execution

3.2.2.4.4.

Stakeholder Review

3.2.2.5.

Phase C - Information Systems Architectures

3.2.2.5.1.

Data Architecture Development

3.2.2.5.2.

Application Architecture Development

3.2.2.5.3.

Integration Requirements

3.2.2.5.4.

Technology Constraints

3.2.2.6.

Phase D - Technology Architecture

3.2.2.6.1.

Technology Architecture Development

3.2.2.6.2.

Technology Standards Definition

3.2.2.6.3.

Implementation Planning

3.2.2.6.4.

Migration Considerations

3.2.2.7.

Phase E - Opportunities and Solutions

3.2.2.7.1.

Solution Option Identification

3.2.2.7.2.

Implementation Factor Assessment

3.2.2.7.3.

Solution Selection

3.2.2.7.4.

Implementation Strategy

3.2.2.8.

Phase F - Migration Planning

3.2.2.8.1.

Implementation Roadmap

3.2.2.8.2.

Transition Architecture Definition

3.2.2.8.3.

Business Value Assessment

3.2.2.8.4.

Risk Assessment

3.2.2.9.

Phase G - Implementation Governance

3.2.2.9.1.

Architecture Contract Development

3.2.2.9.2.

Compliance Monitoring

3.2.2.9.3.

Change Management

3.2.2.9.4.

Performance Measurement

3.2.2.10.

Phase H - Architecture Change Management

3.2.2.10.1.

Change Request Management

3.2.2.10.2.

Impact Assessment

3.2.2.10.3.

Architecture Update

3.2.2.10.4.

Continuous Improvement

3.2.2.11.

Requirements Management

3.2.2.11.1.

Requirements Identification

3.2.2.11.2.

Requirements Analysis

3.2.2.11.3.

Requirements Traceability

3.2.2.11.4.

Requirements Validation

3.2.3.

Architecture Content Framework

3.2.3.1.

Content Metamodel

3.2.3.2.

Core Architecture Artifacts

3.2.3.3.

Architecture Building Blocks

3.2.3.4.

Solution Building Blocks

3.2.4.

Enterprise Continuum

3.2.4.1.

Architecture Continuum

3.2.4.2.

Solutions Continuum

3.2.4.3.

Architecture Repository

3.2.4.4.

Reuse and Leveraging

3.2.5.

Architecture Capability Framework

3.2.5.1.

Architecture Board

3.2.5.2.

Architecture Compliance

3.2.5.3.

Architecture Contracts

3.2.5.4.

Architecture Governance

3.3.

Zachman Framework

3.3.1.

Framework Structure

3.3.1.1.

Six Perspectives

3.3.1.2.

Six Interrogatives

3.3.1.3.

Cell Relationships

3.3.1.4.

Framework Rules

3.3.2.

3.3.2.1.

Planner Perspective

3.3.2.2.

Owner Perspective

3.3.2.3.

Designer Perspective

3.3.2.4.

Builder Perspective

3.3.2.5.

Implementer Perspective

3.3.2.6.

Worker Perspective

3.3.3.

3.3.3.1.

What - Data Perspective

3.3.3.2.

How - Function Perspective

3.3.3.3.

Where - Network Perspective

3.3.3.4.

Who - People Perspective

3.3.3.5.

When - Time Perspective

3.3.3.6.

Why - Motivation Perspective

3.3.4.

Framework Application

3.3.4.1.

Cell Population

3.3.4.2.

Artifact Development

3.3.4.3.

Perspective Alignment

3.3.4.4.

Completeness Assessment

3.4.

Other Notable Frameworks

3.4.1.

Federal Enterprise Architecture Framework

3.4.1.1.

Framework Structure

3.4.1.2.

Reference Models

3.4.1.3.

Performance Reference Model

3.4.1.4.

Business Reference Model

3.4.1.5.

Service Component Reference Model

3.4.1.6.

Technical Reference Model

3.4.1.7.

Data Reference Model

3.4.2.

Gartner Enterprise Architecture Method

3.4.2.1.

Framework Principles

3.4.2.2.

Process Methodology

3.4.2.3.

Governance Approach

3.4.2.4.

Maturity Assessment

3.4.3.

Department of Defense Architecture Framework

3.4.3.1.

Viewpoint Structure

3.4.3.2.

3.4.3.3.

Architecture Description

3.4.3.4.

Stakeholder Concerns

3.4.4.

SABAF - Sherwood Applied Business Security Architecture

3.4.4.1.

Security Architecture Framework

3.4.4.2.

Risk-Driven Approach

3.4.4.3.

Business Alignment

3.4.4.4.

Security Governance

Previous

2. Enterprise Architecture Domains

Go to top

Next

4. Enterprise Architecture Practice and Governance