B1-4

EA frameworks and modeling

(with TOGAF and Archimate intro)
Case discussion
By Stephane Jans
 2

Case Study

See Y121.pdf

All products and trademarks mentioned are the property of their legitimate owners
(and listed here for educational purpose only)

Executive Master in IT Management- 2016 1/03/16

 What is the TOGAF ADM?

• The ADM forms the core of TOGAF

• The result of contributions from many architecture practitioners
• It is specifically designed to address enterprise’s business and IT
needs by providing:
– A set of architecture views (business, data, application, technology)
– Guidelines on tools for architecture development
– A set of recommended deliverables
– Links to practical case studies
– A method for managing requirements

Licensed from The Open Group. Adapted and reproduced with permission 3
 The Architecture Development Method (ADM)

• The core of TOGAF

• A proven way of developing an
architecture
• Specifically designed to address
business requirements
• An iterative method
• A set of architecture views to
ensure that a complex set of
requirements are adequately
addressed

Licensed from The Open Group. Adapted and reproduced with permission 4
 ADM – Basic Principles

An iterative method, over the whole

process, between phases and within
phases
Each iteration = new decisions:
Enterprise coverage
Level of detail
Time horizon
Architecture asset re-use:
previous ADM iterations
other frameworks, system
models, industry models,…
Decisions based on:
Competence / resource availability
Value accruing to the enterprise.

Licensed from The Open Group. Adapted and reproduced with permission 5
 ADM – Basic Principles

Every phase is validated

against and validates the
current requirements of the
business

Licensed from The Open Group. Adapted and reproduced with permission 6
Prepare the organization for a successful
architecture project
ADM Phases

Ensure that very stage of a TOGAF

project is based on and validates
business requirements
7
Licensed from The Open Group. Adapted and reproduced with permission
 Preliminary Phase

• This phase prepares the

organisation for undertaking
successful enterprise
architecture projects
– Understand business
environment
– High level management
commitment
– Agreement on scope
– Establish principles
– Establish governance
structure
– Agree method to be
adopted

Licensed from The Open Group. Adapted and reproduced with permission 8
 9

Executive Master in IT Management- 2016 1/03/16

 Set the scope, constraints and
expectations for a TOGAF project;
ADM Phases create the Architecture Vision;
validate the business context; create
the Statement of Architecture Work

Ensure that very stage of a TOGAF

project is based on and validates
business requirements
10
Licensed from The Open Group. Adapted and reproduced with permission
 Phase A: Architecture Vision

• Initiates one iteration of the

architecture process
– Sets scope, constraints,
expectations
– Required at the start of
every architecture cycle
• Create the Architecture Vision
• Validates business context
• Creates Statement of
Architecture work

Licensed from The Open Group. Adapted and reproduced with permission 11
 12

Phase A: Architecture Vision

Role

Driver

Executive Master in IT Management- 2016 1/03/16

 13

TOGAF Templates

Executive Master in IT Management- 2016 1/03/16

 14

Phase A: Architecture Vision

Driver

Goal

Executive Master in IT Management- 2016 1/03/16

 15

Phase A: Architecture Vision

Goal

Principle

Executive Master in IT Management- 2016 1/03/16

 16

TOGAF Templates
• TOGAF: Principle Catalog

Name <Name of Principle>

Statement The Statement should succinctly and unambiguously communicate the fundamental rule. For
the most part, the principles statements for managing information are similar from one
organization to the next. It is vital that the principles statement be unambiguous.
Rationale The Rationale should highlight the business benefits of adhering to the principle, using business
terminology. Point to the similarity of information and technology principles to the principles
governing business operations. Also describe the relationship to other principles, and the
intentions regarding a balanced interpretation. Describe situations where one principle would be
given precedence or carry more weight than another for making a decision.
Implications The Implications should highlight the requirements, both for the business and IT, for carrying
out the principle – in terms of resources, costs, and activities/tasks. It will often be apparent that
current systems, standards, or practices would be incongruent with the principle upon adoption.
The impact to the business and consequences of adopting a principle should be clearly stated.
The reader should readily discern the answer to: “How does this affect me?” It is important not
to oversimplify, trivialize, or judge the merit of the impact. Some of the implications will be
identified as potential impacts only, and may be speculative rather than fully analyzed.

Executive Master in IT Management- 2016 1/03/16

 ADM Phases

Develop Business Architecture

Develop baseline and target
architectures and
analyze the gaps

Ensure that very stage of a TOGAF

project is based on and validates
business requirements
17
Licensed from The Open Group. Adapted and reproduced with permission
 Phase B: Business Architecture

