Welcome to the TOGAF™ 8.1.1 -- Specification Site Map

• Frontmatter
  • Preface
    • This Document
    • Intended Audience
    • Keywords
  • About The Open Group
    • The Open Group
  • Trademarks
  • Acknowledgements
  • Referenced Documents
• Introduction
  • Structure of the TOGAF Document
  • Downloads
    • Conditions of Use
  • Frequently Asked Questions
    • What is an enterprise? ...
    • ... an architecture? ...
    • ... an architecture description? ...
    • ... an architecture framework? ...
    • Why do I need an enterprise architecture?
    • Why do I need a framework for enterprise architecture?
    • Why is this important?
    • What specifically would prompt me to develop an architecture?
    • What is TOGAF?
    • What kind of architecture does TOGAF deal with?
    • Who would benefit from using TOGAF?
    • What specifically does TOGAF contain?
    • Just how do you use TOGAF?
    • How much does TOGAF cost?
    • Since TOGAF is freely available, why join The Open Group?
• TOGAF as an Enterprise Architecture Framework
  • Introduction
  • The Role of TOGAF
  • TOGAF and Architecture Governance
  • Using TOGAF with Other Frameworks
    • Overview
    • The Enterprise Continuum
  • Summary
• Introduction to the ADM
  • ADM Overview
    • Relationship to Other Parts of TOGAF
    • The ADM and the Enterprise Continuum
    • The ADM and the Resource Base
  • The Architecture Development Cycle
    • Key Points
    • Basic Structure
  • Adapting the ADM
  • Architecture Governance
  • Process Management
  • Scoping the Architecture
    • Enterprise Scope/Focus
    • Architecture Domains
    • Vertical Scope/Level of Detail
    • Time Horizon
  • Architecture Integration
  • Summary
• Preliminary Phase: Framework and Principles
  • Objectives
  • Approach
    • Principles
    • Framework
  • Inputs
  • Steps
  • Outputs
• Phase A: Architecture Vision
  • Objectives
  • Approach
    • General
    • Creating the Architecture Vision
  • Inputs
  • Steps
    • Business Scenarios
  • Outputs
• Phase B: Business Architecture
  • Objectives
  • Approach
    • General
    • Developing the Baseline Description
    • Business Modeling
    • Enterprise Continuum
    • Gap Analysis
  • Inputs
  • Steps
  • Outputs
• Phase C: Information System Systems Architectures
  • Objective
  • Approach
    • Development
    • Implementation
  • Inputs
  • Steps
  • Outputs
• Phase C: Information System Systems Architectures - Data Architecture
  • Objective
  • Approach
    • Enterprise Continuum
    • Gap Analysis
  • Inputs
  • Steps
  • Outputs
• Phase C: Information System Systems Architectures - Applications Architecture
  • Objective
  • Approach
    • Enterprise Continuum
    • Gap Analysis
  • Inputs
  • Steps
  • Outputs
• Phase D: Technology Architecture
  • Objective
  • Approach
    • General
    • Architecture Continuum
  • Inputs
  • Steps
  • Outputs
  • Target Technology Architecture - Detail
    • Introduction
    • Overview
    • Step 1
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Step 2
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Step 3
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Step 4
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Step 5
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Step 6
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Step 7
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Step 8
      • Objective
      • Approach
      • Inputs
      • Activities
      • Outputs
    • Postscript
• Phase E: Opportunities and Solutions
  • Objectives
  • Approach
  • Inputs
  • Steps
  • Outputs
• Phase F: Migration Planning
  • Objective
  • Approach
  • Inputs
  • Steps
  • Outputs
• Phase G: Implementation Governance
  • Objectives
  • Approach
  • Inputs
  • Steps
  • Outputs
• Phase H: Architecture Change Management
  • Objective
  • Approach
    • The Drivers for Change
    • The Change Management Process
    • Guidelines for Maintenance versus Architecture Redesign
  • Inputs
  • Steps
  • Outputs
• ADM Architecture Requirements Management
  • Objective
  • Approach
    • General
    • Resources
      • Business Scenarios
      • Volere Requirements Specification Template
      • Requirements Tools
  • Inputs
  • Steps
  • Outputs
    • Footnotes
• ADM Input and Output Descriptions
  • Introduction
  • Major Input Descriptions
    • Request for Architecture Work
    • Architecture Principles
    • Re-Usable Architecture Building Blocks
    • Product Information
    • New Technology Reports
  • Major Output Descriptions
    • Statement of Architecture Work
    • Business Scenario/Architecture Vision
    • Business Architecture
    • Technology Architecture
    • Impact Analysis
    • Architecture Contract
    • Requirements Impact Statement
