7/09/2020

2
 7/09/2020

Before We Get Started

 Evacuation Procedures
 House Rules
 Mobile Device Usage
 Course Timings
 Start 9:00
 Breaks 15 mins
 Lunch 45 mins
 Close 17:00
 Special Needs?
 AOB?

Introductions

 Name / Role/ Company

 Experience in EA and TOGAF
 Course Objectives
 One thing of interest about yourself

4
 7/09/2020

Tools
 Course workbook
 Case Study
 Optional Exercises
 Class discussion & Elevator pitches
 Quick quizzes
 TOGAF document
 Class Experience
 Homework

About The Slides

 Partly instruction partly reference
 Common terminology used
 Amplification

 Not all slides will be discussed during the day

 ALL slides should be revised as evening work

6
 7/09/2020

Course Outline
 Course Introduction
 Module F13: The TOGAF Certification for People Program
 Module 1: Management Overview
 Module F6: ADM Phases Level 1
 Module F7: ADM Guidelines and Techniques
 Module F11: ADM Deliverables Level 1
 Module F12: TOGAF Reference Models
 Module 2: The TOGAF Framework Components
 Module 3: Introduction to the Architecture Development Method
 Method 4: The Enterprise Continuum and Tools
 Module 5: Architecture Repository
 Module 6: Architecture Content Framework
 Module 7: TOGAF Content Metamodel
 Module 8: Preliminary Phase
 Module 9: Architecture Governance 7

Course Outline
 Module 10: Business Scenarios
 Module 11: Stakeholder Management
 Module 12: Architecture Views and Viewpoints
 Module 13: Building Blocks
 Module 14: Architecture Implementation Support Techniques
 Module 15: Phase A: Architecture Vision
 Module 16A: Phase B: Business Architecture – Catalogs, Matrices and Diagrams
 Module 16: Phase B: Business Architecture
 Module 17: Phase C: Information Systems Architectures – Overview
 Module 18A: Phase C: Data Architecture – Catalogs, Matrices and Diagrams
 Module 18: Phase C: Data Architecture
 Module 19: The Integrated Information Infrastructure Reference Model
 Module 20A: Phase C: Application Architecture – Catalogs, Matrices and Diagrams
 Module 20: Phase C: Application Architecture

8
 7/09/2020

Course Outline
 Module 21: TOGAF Foundation Architecture: the TRM
 Module 22A: Phase D: Technology Architecture – Catalogs, Matrices and Diagrams
 Module 22: Phase D: Technology Architecture
 Module 23: Migration Planning Techniques
 Module 24: Phase E: Opportunities and Solutions
 Module 25: Phase F: Migration Planning
 Module 26: Phase G: Implementation Governance
 Module 27: Phase H: Architecture Change Management
 Module 28: ADM Architecture Requirements Management
 Module 29: Architecture Partitioning
 Module 30: Adapting the ADM: Iteration and Levels
 Module 31: Adapting the ADM: Security
 Module 33: Architecture Maturity Models
 Module 34: Architecture Skills Framework
9

TOGAF® Standard Courseware

Version 9.2 Edition

TOGAF is a registered trademark of The Open

Group in the United States and other
countries

10
 7/09/2020

Course Objectives

 Introduce you to the TOGAF methodology

 Develop the EA perspective
 Start you considering how to apply TOGAF at
work
 Help you prepare for the exams

11

Course contents
 Exam Basics
 Core Concepts
 ADM Phases
 ADM Guidelines & Techniques
 Enterprise Continuum & Tools
 Describing the Enterprise
 ADM Deliverables
 Architecture Governance
 Building Blocks
 Views & Viewpoints

12
 7/09/2020

TOGAF 9.2 Certification Levels

Level Exam Purpose

To provide validation that the candidate has gained

TOGAF 9.2 knowledge of the terminology and basic concepts of
1 TOGAF 9 and understands the core principles of
Foundation
Enterprise Architecture and TOGAF

To provide validation that in addition to knowledge

TOGAF 9.2 and comprehension, the candidate is able to
2 analyze and apply knowledge of TOGAF
Certified

13

Exam Approach

14

14
 7/09/2020

Level 1 exam requirements

