Core Concepts Flashcards
What is the TOGAF Standard?
The TOGAF standard is an architecture framework that provides the methods and tools for
assisting in the acceptance, production, use, and maintenance of an Enterprise Architecture.
What is architecture in the context of the TOGAF ?
The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.
There are four architecture domains that are commonly accepted as subsets of an overall Enterprise Architecture, all of which the TOGAF standard is designed to support
-
Business Architecture defines the business strategy, governance, organization, and
key business processes -
Data Architecture describes the structure of an organization’s logical and physical
data assets and data management resources - Application Architecture provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization
- Technology Architecture describes the logical 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, standards, etc.
Architecture Development Method
The TOGAF Architecture Development Method (ADM) provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures.
Preliminary Phase
The Preliminary Phase describes the preparation and initiation activities required to create an Architecture Capability** including **customization of the TOGAF framework** and d_efinition of Architecture Principles_**
Phase A: Architecture Vision
Phase A: Architecture Vision describes the initial phase of an architecture development cycle** It includes information about defining the **scope** of the architecture development initiative, **identifying the stakeholders**, **creating the Architecture Vision**, and obtaining **approval to proceed with the architecture development.
Phase B: Business Architecture
Phase B: Business Architecture describes the development of a Business Architecture to support the agreed Architecture Vision.
Phase C: Information Systems Architecture (_D_ata & _A_pplication)
Phase C: Information Systems Architectures describes the development of Information Systems Architectures to support the agreed Architecture Vision.
Phase D: Technology Architecture
Phase D: Technology Architecture describes the development of the Technology Architecture to support the agreed Architecture Vision
Phase E: Opportunities & Solutions
Phase E: Opportunities & Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases
Phase F: Migration Planning
Phase F: Migration Planning addresses how to move from the Baseline to the Target Architectures** by **finalizing** a **detailed Implementation and Migration Plan
Phase G: Implementation Governance
Phase G: Implementation Governance provides an architectural oversight of the implementation
Phase H: Architecture Change Management
Phase H: Architecture Change Management establishes procedures for managing change to the new architecture.
Requirements Management
Requirements Management examines the process of managing architecture requirements throughout the ADM.
Deliverable
A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders