2 Understanding Enterprise Architecture m2 Slides
2 Understanding Enterprise Architecture m2 Slides
2 Understanding Enterprise Architecture m2 Slides
Joseph Anthony
@ansolabs | www.ansolabs.net
What Are Frameworks?
Consider the Periodic Table for Example
Frameworks are tools that help us
organize concepts, knowledge, thinking
and codify collective experience
They enable quicker and easier
comprehension domains as well as
consistent communication
EA can be quite daunting to practice in
the absence of the organizing
frameworks
EA frameworks help by organizing
concepts, principles, artefacts,
processes, templates, reference models
etc.
EA frameworks enable effective
collaboration with a wide spectrum of
stakeholders
Enterprise Architecture Timeline
Frameworks tend to have a lot of influence on how EA is practiced in the industry today
This module will provide a quick overview of two of the popular EA frameworks
The objective here is to provide overview of key concepts
Focus of This Module
Zachman TOGAF
(The Open Group
Framework Architecture Framework)
Zachman framework is a metamodel, it provides a model of a model
Executive
Perspective
Business
Mgmt.
Perspective
Architect
Perspective
Engineer
Perspective
Technician
Perspective
Enterprise
Perspective
Column ordering can be random
Ordering of
rows are fixed
Executive view, capturing the vision, strategy,
drivers etc.
Business management concepts and
information required to model the enterprise
Architectural perspectives of systems -
models, catalogs, matrices, patterns etc.
Engineering/ Design perspectives
Technology implementer’s perspectives
TOGAF content framework provides a more prescriptive metamodel describing the kinds of building blocks
A building block (described using catalogues, matrices, diagrams, patterns etc. ) represents an architectural or solution
component that can be reused
A collection of building blocks is referred to as architecture artefact
TOGAF Architecture Development Method (ADM)
Phase B:
Business architecture is developed in alignment with
Information
C architecture vision
Requirements
Systems
Management Architecture Phase C:
Information systems architecture, incorporating both
Applications architecture
Information (Data) architecture
Phase D:
Preliminary
Captures and describes the building blocks that make
up the enterprise’s technology infrastructure
Phase E:
A Identifies how the developed architecture can be
Architecture delivered and realized through solutions
vision
H
Architecture Phase F:
Change
Business B Formulates an architecture road map that describes
Management Architecture
transition from current state to future state architecture
Phase G:
Information
Provides the architectural oversight of implementation
Implementation Requirements
G Governance Management
Systems C
Architecture Phase H:
Establishes procedures for change management while
transitioning from current state to target state
Generic Specific