Exam Details
TOGAF 9.1 Exam Type: Multiple Choice
Foundation 40 Questions / 60 minutes
Supervised: Yes
Open Book: No
Pass mark: 22

Note: Both exam details subject to change – always

check the Open Group Website before taking the exam

15

Level 1: Exam topic areas

 Basic Concepts (3 questions)
 Core Concepts (3 questions)
 Introduction to the ADM (3 questions)
 The Enterprise Continuum and Tools (4 questions)
 ADM Phases (9 questions)
 ADM Guidelines and Techniques (6 questions)
 Architecture Governance (4 questions)
 Architecture Views, Viewpoints and Stakeholders (2 questions)
 Building Blocks (2 questions)
 ADM Deliverables (2 questions)
 TOGAF Reference Models (2 questions)

16
 7/09/2020

Level 2 is a superset of Level 1

TOGAF 9.1 Certified

TOGAF 9.1 Foundation

17

Level 2 exam requirements

Exam Details
TOGAF 9.2 Exam Type: Complex Multiple Choice Scenario-based
Certified 8 Questions / 90 minutes
Supervised: Yes
Open Book: Yes (Electronic version supplied as part
of exam interface)

Pass mark: 24/40

Note: You must pass the Level 1 exam before attempting the Level 2

18
 7/09/2020

Level 2: Exam topic areas

Eight questions:

 ADM Phases: Project Establishment (phases Preliminary, A, Requirements

Management)
 ADM Phases: Architecture Definition (phases B,C,D)
 ADM Phases: Transition Planning (phases E and F)
 ADM Phases: Governance (phases G and H)
 Adapting the ADM
 Architecture Content Framework
 TOGAF Reference Models
 Architecture Capability Framework

19

Level 2 Combined Exam

Exam Details
TOGAF 9.2 TOGAF 9 Combined Part 1 and 2
Certified Exam Type: Two sections in a single exam corresponding to the TOGAF
9 Part 1 and 2 exams:

• Each section must be passed in order to obtain an overall pass mark

• If you fail a section then no certification is awarded, however you only
need retake the Examination corresponding to the failed section
• You must wait one month before a retake

20
 7/09/2020

Exam points to be aware of

 Contact your sales advisor to obtain an electronic voucher for the Direct
(combined) exam
 Voucher valid for approximately one year
 Use this voucher to book an exam slot
 Do not forget the two forms of ID needed to take the exam
 See prometric web site
 Remember all exams subject to change
 You cannot re-sit an exam within the month
 You cannot attempt Level 2 without passing Level 1 (unless attempting
Direct exam)

21

Exam Details
 Email [email protected] to obtain an electronic
voucher for the Direct (combined) exam
 Voucher valid for approximately one year
 Use this voucher to book an exam slot via
 http://pearsonvue.com/theopengroup
 Do not forget the two forms of ID needed to take the exam
 See pearsonvue.com website
 Remember all exams are subject to change
 You cannot resit an exam within the month
 You cannot attempt Level 2 without passing Level 1 (unless attempting
Direct exam)

22
 7/09/2020

Certification: Final Steps

 Within 6 to 14 working days of receipt of the exam results you will receive an
email from The Open Group and be invited to login to complete your
certification
 You may download and print your certificate
 You can adjust your register entry to make it public (the default is to be
confidential)

23

What is TOGAF®?

 TOGAF is an architecture framework – The Open Group

Architecture Framework.
 TOGAF is a tool for assisting in the acceptance, production,
use, and maintenance of enterprise architectures.
 The first version of TOGAF, developed in 1995, was based on the
US Department of Defense Technical Architecture Framework
for Information Management (TAFIM).
 The key to TOGAF is the method – the TOGAF Architecture
Development Method (ADM) – for developing an enterprise
architecture that addresses business needs.

24
 7/09/2020

TOGAF Development Overview

25

25

What Are The Benefit's Of TOGAF

26

26
 7/09/2020

• Applying Iteration
•Establishing an to the ADM
• Applying the ADM at different

Overview of TOGAF Content