• The fundamental organization

of a business, embodied in
– its business processes and
people,
– their relationships
• to each other and the
environment,
– and the principles
governing its design and
evolution
• Shows how the organization
meets its business goals

Licensed from The Open Group. Adapted and reproduced with permission 18
 Business Architecture - Contents

• Organization structure
• Business goals and objectives
• Business functions
• Business Services
• Business processes
• Business roles
• Correlation of organization and
functions.

Licensed from The Open Group. Adapted and reproduced with permission 19
 Business Architecture - Steps

1. Select reference models,

viewpoints and tools
2. Define Baseline Architecture
Description
3. Define Target Architecture
Description
4. Perform gap analysis
5. Define roadmap components
6. Conduct formal stakeholder
review
7. Finalize the Architecture
8. Create Architecture Definition
Document

Licensed from The Open Group. Adapted and reproduced with permission 20
 21

Executive Master in IT Management- 2016 1/03/16

 22

Actor

Location

Executive Master in IT Management- 2016 1/03/16

 23

TOGAF Templates
• TOGAF: Organization Decomposition

Executive Master in IT Management- 2016 1/03/16

 24

Actor
Function

Executive Master in IT Management- 2016 1/03/16

 25

TOGAF Templates
• TOGAF: Functional Decomposition

Support Primary

Human Marketing
Business
Admin Finance & Engineering Inventory Manufacturing Distribution
Resources Planning
Sales

Manage Public Develop & Track Plan Human Formulate Develop New Research and Plan Material Plan Engineer
Develop Manufacturing
Relations Financial Plan Resources Strategy Business Technology Requirements Requirements Packages

Acquire Develop and Establish Procure

Provide Legal Appropriate Engineer and Perform Quality Ship
Human Maintain Customer Equipment
Services Funds Resources Business Plan Design Products Material & Tools Engineering Products
Requirements

Perform Develop & Engineer and Convert

Develop Obtain Sales Manage
Audit Manage Design Resources
& Controls Product Cost Employees Commitments Processes Suppliers to Product

Provide Provide
Manage Manage Design Tools Manage Control
Employee Customer
Transportation Payables Services Support and Equipment Inventory Production

Manage Maintain Plant

Maintain Manage Manage Union Engineering Equipment &
Facilities Receivables Activities Changes Tools

Provide Manage
Terminate Active Warranty
Administrative Manage Assets
Services Employment Activities

Executive Master in IT Management- 2016 1/03/16

 26

TOGAF Templates
• TOGAF: Functional Decomposition

Executive Master in IT Management- 2016 1/03/16

 27

Executive Master in IT Management- 2016 1/03/16

 28

TOGAF Templates
• TOGAF: Process Flow Diagram /

Executive Master in IT Management- 2016 1/03/16

 ADM Phases

Develop Information
Systems Architectures
Develop baseline and target
architectures and
analyze the gaps

Ensure that very stage of a TOGAF

project is based on and validates
business requirements
29
Licensed from The Open Group. Adapted and reproduced with permission
 Phase C: Information Systems Architectures

• The fundamental organization

of an IT system, embodied in
• The major types of
information and application
systems that process them
• relationships to each other
and the environment, and
the principles governing its
design and evolution
• Shows how the IT systems
meets the business goals of the
enterprise

Licensed from The Open Group. Adapted and reproduced with permission 30
 Data or Applications first ?

• It is usually necessary to address

both
• Not always the case,
depending on project scope
and constraints
• May be developed in either order,
or in parallel
• Theory suggests Data
Architecture comes first
• Practical considerations may
mean that starting with
Application Systems may be
more efficient
• There will need to be some
iteration to ensure consistency

Licensed from The Open Group. Adapted and reproduced with permission 31
 32

Executive Master in IT Management- 2016 1/03/16

 33

Executive Master in IT Management- 2016 1/03/16

 34

TOGAF Templates
• TOGAF: Application Communication (ppt)

Executive Master in IT Management- 2016 1/03/16

 35

TOGAF Templates
• TOGAF: Application Communication (ppt)

Executive Master in IT Management- 2016 1/03/16

 36

TOGAF Templates
• TOGAF: Application Communication (ppt)

Executive Master in IT Management- 2016 1/03/16

 37

Executive Master in IT Management- 2016 1/03/16

 38

TOGAF Templates
• TOGAF: application/organization matrix, application/function matrix

Executive Master in IT Management- 2016 1/03/16

 39

Executive Master in IT Management- 2016 1/03/16

 40