• Introduction to the Enterprise Continuum
  • Overview
  • The Enterprise Continuum and Architecture Re-Use
  • The Enterprise Continuum and the TOGAF ADM
  • Constituents of the Enterprise Continuum
  • Structure of Part III
• The Enterprise Continuum in Detail
  • The Architecture Continuum
    • Introduction
    • Foundation Architecture
    • Common Systems Architectures
    • Industry Architectures
    • Enterprise Architectures
  • The Solutions Continuum
    • Introduction
    • Products and Services
    • Systems Solutions
    • Industry Solutions
    • Enterprise Solutions
  • The Enterprise Continuum and Your Organization
    • Relationships
    • Your Enterprise
    • Footnotes
• Foundation Architecture: Technical Reference Model
  • Concepts
    • Role of the TRM in the Foundation Architecture
    • TRM Components
    • Other TRMs
  • High-Level Breakdown
    • Overview
    • Portability and Interoperability
  • The TRM in Detail
    • Introduction
    • TRM Entities and Interfaces
    • Application Software
      • Business Applications
      • Infrastructure Applications
    • Application Platform
      • The Platform Concept
      • Extending the TRM
      • Interfaces Between Services
      • Future Developments
    • Communications Infrastructure
    • Application Platform Interface
    • Communications Infrastructure Interface
    • Qualities
  • Application Platform - Taxonomy
    • Basic Principles
    • Application Platform Service Categories
      • Object-Oriented Provision of Services
    • Application Platform Service Qualities
      • Principles
      • Taxonomy of Service Qualities
• Detailed Platform Taxonomy
  • Data Interchange Services
  • Data Management Services
  • Graphics and Imaging Services
  • International Operation Services
  • Location and Directory Services
  • Network Services
  • Operating System Services
  • Software Engineering Services
  • Transaction Processing Services
  • User Interface Services
  • Security Services
  • System and Network Management Services
  • Object-Oriented Provision of Services
• Foundation Architecture: Standards Information Base
  • Introduction
    • Role of the SIB
      • What is the SIB?
      • What is it for?
      • How is it Used in Architecture Development?
    • Accessing the SIB
  • The Open Group Standards
    • Overview
    • Criteria for Inclusion in the SIB
    • The Open Group Technical Processes
    • Product Standards
    • The Open Brand
  • Using the SIB
    • Introduction
    • Examples
      • Getting Started
      • Example 1: The Entire SIB
      • Example 2: Referenced Standards
      • Example 3: Open Group Technical Standards
      • Example 4: Open Group Product Standards
    • Summary of Open Group Databases and Resources
    • Footnotes
• Integrated Information Infrastructure Reference Model
  • Basic Concepts
    • Background
    • Components of the Model
    • Relationship to Other parts of TOGAF
    • Key Business and Technical Drivers
      • Problem Space: The Need for Boundaryless Information Flow
      • Solution Space: The Need for Integrated Information Infrastructure
    • Health Warning
  • High-Level View
    • Derivation of the III-RM from the TRM
    • The High-Level III-RM Graphic
    • Components of the High-Level III-RM
  • Detailed Taxonomy
    • Detailed III-RM Graphic
    • Business Applications
      • Information Provider Applications
      • Brokerage Applications
      • Information Consumer Applications
    • Infrastructure Applications
      • Development Tools
      • Business Modeling Tools
      • Design Modeling Tools
      • Implementation and Construction Tools
      • Data Modeling Tools
      • Deployment Tools
      • Libraries
      • Management Utilities
      • Operations, Administration, and Management (OA&M) Utilities
      • Quality of Service Manager Utilities
      • Copy Management Utilities
      • Storage Management Utilities
    • Application Platform
      • Software Engineering Services
      • Security Services
      • Location and Directory Services
      • Human Interaction Services
      • Data Interchange Services
      • Data Management Services
      • Additional Operating System Services
    • Qualities
    • Footnotes
• Architecture Board
  • Role
  • Responsibilities
  • Setting Up the Architecture Board
    • Triggers
    • Size of the Board
    • Board Structure
  • Operation of the Architecture Board
    • General
    • Preparation
    • Agenda
      • Minutes of Previous Meeting
      • Requests for Change
      • Dispensations
      • Compliance Assessments
      • Dispute Resolution
      • Architecture Strategy and Direction Documentation
      • Actions Assigned
      • Contract Documentation Management
      • Any Other Business (AOB)
      • Schedule of Meetings