Service-Oriented Architecture Capability
Enterprise Levels
Architecture • Security Architecture and the
• Architecture
ADM Board
• Using TOGAF to define and
• Architecture Compliance
Govern SOAs
• Architecture Principles
•Architecture Contracts
• Architecture Stakeholder
Architecture Capability
 PART I - Introduction • Architecture
Management Governance
Framework (Part VI)
• Architecture Patterns
• •Architecture Maturity
Business Scenarios
 PART II - Architecture Development Method • Gap Analysis
Models
 Part III - ADM Guidelines and Techniques • • Migration
ContentPlanning Techniques
Metamodel
• Interoperability
•Architecture Requirements
Skills
Architectural
• • Business Artifacts
Transformation
 Part IV – Architecture Content Framework Architecture Development Architectural
• Framework
Enterprise
• Readiness Continuum
Assessment
Method (Part II) • • Risk Management Partitioning
Deliverables
Architecture
 Part V – Enterprise Continuum & Tools • • Capability-Based
ArchitecturePlanning
Building Blocks Repository
ADM Guidelines and • Technical Reference
Techniques (Part III) • Tools for Architecture
 Part VI – Architecture Capability Framework Model (TRM)
Development
 TOGAF Reference Models (TOGAF Library) Architecture
• Integrated Information
Content
Framework Infrastructure
(Part IV) Reference Model
• (III-RM)
Enterprise Continuum and
Tools (Part V)

TOGAF Reference
Model (TOGAF Library)
27

27

What is Architecture in the Context of

TOGAF?
In TOGAF, “architecture” has two meanings depending upon
the context:
1. A formal description of a system, or a detailed plan of the
system at a component level to guide its implementation.
2. The structure of components, their inter-relationships,
and the principles and guidelines governing their design and
evolution over time.

28
 7/09/2020

The TOGAF Standard, Version 9.2

Table of Contents Part I - Introduction
Preface, Executive Overview, Core Concepts, Definitions

Part II – Architecture Development Method

Introduction to ADM
ADM Phase Narratives
Part III – ADM Guidelines and Techniques
Guidelines for Adapting the ADM Process
Techniques for Architecture Development
Part IV – Architecture Content Framework
Content Metamodel
Architectural Artifacts
Architecture Deliverables
Building Blocks
Part V – Enterprise Continuum and Tools
Enterprise Continuum
Architecture Partitioning
Architecture Repository
Tools for Architecture Development
Part VI – Architecture Capability Framework
Architecture Board
Architecture Compliance
Architecture Contracts
Architecture Governance
Architecture Maturity Models
Architecture Skills Framework

29

TOGAF Components
 Architecture Development Method (ADM)
 An iterative sequence of steps to develop an enterprise-wide architecture

 ADM Guidelines and Techniques

 Guidelines and techniques to support the application of the ADM
 Architecture Content Framework
 A detailed model of architectural work products, including deliverables, artifacts within
deliverables, and the Architecture Building Blocks (ABBs) that deliverables represent.

 The Enterprise Continuum

 A model for structuring a virtual repository and methods for classifying architecture
and solution artifacts

 The Architecture Capability Framework

 A structured definition of the organisations, skills, roles and responsibilities to establish
and operate an Enterprise Architecture.
 The TOGAF Library
 A supporting element separate to the Standard
 A reference library containing guidelines, templates, patterns, and other forms of
reference material to accelerate the creation of new Enterprise Architectures.

30
 7/09/2020

Modular Structure
Content Framework
Extended Guidance
TOGAF Capability Framework Architectural Styles
Additional ADM detail

Informs the Sets targets, KPIs,

capability Architecture Capability budgets for
Framework (Part VI) architecture roles
Ensures Realization
Drives need for
of Business Vision Architecture Capability
maturity

Business needs Architecture Development Delivers new

feed into method Method (Part II) business solutions

Business ADM Guidelines &

Refines Business
Vision and Techniques (Part III)
Understanding Capabilities
Drivers
TOGAF ADM &
Architecture Content Framework
Content Framework
(Part IV)

Enterprise Continuum &

Tools (Part V)
Informs the Business Operational changes
TOGAF Reference cause updates
of the current state
Materials (TOGAF Library)
TOGAF Enterprise
Continuum & Tools

31