• TOGAF: Logical Data Diagram /

Executive Master in IT Management- 2016 1/03/16

 41

Executive Master in IT Management- 2016 1/03/16

 42

Executive Master in IT Management- 2016 1/03/16

 43

TOGAF Templates
• TOGAF: Data dissemination diagram

Executive Master in IT Management- 2016 1/03/16

 44

TOGAF Templates
• TOGAF: Data dissemination diagram

Executive Master in IT Management- 2016 1/03/16

 45

TOGAF Templates
• TOGAF: Data dissemination diagram

Executive Master in IT Management- 2016 1/03/16

 ADM Phases

Develop Technology
Architecture

Develop baseline and target

Ensure that very stage of a TOGAF architectures and
project is based on and validates analyze the gaps
business requirements
46
Licensed from The Open Group. Adapted and reproduced with permission
 Phase D: Technology Architecture

• The fundamental organization

of an IT system, embodied in
• its hardware, software and
communications
technology
• their relationships to each
other and the environment,
• and the principles
governing its design and
evolution

Licensed from The Open Group. Adapted and reproduced with permission 47
 48

Executive Master in IT Management- 2016 1/03/16

 49

Executive Master in IT Management- 2016 1/03/16

 50

• TOGAF: Environments and Locations diagram

Executive Master in IT Management- 2016 1/03/16

 51

Executive Master in IT Management- 2016 1/03/16

 52

Executive Master in IT Management- 2016 1/03/16

 53

Executive Master in IT Management- 2016 1/03/16

 54

Executive Master in IT Management- 2016 1/03/16

 55

Executive Master in IT Management- 2016 1/03/16

 56

In PDF

Executive Master in IT Management- 2016 1/03/16

 57

Executive Master in IT Management- 2016 1/03/16

 58

Executive Master in IT Management- 2016 1/03/16

 59

Executive Master in IT Management- 2016 1/03/16

 ADM Phases

Ensure that very stage of a TOGAF

project is based on and validates
business requirements Perform initial implementation
planning; identify major 60
Licensed from The Open Group. Adapted and reproduced with permission
implementation projects
 Phase E: Opportunities and Solutions

• Perform initial implementation

planning
• Identify the major
implementation projects
• Group projects into Transition
Architectures
• Decide on approach
• Make v Buy v Re-Use
• Outsource
• COTS
• Open Source
• Assess priorities
• Identify dependencies

Licensed from The Open Group. Adapted and reproduced with permission 61
 62

Executive Master in IT Management- 2016 1/03/16

 63

Executive Master in IT Management- 2016 1/03/16

 ADM Phases

Analyze costs, benefits and

risks; develop detailed
Implementation and Migration
Plan

Ensure that very stage of a TOGAF

project is based on and validates
business requirements
64
Licensed from The Open Group. Adapted and reproduced with permission
 Phase F: Migration Planning

• For projects identified in Phase

E perform
• Cost/benefit analysis
• Risk assessment
• Develop a detailed
Implementation and Migration
Plan

Licensed from The Open Group. Adapted and reproduced with permission 65
 ADM Phases

Provide architectural oversight

for the implementation; ensure
that the implementation project
conforms to the architecture

Ensure that very stage of a TOGAF

project is based on and validates
business requirements
66
Licensed from The Open Group. Adapted and reproduced with permission
 Phase G: Implementation Governance

• Provide architectural oversight

for the implementation.
• Defines architecture
constraints on implementation
projects
• Architecture contract
• Monitors implementation work
for conformance
• Produce a Business Value
Realization.

Licensed from The Open Group. Adapted and reproduced with permission 67
 ADM Phases
Provide continual monitoring and a
change management process to ensure
that the architecture responds to the
needs of the enterprise

Ensure that very stage of a TOGAF

project is based on and validates
business requirements
68
Licensed from The Open Group. Adapted and reproduced with permission
 Phase H: Architecture Change Management

• Provide continual monitoring

and a change management
process
• Ensures that changes to the
architecture are managed in a
cohesive and architected way
• Establishes and supports the
Enterprise Architecture to
provide flexibility to evolve
rapidly in response to changes
in the technology or business
environment
• Monitors the business and
capacity management.

Licensed from The Open Group. Adapted and reproduced with permission 69
 Architecture Development Method – Process

• The ADM is an iterative process:

– Over the whole process
– Between phases
– Within phases
• For each iteration, re-consider:
– Scope
– Detail
– Schedules, milestones

Licensed from The Open Group. Adapted and reproduced with permission 70
 Architecture Development Method – Process