• Architecture Compliance
  • Introduction
  • Terminology - The Meaning of Architecture Compliance
  • Project Impact Assessments (Project Slices)
    • Introduction
    • Sources
  • Architecture Compliance Reviews
    • Purpose
    • Timing
    • Governance and Personnel Scenarios
  • Architecture Compliance Review Process
    • Overview
    • Roles
    • Steps
  • Architecture Compliance Review Checklists
    • Hardware and Operating System Checklist
    • Software Services and Middleware Checklist
    • Applications Checklists
      • Infrastructure (Enterprise Productivity) Applications
      • Business Applications
      • Application Integration Approach
    • Information Management Checklists
      • Data Values
      • Data Definition
      • Security/Protection
      • Hosting, Data Types, and Sharing
      • Common Services
      • Access Method
    • Security Checklist
    • System Management Checklist
    • System Engineering/Overall Architecture Checklists
      • General
      • Processors/Servers/Clients
      • Client
      • Application Server
      • Data Server
      • COTS (where applicable)
    • System Engineering/Methods & Tools Checklist
  • Architecture Compliance Review Guidelines
    • Guidelines for Tailoring the Checklists
    • Guidelines for Conducting Architecture Compliance Reviews
• Architecture Contracts
  • Role
  • Contents
    • Statement of Architecture Work
    • Contract between Architecture Design and Development Partners
    • Contract between Architecting Function and Business Users
  • Relationship to Architecture Governance
• Architecture Governance
  • Introduction
    • Levels of Governance within the Enterprise
    • The Nature of Governance
      • Governance: A Generic Perspective
      • The Characteristics of Governance
    • Technology Governance
    • IT Governance
      • An IT Governance Framework - COBIT
    • Architecture Governance: Overview
      • Architecture Governance Characteristics
      • Architecture Governance as a Board-Level Responsibility
      • TOGAF and Architecture Governance
  • Architecture Governance Framework
    • Architecture Governance Framework - Conceptual Structure
      • Key Concepts
      • Key Architecture Governance Processes
      • Policy Management and Take-On
      • Compliance
      • Dispensation
      • Monitoring and Reporting
      • Business Control
      • Environment Management
    • Architecture Governance Framework - Organizational Structure
      • Overview
      • Key Areas
      • Operational Benefits
  • Architecture Governance in Practice
    • Architecture Governance - Key Success Factors
    • Elements of an Effective Architecture Governance Strategy
      • Architecture Governance and Corporate Politics
      • Key Strategic Elements
• Architecture Maturity Models
  • Overview
  • Background
  • The US DoC ACMM Framework
    • Overview
    • Elements of the ACMM
    • Example: IT Architecture Process Maturity Levels
      • Level 0: None
      • Level 1: Initial
      • Level 2: Under Development
      • Level 3: Defined
      • Level 4: Managed
      • Level 5: Optimizing
  • Capability Maturity Models Integration (CMMI)
    • Introduction
    • The SCAMPI Method
  • Conclusions
    • Footnotes
• Architecture Patterns
  • Introduction
    • Background
    • Content of a Pattern
    • Terminology
      • Architecture Patterns and Design Patterns
      • Patterns and the Architecture Continuum
      • Patterns and Views
      • Patterns and Business Scenarios
    • Architecture Patterns in Use
  • US Treasury Architecture Development Guidance (TADG)
    • TADG Pattern Content
    • TADG Architecture Patterns
  • IBM Patterns for e-Business
  • Some Pattern Resources
• Architecture Principles
  • Introduction
  • Characteristics of Architecture Principles
  • Components of Architecture Principles
  • Developing Architecture Principles
    • Qualities of Principles
  • Applying Architecture Principles
  • Example Set of Architecture Principles
    • Business Principles
    • Data Principles
    • Application Principles
    • Technical Technology Principles
• Architecture Skills Framework
  • Introduction
  • The Need for an IT Architecture Skills Framework
    • Definitional Rigor
    • The Basis of an Internal Architecture Practice
  • Goals/Rationale
    • Enterprise Certification of IT Architects
    • Specific Benefits
  • IT Architecture Role and Skill Categories
    • Overview
    • TOGAF Roles
    • Categories of Skills
    • Proficiency Levels
  • IT Architecture Role and Skill Definitions
    • Generic Skills
    • Business Skills & Methods
    • Enterprise Architecture Skills
    • Program or Project Management Skills
    • IT General Knowledge Skills
    • Technical IT Skills
    • Legal Environment
  • Generic Role and Skills of the IT Architect
    • Generic Role
    • Characterization in Terms of the Enterprise Continuum
    • Key Characteristics of an IT Architect
      • Skills and Experience in Producing Designs
      • Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines
      • Method-Driven Approach to Execution
      • Full Project Scope Experience
      • Leadership
      • Personal and Professional Skills
      • Skills and Experience in One or More Industries
  • Conclusions