Structure of TOGAF
Needs of the business shape non-architectural aspects of business operation

Sets, targets, KPIs, plans and

Informs the size, structure, budgets for architecture roles
and culture of the capability
Architecture Capability
Framework (Part VII)
Effective operations of the Business capability drives the
Architecture capability ensures Introduction need for Architecture Capability
realization of the Business Vision
(Part I) Maturity
Business Vision and Drivers

The Architecture Capability

Business Capabilities

operates a method
Business need feeds into the
method, identifying problems Architecture Development
to be addressed Method (Part II)

ADM Guidelines and The method delivers new

The method refines the business solutions
understanding of business need Techniques (Part III)

Architecture
The method Produces content to be Content TOGAF ADM and
stored in the Repository classified Content Framework
Framework
according to the Enterprise continuum
(Part IV)

Enterprise Continuum and

The Enterprise Continuum and Tools (Part V) Operational Changes update the
Repository inform the business Enterprise Continuum &
of current state Repository
TOGAF Reference
Model (Part VI)

32
Learning From business operation creates new business need

32
 7/09/2020

Structure Of the Standard

33

What is an Enterprise?
• A collection of organisations that share a common set of goals
o Government agency
o Part of a corporation
o Corporation
• Large corporations may comprise multiple enterprises
• May be an “extended enterprise” including partners, suppliers and
customers

What is an Architecture?
• An Architecture is the fundamental concepts or properties of a
system in its environment embodied in:
o its elements
o their relationships to each other and the environment
o and the principles governing its design and evolution

34
 7/09/2020

Exercise -1
What is Enterprise Architecture?

35

35

Architecture Types

Business
Architecture

Application Data
Architecture Architecture

Technology
Architecture

36
 7/09/2020

Classify your existing role

 Participants should map their existing roles and responsibilities to

Architecture types among the following:
 Business Architecture
 Application Architecture
 Data Architecture
 Technology Architecture

A short note on the mapping reasons.

If your roles maps to multiple domains, specify it.
Time- 5 mins.
37

37

Why do we need EA Practise..?

 Lets Understand…!!!!!!!!!!

38
 7/09/2020

Why Enterprise Architecture?

 Effective management and exploitation of information and Digital Transformation
are key to business success
 Good information management = competitive advantage
 Current IT systems do not really meet the needs of business
 Fragmented, duplicated
 Poorly understood
 Not responsive to change
 Investment in Information Technology
 Focussed on system maintenance
 Tactical developments rather than a strategic plan
 Two key reasons why you need an Enterprise Architecture:
 A means to achieve competitive advantage
 Enables managed innovation within the enterprise

39

Pressure to Develop Enterprise

Architecture
 Laws and regulations
 Clinger-Cohen Act (US Information Technology Management Reform
Act 1996)
 EU Directives on the Award of Public Contracts
 Sarbanes-Oxley
 More extended enterprises
 More co-operative IT operations
 Greater publicity to failures
 Increase in litigation
 Audit requirements

40
 7/09/2020

Business Benefits of Enterprise

Architecture
 It helps an organisation achieve its business strategy
 Faster time to market for new innovations and capabilities
 More consistent business processes and information across business units
 More reliability and security, less risk
 A more efficient business operation
 A more efficient IT operation
 Better return on existing investment,
 Reduced risk for future investment
 Faster, simpler, and cheaper procurement

Source: “Why Enterprise Architecture Matters?”, The Open Group White Paper, W076

41

The Importance of Governance

Governance = The way in which decisions are made

Who is responsible? Who is involved? Who is accountable?

 An Enterprise
Architecture is only as
good as the decision
making framework that
is established around it
 ”governance”
framework
 The Governance
Framework depends on
 Clear authority
structure
 The right participants

42
 7/09/2020

What is an Architecture Framework?

 TOGAF Standard Definition: Architecture Framework

 A conceptual structure used to develop, implement, govern, and sustain an

architecture

 It should describe a method for designing 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

The Value of a Framework

 Provides a practical starting point for an Architecture Project

 Avoids the initial panic when the scale of the task becomes apparent

 Systematic – “Codified common sense”

 Captures what others have found to work in real life

 Contains a Baseline set of resources for reuse

43