• Consider assets from:

– Previous iterations
– Marketplace, according to
availability,competence,
and value:
• Other frameworks
• Systems models
• Vertical Industry models

Licensed from The Open Group. Adapted and reproduced with permission 71
 Relationship to other Parts of TOGAF
The ADM forms the core
It is supported by the other main parts of TOGAF:
– ADM Guidelines and Techniques
• Set of guidelines, templates, checklists
– Architecture Content Framework
– The Enterprise Continuum
• Framework and context for architecture assets including descriptions,
models and patterns
– TOGAF Reference Models
– The Architecture Capability Framework

Licensed from The Open Group. Adapted and reproduced with permission 72
 73

Executive Master in IT Management- 2016 1/03/16

 Prepare the organization for a successful Set the scope, constraints and
architecture project expectations for a TOGAF project;
ADM Phases create the Architecture Vision;
validate the business context; create
Provide continual monitoring and a the Statement of Architecture Work
change management process to ensure
that the architecture responds to the Develop Business Architecture
needs of the enterprise Develop baseline and target
architectures and
analyze the gaps
Provide architectural oversight
for the implementation; ensure
that the implementation project
conforms to the architecture Develop Information
Systems Architectures
Develop baseline and target
architectures and
Analyze costs, benefits and analyze the gaps
risks; develop detailed
Implementation and Migration
Develop Technology
Plan
Architecture

Develop baseline and target

Ensure that very stage of a TOGAF architectures and
project is based on and validates analyze the gaps
business requirements Perform initial implementation
planning; identify major 74
Licensed from The Open Group. Adapted and reproduced with permission
implementation projects
 75

ADM: Overview

Executive Master in IT Management- 2016 1/03/16

 ADM Guidelines and Techniques
• A set of guidelines and techniques to support the application of the ADM
• The guidelines help to adapt the ADM to deal with different scenarios, including
different process styles (e.g. the use of iteration) and also specific requirements
(e.g. security).
• The techniques support specific tasks within the ADM (e.g. defining principles,
business scenarios, gap analysis, migration planning, risk management, etc).

Licensed from The Open Group. Adapted and reproduced with permission 76
 Applying Iteration to the ADM

Example Guideline

Licensed from The Open Group. Adapted and reproduced with permission 77
 Applying the ADM at Different Levels

Example Guideline

Licensed from The Open Group. Adapted and reproduced with permission 78
 79

Executive Master in IT Management- 2016 1/03/16

 80

Executive Master in IT Management- 2016 1/03/16

 81

Executive Master in IT Management- 2016 1/03/16

 82

Executive Master in IT Management- 2016 1/03/16

 83

• TOGAF: Solution Concept Diagram

Executive Master in IT Management- 2016 1/03/16

 84

Executive Master in IT Management- 2016 1/03/16

 85

• TOGAF: Business Footprint Diagram

Executive Master in IT Management- 2016 1/03/16

 86

Executive Master in IT Management- 2016 1/03/16

 87

Executive Master in IT Management- 2016 1/03/16

 88

Executive Master in IT Management- 2016 1/03/16

 89

Executive Master in IT Management- 2016 1/03/16

 90

Executive Master in IT Management- 2016 1/03/16

 91

Executive Master in IT Management- 2016 1/03/16

 92

• TOGAF: Project Context Diagram

Executive Master in IT Management- 2016 1/03/16

 93

Appendix
 realization
access

Passive: Behavioral: Active/Structure:

Elements that cannot act Elements that represent the Elements that act
and which are acted upon Behavior of the active elements.
by the behavior
Source: Mastering Archimate (2nd Edittion), Gerben Wierda
 95

Visibility
and use

Internals

Source: Mastering Archimate (2nd Edittion), Gerben Wierda

Executive Master in IT Management- 2016 1/03/16
 96

realization
access

Source: Mastering Archimate (2bd Edittion), Gerben Wierda

Executive Master in IT Management- 2016 1/03/16
 97

Used by

realizes

Executive Master in IT Management- 2016 1/03/16

 98

Source: Mastering Archimate (2bd Edittion), Gerben Wierda

Executive Master in IT Management- 2016 1/03/16
 99

Zachman Framework – Row 1

Scope/Planner’s View
§ Motivation/Why • External Requirements
Business goals, objectives and performance
measures related to each function and Drivers
n Function/How • Business Function
High-level business functions
Modeling
n Data/What
High-level data classes related to each
function What How Where Who When Why

1 Contextual Contextual
n People/Who
Stakeholders related to each function Conceptual Conceptual