• Developing Architecture Views
  • The Role of Architecture Views
    • Introduction
    • TOGAF and Standards for IT Architecture Description
    • A Note on Terminology
  • Basic Concepts
    • A Simple Example of a Viewpoint and View
  • Developing Views in the ADM
    • General Guidelines
    • View Creation Process
  • Core Taxonomy of Architecture Views
    • Overview
    • Stakeholders
    • Views/Viewpoints
    • Description
  • Views, Tools, and Languages
    • Overview
  • Views and Viewpoints
    • Example of Views and Viewpoints
    • Views and Viewpoints in Information Systems
    • The Need for a Common Language and Interoperable Tools for Architecture Description
  • Conclusions
  • Developing a Business Architecture View
    • Stakeholder and Concerns
    • Modeling the View
    • Key Issues
  • Developing an Enterprise Security View
    • Stakeholder and Concerns
    • Modeling the View
    • Basic Concepts
      • Information Domains
      • Strict Isolation
      • Absolute Protection
    • Security Generic Architecture View
    • Security Services Allocation
      • Operating System Services
      • Network Services
      • System Security Management Services
  • Developing a Software Engineering View
    • Stakeholders and Concerns
      • Development Approach
      • Software Modularity and Re-Use
      • Portability
      • Migration and Interoperability
    • Key Issues
      • Data-Intensive Versus Information-Intensive Software Systems
      • Achieving Interoperability
      • Software Tiers
      • Two-Tier
      • Three-Tier
      • Five-Tier
      • Some Uses of a Data Access Tier
      • One Possible Instantiation of a Data Access Interface
      • DAIs Enable Flexibility
      • Distribution
      • The Infrastructure Bus
    • Conclusion
  • Developing a System Engineering View
    • Stakeholder and Concerns
    • Key Issues
      • Client/Server Model
      • Master/Slave and Hierarchic Models
      • Peer-to-Peer Model
      • Distributed Object Management Model
  • Developing a Communications Engineering View
    • Stakeholder and Concerns
    • Key Issues
      • Communications Infrastructure
      • Communications Models
      • The OSI Reference Model
      • Communications Framework
      • Allocation of Services to Components
  • Developing a Data Flow View
    • Stakeholder and Concerns
    • Modeling the View
    • Key Issues
      • Database Management Systems
      • Database Models
      • Distributed DBMSs
      • Distributed Heterogeneous DBMSs
      • Data Dictionary/Directory Systems
      • Data Administration
      • Repository
      • Database Administration
      • Data Security
  • Developing an Enterprise Manageability View
    • Stakeholders and Concerns
    • Modeling the View
    • Key Issues
  • Developing an Acquirer's View
    • Stakeholders and Concerns
    • Modeling the View
    • Key Issues
    • Footnotes
• Building Blocks
  • Overview
  • Introduction to Building Blocks
    • Overview
    • Generic Characteristics
    • Architecture Building Blocks
      • Characteristics
      • Specification Content
    • Solution Building Blocks
      • Characteristics
      • Specification Content
  • Building Blocks and the ADM
    • Basic Principles
      • Building Blocks in Architecture Design
      • Building Block Design
    • Building Block Specification Process in the ADM
    • Levels of Modeling
      • Mapping the Modeling Levels to the ADM
  • Building Blocks Example
    • Introduction
    • Structure
    • Background to the Example
    • Business Process Level (Phase B)
    • Technical Functionality and Constraints Level (Phases B, C, & D)
      • Assumptions of Required Technical Functionality
    • Architectural Model Level (Phases B, C, and D)
      • Customer Information System Building Block Specification
      • Description
      • Mandated Building Blocks
      • Map to Business Organization Entities and Policies
    • Opportunity Identification (Phase E)
    • Re-Use of Building Blocks in Other Projects (Phases F to G)
• Business Process Domain Views
  • Introduction
  • Role