Break for 2 mins

 Digest the intro and basics covered

44
 7/09/2020

Part I
Definitions, Core Concepts

45

45

Definitions

46

46
 7/09/2020

Key Terms
 Activity: A task or collection of tasks that support the functions of an organization; for
example, a user entering data into an IT system or traveling to visit customers.
 Application :A deployed and operational IT system that supports business functions and
services; for example, a payroll. Applications use data and are supported by multiple
technology components but are distinct from the technology components that support
the application.
 Application Architecture : A description of the major logical grouping of capabilities
that manage the data objects necessary to process the data and support the business.
 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.
 Architecture Building Block (ABB) :A constituent of the architecture model that
describes a single aspect of the overall model.
 Business Architecture :The business strategy, governance, organization, and key
business processes information, as well as the interaction between these concepts.
 Architecture Principles :A qualitative statement of intent that should be met by the
architecture. Has at least a supporting rationale and a measure of importance. 47

47

Key Terms
 Architecture Continuum :A part of the Enterprise Continuum. A repository of
architectural elements with increasing detail and specialization. This Continuum begins
with foundational definitions such as reference models, core strategies, and basic
building blocks. From there it spans to Industry Architectures and all the way to an
organization’s specific architecture.
 Architecture Development Method (ADM) :The core of TOGAF. A step-by-step approach
to develop and use an enterprise architecture.
 Architecture Domain :The architectural area being considered. There are four
architecture domains within TOGAF: Business, Data, Application, and Technology.
 Architecture Framework :A foundational structure, or set of structures, which can be
used for developing a broad range of different architectures. It should contain a method
for designing an information system 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.

48

48
 7/09/2020

Key Terms
 Architecture View : A view is a representation of a system from the perspective of a
related set of concerns. A view is what you see (or what a stakeholder sees). Views are
specific.
 Architecture Viewpoint: where you are looking from; the vantage point or perspective.
Viewpoints are generic. A model (or description) of the information contained in a view.
 Architecture Vision : A high-level, aspirational view of the Target Architecture. / A
phase in the ADM which delivers understanding and definition of the Architecture Vision
/Level of granularity of work to be done.
 Baseline :A specification that has been formally reviewed and agreed upon, that
thereafter serves as the basis for further development or change and that can be
changed only through formal change control procedures or a type of procedure such as
configuration management.
 Baseline Architecture :The existing defined system architecture before entering a
cycle of architecture review and redesign.

49

49

Key Terms
 Business Governance :Concerned with ensuring that the business processes and policies
(& their operation) deliver the business outcomes & adhere to relevant business
regulation.
 Capability :An ability that an organization, person, or system possesses. Capabilities are
typically expressed in general and high-level terms and typically require a combination of
organization, people, processes, and technology to achieve; or example, marketing,
customer contact, or outbound telemarketing.
 Concerns :The key interests that are crucially important to the stakeholders in a system,
and determine the acceptability of the system. Concerns may pertain to any aspect of the
system’s functioning, development, or operation, including considerations such as
performance, reliability, security, distribution, and evaluability. Longer lasting than
problem (eg. state of the economy), not a requirement, which is short term.
 Constraint: An external factor that prevents an organization from pursuing particular
approaches to meet its goals. For example, customer data is not harmonized within the
organization, regionally or nationally, constraining the organization's ability to offer
effective customer service.
 Enterprise: The highest level (typically) of description of an organization and typically
50
covers all missions and functions. An enterprise will often span multiple organizations.

50
 7/09/2020

Key Terms
 Enterprise Continuum A categorization mechanism useful for classifying architecture
and solution artifacts, both internal and external to the Architecture Repository, as they
evolve from generic Foundation Architectures to Organization-Specific Architectures.
 Foundation Architecture Generic building blocks, their inter-relationships with other
building blocks, combined with the principles and guidelines that provide a foundation
on which more specific architectures can be built.
 Framework A structure for content or process that can be used as a tool to structure
thinking, ensuring consistency and completeness.
 Repository A system that manages all of the data of an enterprise, including data and
process models and other enterprise information. Hence, the data in a repository is
much more extensive than that in a data dictionary, which generally defines only the
data making up a database
 Segment Architecture A detailed, formal description of areas within an enterprise,