Logical Logical
n Network/Where
VA locations related to each function Physical Physical

As Built As Built
n Time/When
Cycles and events related to each Functioning Functioning
function What How Where Who When Why
 100

Zachman Framework – Row 2

Enterprise Model/Designer’s View
§ Motivation/Why • Business Process Models
Policies, procedures and standards for each
process • Business Function
n Function/How Allocation
Business processes
• Elimination of Function
n Data/What Overlap and Ambiguity
Business data
What How Where Who When Why

Contextual Contextual
n People/Who
VA roles and responsibilities in each 2 Conceptual Conceptual
process
Logical Logical
n Network/Where
VA locations related to each process Physical Physical

As Built As Built
n Time/When
Events for each process and sequencing Functioning Functioning
of integration and process improvements What How Where Who When Why
 101

Zachman Framework – Row 3

System Model/Designer’s View
§ Motivation/Why • Logical Models
VA policies, standards and procedures
associated with a business rule model • Project Management
n Function/How
Logical representation of information
• Requirements Definition
systems and their relationships
n Data/What
Logical data models of data and data
relationships underlying VA information What How Where Who When Why

Contextual Contextual
n People/Who
Logical representation of access privileges Conceptual Conceptual
constrained by roles and responsibilities
3 Logical Logical
n Network/Where
Logical representation of the distributed Physical Physical
system architecture for VA locations
As Built As Built
n Time/When
Logical events and their triggered responses Functioning Functioning
constrained by business events and their responses What How Where Who When Why
 102

Zachman Framework – Row 4

Technology Model/Builder’s View
§ Motivation/Why
• Physical Models
VA business rules constrained by information
systems standards
• Technology Management
Function/How
Solution Definition and
n
Specifications of applications that operate •
on particular technology platforms Development
n Data/What
Database management system (DBMS) type
requirements constrained by logical data models What How Where Who When Why

Contextual Contextual
n People/Who
Specification of access privileges to Conceptual Conceptual
specific platforms and technologies
Logical Logical
n Network/Where
Specification of network devices and their 4 Physical Physical
relationships within physical boundaries
As Built As Built
n Time/When
Specification of triggers to respond to system Functioning Functioning
events on specific platforms and technologies What How Where Who When Why
 103

Zachman Framework – Row 5

As Built/Integrator’s View
§ Motivation/Why • As Built
VA business rules constrained by specific
technology standards • Configuration Management
n Function/How
Programs coded to operate on specific
• Deployment
technology platforms
n Data/What
Data definitions constrained by physical
data models What How Where Who When Why

Contextual Contextual
n People/Who
Access privileges coded to control access Conceptual Conceptual
to specific platforms and technologies
Logical Logical
n Network/Where
Network devices configured to conform to Physical Physical
node specifications
5 As Built As Built
n Time/When
Timing definitions coded to sequence Functioning Functioning
activities on specific platforms and technologies What How Where Who When Why
 104

Zachman Framework – Row 6

Functioning Enterprise/User’s View
§ Motivation/Why • Functioning Enterprise
Operating characteristics of specific
technologies constrained by standards • Operations Management
n Function/How • Evaluation
Functioning computer instructions

n Data/What
Data values stored in actual databases
What How Where Who When Why

Contextual Contextual
n People/Who
VA personnel and key stakeholders Conceptual Conceptual
working within their roles and responsibilities
Logical Logical
n Network/Where
Sending and receiving messages Physical Physical

Integrated Integrated
n Time/When
Timing definitions operating to sequence 6 Functioning Functioning
activities What How Where Who When Why
 105

Why EA is an Elephant

And this course has to adapt…

 106

Useful metaphor

Executive Master in IT Management- 2016 1/03/16

 107

Useful Metaphor

Executive Master in IT Management- 2016 1/03/16

 108

Useful Metaphor

Executive Master in IT Management- 2016 1/03/16

 109

Useful Metaphor

Executive Master in IT Management- 2016 1/03/16

 110

(Less?) Useful Metaphor

Executive Master in IT Management- 2016 1/03/16

 111

Executive Master in IT Management- 2016 1/03/16

 112

Architecture: definition
• “An Architecture is the fundamental organization of something, embodied in:
– its components,
– their relationships to each other and the environment,
– and the principles governing its design and evolution.”

(Adapted from ANSI/IEEE Standard 1471-2000)

• “Architecture represents the significant design decisions that shape a system,

where significant is measured by cost of change.” – Grady Booch

Executive Master in IT Management- 2016 1/03/16