• Business Scenarios
  • Introduction
  • Benefits of Business Scenarios
  • Creating the Business Scenario
    • The Overall Process
    • Gathering
    • Analyzing
    • Reviewing
  • Contents of a Business Scenario
  • Contributions to the Business Scenario
  • Business Scenarios and the TOGAF ADM
  • Guidelines on Developing Business Scenarios
    • General Guidelines
    • Questions to Ask for Each Area
      • Identifying, Documenting, and Ranking the Problem
      • Identifying the Business & Technical Environment, and Documenting in Models
      • Identifying and Documenting Objectives
      • Identifying Human Actors and their Place in the Business Model
      • Identifying Computer Actors and their Place in the Technology Model
      • Documenting Roles, Responsibilities, Measures of Success, Required Scripts
      • Checking for Fitness-for-Purpose, and refining if necessary
  • Guidelines on Business Scenario Documentation
    • Textual Documentation
    • Business Scenario Models
  • Guidelines on Goals and Objectives
    • The Importance of Goals
    • The Importance of SMART Objectives
      • Example of Making Objectives SMART
    • Categories of Goals and Objectives
      • Goal: Improve Business Process Performance
      • Goal: Decrease Costs
      • Goal: Improve Business Operations
      • Goal: Improve Management Efficacy
      • Goal: Reduce Risk
      • Goal: Improve Effectiveness of IT Organization
      • Goal: Improve User Productivity
      • Goal: Improve Portability and Scalability
      • Goal: Improve Interoperability
      • Goal: Increase Vendor Independence
      • Goal: Reduce Lifecycle Costs
      • Goal: Improve Security
      • Goal: Improve Manageability
  • Summary
• Case Studies
  • The Role of Case Studies
  • Dairy Farm Group (Hong Kong)
  • Department of Social Security (UK)
    • Organizational Context
    • Existing IT
    • Strategic Objectives
    • The Accord Project
    • The Need for a New Architectural Architecture Framework
    • CISITAF Documentation Set
    • Technical Reference Model
    • Standards Information Base
    • Architecture Development Process
    • Architecture Views
    • Model Technical Architecture
    • Using the CISITAF
  • Litton PRC (US)
  • JEDMICS
    • Background
    • Definition of Existing Environment in Existing Terms
    • Restatement of Existing Environment in TOGAF Terms
    • Views, Constraints, and External Environments
      • Operations View
      • Management View
      • Security View
      • Constraints
      • Goals
      • External Environments
    • Target Architecture
    • Migration
  • Ministry of Defence (UK)
    • Executive Summary
    • Laying the Foundations
    • Constructing the Model
    • Building the Framework
    • Defining an Architecture
    • The Way Forward
  • NATO (Belgium)
  • Police IT Organization (UK)
    • Police IT
    • Objectives of NSPIS
    • Purpose
    • NSPIS Technical Architecture Manual
    • Applying the Framework
    • NSPIS Technical Reference Model
    • Interoperability
    • Technical Requirements and Views
    • The Architecture in Action
  • QA Consulting
  • Statskonsult (Norway)
    • Norway Streamlines Government Processes by Going Online
    • Working with The Open Group to Plan the Future
    • An Internet DialTone Framework as Easy-to-Use as the Telephone
  • Westpac (Australia)
    • Footnotes