used at the program or portfolio level to organize and align change activity.
 Solution Building Block (SBB) A candidate solution which conforms to the specification
of an Architecture Building Block (ABB).
51

51

Key Terms
 Solutions Continuum A part of the Enterprise Continuum. A repository of re-usable
solutions for future implementation efforts. It contains implementations of the
corresponding definitions in the Architecture Continuum.
 Standards Information Base (SIB) A database of standards that can be used to define
the particular services and other components of an Organization-Specific Architecture.
 Taxonomy of Architecture Views The organized collection of all views pertinent to an
architecture.
 View The representation of a related set of concerns. A view is what is seen from a
viewpoint. An architecture view may be represented by a model to demonstrate to
stakeholders their areas of interest in the architecture. A view does not have to be visual
or graphical in nature.
 Viewpoint A definition of the perspective from which a view is taken. It is a
specification of the conventions for constructing and using a view (often by means of an
appropriate schema or template). A view is what you see; a viewpoint is where you are
looking from - the vantage point or perspective that determines what you see.
 A "pattern" has been defined as: "an idea that has been useful in one practical context
and will probably be useful in others" [Analysis Patterns - Re-usable Object Models].
52

52
 7/09/2020

Task for Delegates

 Digest the Terms

 Relate them to your existing projects/ Roles & Responsibilities / EA exposure.
 10 mins exercise to note all terms you can relate to.

53

Level 1 Learning Units

 Basic Concepts
 Core Concepts
 General Definitions
 Introduction to the ADM
 Enterprise Continuum and Tools
 ADM Phases (Level 1)
 ADM Guidelines and Techniques
 Architecture Governance (Level 1)
 Architecture Views, Viewpoints and Stakeholders
 Building Blocks
 ADM Deliverables (Level 1)
 TOGAF Reference Models (Level 1)
 TOGAF Certification Program

54
 7/09/2020

Core Concepts

 What is TOGAF?
 TOGAF document layout
 Architecture domains
 First look at the ADM
 Versioning convention
 The architectural landscape
 Architecture Content Framework
 Enterprise Continuum
 TOGAF reference models
 Capability Framework

55

What is TOGAF®?

 TOGAF, an Open Group Standard:

 A proven enterprise architecture methodology and framework used by the world's
leading organizations to improve business efficiency
 The most prominent and reliable enterprise architecture standard, ensuring
consistent standards, methods, and communication among enterprise architecture
professionals
 Enterprise architecture professionals fluent in TOGAF standards enjoy greater
industry credibility, job effectiveness, and career opportunities
 TOGAF helps practitioners avoid being locked into proprietary methods, utilize
resources more efficiently and effectively, and realize a greater return on
investment

56

56
 7/09/2020

Core Concepts
Deliverables
Whatproducts
Formal is TOGAF?
•The Architecture
 What isspecified
TOGAF? Metamodel describes the organizationally tailored application of an
Contractually
architecture
Architecture
Outputs from a framework,
Development
project including
Method a metamodel
(ADM) for architecture content.
TOGAF is Capability
an architecture framework.

A•TheWhat is
canArchitecture
Architecture
deliverable in the
contain many artifacts Context
defines of TOGAF
TOGAF?provides
the parameters, theand
structures, methods and that
processes
support tools for
Deliverables, assisting
Artifacts,
governance in
of theand the acceptance,
Architecture production, use, and maintenance
Repository.
 What
Building
Building
•The ofKind
blocks an enterprise
Blocks
Architecture architecture.
of Architecture
Landscape is DoesIt TOGAF
is basedDeal
onrepresentation
the architectural an iterative process
With? model
of assets deployed
componentssupported by best practices
that can be combined with and a re-usable set ofThe
existing architecture
within
 the operating
Enterprise
otherArchitecture
building Continuum
blocks enterprise
to Development
deliver at aMethod
architecturesparticular point in time. landscape is likely to
exist assets.
at multiple levels of abstraction to suit different architecture objectives.
and solutions
Architecture

