Core Concepts Flashcards
Phases of the ADM
- Preliminary Phase
- Phase A: Architecture Vision
- Phase B: Business Architecture
- Phase C: Information Systems Architectures
- Phase D: Technology Architecture
- Phase E: Opportunities and Solutions
- Phase F: Migration Planning
- Phase G: Implementation Governance
- Phase H: Architecture Change Management
- Requirements Management
Preliminary Phase
Describes the preparation and initiation activities required to create an Architecture Capability, including the customization of the TOGAF framework, and the definition of Architecture Principles.
Phase A: Architecture Vision
Describes the initial phase of an Architecture Development Cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.
Phase B: Business Architecture
Describes the development of a Business Architecture to support an agreed Architecture Vision.
Phase C: Information Systems Architectures
Describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.
Phase D: Technology Architecture
Describes the development of the Technology Architecture for an architecture project.
Phase E: Opportunities and Solutions
Describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture defined in the previous phases.
Phase F: Migration Planning
Describes the development of a detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture.
Phase G: Implementation Governance
Provides an architectural oversight of the implementation.
Phase H: Architecture Change Management
Establishes procedures for managing change to the new architecture.
Requirements Management
Examines the process of managing architecture requirements throughout the ADM.
The Architecture Content Framework uses three categories to describe the type of architectural work product within the context of use.
- Deliverable
- Artifact
- Building block
Deliverable
Is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders
Artifact
Is an architectural work product that describes an aspect of the architecture
Building block
Represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions
The Enterprise Continuum and the Architecture Repository
The Enterprise Continuum provides a view of the Architecture Repository that shows the evolution of these related architectures from generic to specific, from abstract to concrete, and from logical to physical.
The Enterprise Continuum and the Architecture Repository
The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures.
Concepts of the Enterprise Continuum
- Architecture Continuum
- Solutions Continuum
Components within an Architecture Repository
- Architecture Metamodel
- Architecture Capability
- Architecture Landscape
- Standards Information Base (SIB)
- Reference Library
- Governance Log
- Architecture Requirements Repository
- Solutions Landscape
Architecture Metamodel
Describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content.
Architecture Capability
Defines the parameters, structures, and processes that support governance of the Architecture Repository
Architecture Landscape
Shows an architectural view of the building blocks that are in use within the organization today (e.g., a list of the live applications); the landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives
Standards Information Base (SIB)
Captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization
Reference Library
Provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise
Governance Log
Provides a record of governance activity across the enterprise
Architecture Requirements Repository
Provides a view of all authorized architecture requirements which have been agreed with the Architecture Board
Solutions Landscape
Presents an architectural representation of the SBBs supporting the Architecture Landscape which have been planned or deployed by the enterprise
Architecture Capability Framework Contents Summary
- Establishing an Architecture Capability. Guidelines for establishing an Architecture Capability within an organization.
- Architecture Board. Guidelines for establishing and operating an enterprise Architecture Board.
- Architecture Compliance. Guidelines for ensuring project compliance with architecture.
- Architecture Contracts. Guidelines for defining and using Architecture Contracts.
- Architecture Governance. Framework and guidelines for Architecture Governance.
- Architecture Maturity Models. Techniques for evaluating and quantifying an organization’s maturity in Enterprise Architecture.
- Architecture Skills Framework. A set of role, skill, and experience norms for staff undertaking Enterprise Architecture work.
The Enterprise Continuum.
Provides methods for classifying artifacts
Architecture Capability Framework
Discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture practice within an enterprise
To promote effective architectural activity within the enterprise, the TOGAF standard recommends the establishment of a(n)
Enterprise Architecture Capability
Architecture Capability
A class of architectural information within the Architecture Repository that defines processes supporting the governance of the Architecture Repository
Purpose of the TOGAF Library
To accelerate the creation of new enterprise architectures
Use the Architecture Development Method
is recommended to achieve a customer-focused, value-adding, and sustainable architecture practice
Preliminary phase
Includes the objective of establishing the organizational model for Enterprise Architecture
