Basic Concepts Flashcards
First Version
The first version of the TOGAF standard, developed in 1995
Structure of the TOGAF Library: Section 1: Foundation
Broadly applicable information relating to the subject of the TOGAF framework or Enterprise Architecture.
Structure of the TOGAF Library: Section 2: Generic Guidance and
Techniques
Information describing architecture styles and how the TOGAF framework and Enterprise Architecture can be adapted to exploit the characteristics of a more specific context.
Structure of the TOGAF Library: Section 3: Industry-Specific Guidance and Techniques
Information describing how the TOGAF framework and Enterprise Architecture can be applied to meet the specific needs of a vertical industry segment.
Structure of the TOGAF Library: Section 4: Organization-Specific Guidance and Techniques
nformation describing how the TOGAF framework and Enterprise Architecture have been applied to meet the needs of specific enterprises.
Enterprise
The TOGAF standard considers an “enterprise” to be any collection of organizations that has
common goals. For example, an enterprise could be a whole corporation, or a division of a
corporation; a government agency or a single government department; a chain of geographically
distant organizations linked together by common ownership; groups of countries or governments
working together to create common or shareable deliverables or infrastructures; partnerships and
alliances of businesses working together, such as a consortium or supply chain
Enterprise Architecture
Enterprise Architecture is:
1. The organizing logic for business processes and IT infrastructure reflecting the integration
and standardization requirements of the firm’s operating model.
[Source: MIT Center for Information Systems Research]
2. A conceptual blueprint that defines the structure and operation of an organization. The
intent of an Enterprise Architecture is to determine how an organization can most effectively
achieve its current and future objectives.
Architecture
The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.
Why do I Need Enterprise Architecture
More effective and efficient business operations
More effective and efficient Digital Transformation and IT operations
Better return on existing investment, reduced risk for future investment
Faster, simpler, and cheaper procurement
Architecture Framework
An architecture framework is a foundational structure, or set of structures, that can be used for
developing a broad range of different architectures. It should describe a method for designing a
target state of the enterprise in terms of a set of building blocks, and for showing how the
building blocks fit together. It should contain a set of tools and provide a common vocabulary. It
should also include a list of recommended standards and compliant products that can be used to
implement the building blocks.
Why do I Need a Framework for Enterprise Architecture?
Using an architecture framework will speed up and simplify architecture development, ensure
more complete coverage of the designed solution, and make certain that the architecture selected
allows for future growth in response to the needs of the business.
Architecture Domains supported by TOGAF
Business Architecture - The business strategy, governance, organization, and key business
processes.
Data Architecture - The structure of an organization’s logical and physical data assets and data
management resources.
Application Architecture - A blueprint for the individual application systems to be deployed, their
interactions, and their relationships to the core business processes of the organization.
Technology Architecture - The software and hardware capabilities that are required to support the
deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, and standards
The Architecture Development Method (ADM)
The ADM describes a process for deriving an organization-specific Enterprise Architecture that
addresses business requirements The ADM is the major component of the TOGAF framework and provides guidance for
architects on a number of levels: architecture development phases
ADM Guidelines and Techniques
provides a number of guidelines and techniques to support
the application of the ADM. The guidelines include adapting the ADM to deal with a number of
usage scenarios, including different process styles (e.g., the use of iteration) and applying the
ADM across the Architecture Landscape.
Architecture Content Framework
provides a detailed model of architectural work
products, including deliverables, artifacts within deliverables, and the Architecture Building
Blocks (ABBs) that deliverables represent.