• Glossary
  • AC
  • ACSE
  • Ada
  • ADM
  • ANSI
  • API
  • APP
  • Application
  • Application Platform
  • Application Portability Profile (APP)
  • Application Program Interface (API)
  • Application Software
  • APSE
  • Architectural Framework Architecture
  • Architecture, Baseline
  • Architecture Continuum
  • Architecture, Database
  • Architecture Framework
  • Architecture, Target
  • Architecture View
  • ASN
  • ASP
  • Availability
  • Base-Level Functions
  • Baseline
  • Batch Processing
  • Business System
  • CCITT
  • Client
  • CMIS
  • CMIP
  • COBIT
  • COBOL
  • Communications Mechanism
  • Communications Network
  • Communications Node
  • Communications System
  • Configuration Management
  • Connectivity Service
  • CORBA
  • Data Dictionary
  • Data Element
  • Database
  • Database Management System
  • Data Interchange Service
  • Data Management Service
  • DBMS
  • DCE
  • DDL
  • Default
  • Directory Service
  • DISA
  • Distributed Database
  • DMF
  • ECMA
  • EDI
  • EEI
  • End User
  • Enterprise
  • Enterprise Continuum
  • Enterprise Model
  • ERP
  • ES
  • Expand
  • External Environment Interface (EEI)
  • File
  • FIPS
  • FORTRAN
  • FTAM
  • Function
  • GNMP
  • GOSIP
  • GSS
  • GUI
  • Hardware
  • Human Computer Interface (HCI)
  • IEC
  • IEEE
  • III
  • III-RM
  • Information
  • Information Domain
  • Information System
  • Information Technology (IT)
  • Interface
  • Interoperability
  • IS
  • ISA
  • ISO
  • IT
  • ITIL
  • JTC1
  • LAN
  • Lifecycle
  • MAN
  • Metaview (also known as a Viewpoint)
  • MIS
  • MLS
  • MTA
  • Multimedia Service
  • NIST
  • NLSP
  • ODA
  • ODIF
  • OECD
  • OIW
  • OODBMS
  • Open Specifications
  • Open System
  • Open Systems Environment (OSE)
  • Operating System Service
  • ORB
  • OS
  • OSE
  • OSI
  • PEX
  • PHIGS
  • Platform
  • Portability
  • POSIX
  • Profile
  • Profiling
  • RAS
  • RDA
  • RDBMS
  • Repository
  • RM
  • RPC
  • Scalability
  • Security
  • Server
  • SGML
  • SIB
  • SMAP
  • SMTP
  • SNA
  • SNMP
  • Solutions Continuum
  • SQL
  • SWG
  • System
  • System and Network Management Service
  • System Stakeholder
  • TAFIM
  • Taxonomy of Architecture Views
  • TCP/IP
  • TCSEC
  • Technical Reference Model
  • TFA
  • TLSP
  • TNI
  • TP
  • Transaction
  • Transaction Sequence
  • TRM
  • TSIG
  • UIDL
  • UIMS
  • UISRM
  • User
  • User Interface Service
  • View
  • Viewpoint (also known as a Metaview)
  • WAN
• Other Architectures and Frameworks
  • Introduction
  • C4ISR Architecture Framework
    • Overview
    • Relationship to TOGAF
  • CORBA
    • Overview
    • Relationship to TOGAF
  • Enterprise Architecture Planning (EAP)
    • Comparison with TOGAF
  • Federal Enterprise Architecture: Practical Guide
    • Overview
    • Relationship to TOGAF
  • FEAF
    • Overview
    • Relationship to TOGAF
  • ISO/IEC TR 14252 (IEEE Std 1003.0)
    • Overview
    • Relationship to TOGAF
  • NCR Enterprise Architecture Framework
  • ISO RM-ODP
    • Overview
    • Relationship to TOGAF
  • SPIRIT Platform Blueprint Issue 3.0
    • Overview
    • Relationship to TOGAF
  • TAFIM
    • Overview
    • Relationship to TOGAF
  • TEAF
    • Overview
    • Relationship to TOGAF
  • Zachman Framework
    • Relationship to TOGAF Footnotes
• Tools for Architecture Development
  • Overview
  • Issues in Tool Standardization
  • Evaluation Criteria and Guidelines
    • Tool Criteria
      • Functionality
      • Key Features and Functions
      • Intuitiveness/Ease-of-Use Factors
      • Organizational Compatibility Factors
      • Tool Capacity/Scalability Constraints
      • Architecture of the Tool
      • Full Lifecycle Support
      • Interoperability Factors
      • Financial Considerations
      • Vendor Factors
    • General Pointers
• ADM and the Zachman Framework
  • Introduction
  • The Zachman Framework
  • Mapping TOGAF to the Zachman Framework
    • Preliminary Phase: Framework and Principles
    • Phase A: Architecture Vision
    • Phase B: Business Architecture
    • Phase C: Informations System Architectures: Data Architecture
    • Phase C: Informations System Architectures: Applications Architecture
    • Phase D: Technology Architecture
      • Step 1: Create a Baseline Description in the TOGAF Format
      • Step 2: Consider Different Architecture Reference Models, Viewpoints, and Tools
      • Step 3: Create an Architectural Model of Building Blocks
      • Step 4: Select the Services Portfolio Required per Building Block
      • Step 8: Conduct a Gap Analysis
      • Composite Mapping for Phase D
• INDEX

return to top of page

The TOGAF document set is designed for use with frames. To navigate around the document:

• In the main Contents frame at the top of the page, click the relevant hyperlink (Part I, Part II, etc.) to load the Contents List for that Part of the TOGAF document into the Secondary Index frame in the left margin.
  
  
• Then click in that Contents List to load a page into this main frame.
  
  

Downloads of the TOGAF documentation, are available under license from the TOGAF information web site . The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A hardcopy book is also available from The Open Group Bookstore as document G063 .