•The Deliverables,
Standards Repository
Artifacts, Base
Information and Building Blocksthe standards with which new
(SIB) captures
architectures
Artifacts must comply, which may include industry standards, selected products
Establishing and Maintaining
and Enterprise
 fine
services from Continuum
grained products suppliers, or shared
that describe an services already deployed within the
anarchitecture
Enterprise Architecture
from a specific viewpoint
organization.
Capability
Architecture
 For Repository
example: use-case specifications,
•The Reference
architectural Library provides
requirements, network guidelines, templates, patterns, and other forms of
Establishing
 diagrams,
reference material
etc. and
thatMaintaining an Enterprise
can be leveraged in order to Architecture
accelerate the creation of new
Classified as: for the enterprise.
architectures
•TheCapability
Catalogs (lists of things),
Governance
Matrices (showing Log provides a record of governance activity across the enterprise.
relationships
between things) or
Diagrams (pictures of things).
Artifacts make up the content of the 57

Architecture Repository

57

Architecture Domains
Domain Covers …
Business Business strategy, governance, organisation, key
Architecture business processes

Data Structure of the organisation’s logical and physical data

Architecture assets
Data management resources
Application A blueprint for the individual application systems to be
Architecture deployed, their interactions, their relationships to the
core business processes of the organisation
Technology The software & hardware capabilities that are required
Architecture to support the deployment of the other three
architectures includes IT infrastructure, middleware,
networks, communications, processing, standards

58
 7/09/2020

The Architecture
Development Method
 The core of TOGAF
 A proven way of developing an
architecture
 Designed to address business
requirements
 An iterative method
 A set of architecture views to
ensure that a complex set of
requirements are adequately
addressed
 Each phase includes
objectives, approach, inputs,
steps and outputs

59

How the ADM Phases Interact

Enterprise Architecture Capability:
Forming the EA Team and the AGB

Enterprise Capability:
Architecture Governance: Project Establishment
Monitoring & oversight of Planning the Architecture Definition
implementation projects project

Architecture Development:
Change Requests
Creation and evolution of
Implementation architecture content by
Projects Architectural Contract
cycling through Phases B, C,
Assessments/ Reviews and D

Transition Planning:
Creation of formal change
roadmaps planning the
Implementation

60
 7/09/2020

Architecture Capability Architecture

iterations support Development iterations
Applying Iteration to the ADM
creation and evolution support creation and
of the Architecture evolution of architecture
Capability content by cycling
through Phases B, C, and
D

Architecture Governance
iterations support
governance of change
activity
As iterations converge on a
Transition Planning target, extensions into
iterations support the Phases E & F ensure the
creation of formal change viability of implementation
roadmaps is considered

61

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).

62
 7/09/2020

Guidelines
 Guidelines for Adapting the ADM Process
 Ways to apply iteration to the ADM,
 Applying the ADM at different levels of the
enterprise,
 Security considerations for the different
phases and
 Supporting SOA (Service Orientated
Architecture)

63

Techniques
 Techniques for Architecture Development,
 Architecture Principles
 Stakeholder Management
 Architecture Patterns
 Business Scenarios
 Gap Analysis
 Migration Planning Techniques
 Interoperability Requirements
 Business Transformation Readiness Assessment
 Risk Management
 Capability-Based Planning

64
 7/09/2020

Versioning convention

 Version 0.1
 Indicates a high-level outline of the architecture is in place
 Version1.0
 Indicates a formally reviewed detailed architecture

65

Applying the ADM across Architecture

Landscape Strategic Architecture provides
an organizing framework for
The following characteristics can be used operational and change activity
and allows for direction setting
to organize the Architecture Landscape
at an executive level
• Breadth (subject matter) Segment Architecture provides
• Depth an organizing framework for
operational and change activity
• Time and allows for direction setting
• Recency and the development of
effective architecture roadmaps
at a program or portfolio level

Capability Architecture provides

an organizing framework for
change activity and the
development of effective
architecture roadmaps realizing
capability increments

66
 7/09/2020

Applying the ADM

Across the Architecture Landscape

Example Guideline

67

Case Study Exercise

Architecture Landscape
Exercise #2

68
 7/09/2020

Case Study
Exercise
Architecture Landscape
Time frame - 15 mins
Discussion - 15 mins

69