TOGAF With ArchiMate Concepts

Avancier
Harmonising two conceptual

frameworks for EA
Mapping TOGAF® to ArchiMate®
AKA Terminology Torture
Including some slides from Avancier’s training to

BCS Enterprise and Solution Architecture Certificates
Copyright © Avancier Ltd, http://avancier.website
Copyright Avancier Ltd 2018

What do we want for EA?
Avancier
► What is needed for the ► Processes

architectural design and ► Products
planning of large-scale ► People
changes to business systems?

Processes and products
Avancier
► TOGAF best known for its process

■ the Architecture Development Method (ADM)
► Also offers a menu of lightly-defined products
■ Deliverables
■ Artifacts
● Catalogs
● Matrices
● Diagrams
► ArchiMate more limited
■ a modelling language
for drawing diagrams
► A perfect marriage?

TOGAF 9.2 artifact types – diagram types in the handout
Avancier
PRELIMINARY VISION REQUIREMENTS PLANNING
Principles Catalog Stakeholder Catalog Requirements Catalog Project Context Diagram
Driver/Goal/Objective Catalog Solution Concept Diagram Requirements Traceability Matrix Benefits Diagram
Value Chain Diagram Business Footprint Diagram
Business Model Diagram
BUSINESS
Capability view People view Process view Business data view
Goal/Objective/Service Diagram Organization Decomposition Diagram Process Catalog Conceptual Data Diagram
Contract Measure Catalog Function/Organization Matrix Business Use Case Diagram Data Entity/Business Function Matrix
Functional Decomposition Diagram Role Catalog Process Flow Diagram Business Service/Information Dgrrm
Business Service/Function Catalog Organization/Role Catalog Event Diagram
Business Interaction Matrix Actor/Role Matrix Product Lifecycle Diagram
Node Connectivity Diagram Location Catalog
Business Capabilities Catalog Organization Map Value Stream (Stages) Catalog

Strategy/Capability Matrix Capability/Organization Matrix Value Stream/Capability Matrix Parallel vocabulary and artifacts
Business Capability Map Value Stream Map
DATA APPLICATIONS TECHNOLOGY IMPLEMENTATION
Data Entity/Data Component Catalog Application Portfolio Catalog Technology Portfolio Catalog Software Engineering Diagram
Application/Data Matrix Interface Catalog Technology Standards Catalog Software Distribution Diagram
Logical Data Diagram Application/Func/Org/Role Matriices Application/Technology Matrix Enteprise Manageability Diagram
Data Dissemination Diagram Information Exchange Matrix Environment Locations Diagram Processing Diagram
Data Security Diagram Application Communication Diagram Platform Decomposition Diagram Networked Computing Hardware Dgrm
Data Migration Diagram Process Application Realization Diagram Communications Engineering Dgrm
Data Lifecycle Diagram Application and User Locations Diagram
Application Use Case Diagram
Application Migration Diagram

ArchiMate diagram symbols
Avancier

This presentation
Avancier
► Not about diagrams! ► Rather, about the concepts in

► See the handout for examples the diagrams
► Because communication
requires that
■ Speakers and hearers share an
understanding of the concepts
spoken words represent.
■ Drawers and readers share an
the diagrams symbols
represent.

The perfect marriage?
Avancier
► The bride and groom come from

different families, with different
cultures.
► ArchiMate ► TOGAF
■ tries to present a coherent and ■ tends to embrace all words and
consistent conceptual framework concepts its authors have found useful
■ using a tightly controlled in practice.
language. ■ leading to incoherence
■ e.g. new authors undermined
● “Building Block” and “Service” in v 9
● “Function” in v9.2

Nevertheless
Avancier
► If you know the history of TOGAF, you can find a coherent

conceptual framework in it
► This presentation compares and contrasts

■ the conceptual framework of TOGAF
■ the conceptual framework of ArchiMate.

The initial direction to EA
Avancier
1. The initial direction to EA

2. What is a business system?
3. Service-orientation in the TOGAF standard
4. Abstraction in TOGAF
5. The generic meta model that underpins ArchiMate
6. Mapping terms in the two standards
7. What is the function/process distinction?
8. Data architecture in TOGAF
9. Mapping the concepts to TOGAF artifacts
10. An alternative Business Architecture approach

Motivations and context for EA
Avancier
► “Business planning at the strategy level provides the initial direction

to Enterprise Architecture”. (Ch. 5)
Business
Direction

Business direction words used in TOGAF 9.2
Avancier
Business Mission Business

Driver Statement Vision
Business
Goal Strategy
Principle
Objective
Business
Direction

In the OMG’s Business Motivation Model
Avancier
► TOGAF’s Principles are “Directives”
► TOGAF’s Goals and Objectives are Contents of “Business Direction” in TOGAF 9.2
“Desired results”
Business Mission Business
Driver Statement Vision
► “Course of action” is a plan, high or low
level, to achieve those desired results.
Directive Desired Result Course of Action
Business
Goal Strategy
Principle
Objective
A business strategy document

may include principles, drivers
and goals, along with very high
level plans or road maps.

Adding more words
Avancier
“Means” and “End” words in the Business Business

Direction
Motivation Model from the OMG
Contents of “Business Direction” in TOGAF 9.2
Business Mission
Mission Vision Business Vision
Driver Statement
Directive Desired Result Course of action Directive Desired Result Course of Action
Business
Goal Strategy Goal Strategy
Principle
Business Business
Objective Tactic Objective Project
Policy Policy
Business Business Architecture

Work Package
Rule Rule Requirement

ArchiMate has symbols for some of these words (and more)
Avancier
Driver Goal
Business Mission
Business Vision
Driver Statement
Principle Requirement
Directive Desired Result Course of Action
!
Business
Goal Strategy
Principle
!
Course of Action Business
Objective Project
Policy
!
Business Architecture
Work Package
Rule Requirement
Work Package

TOGAF’s primary Business Direction artifact
Avancier
Driver
Stimulate
BMM
Goal Desired Result
Driver/Goal/Objective catalog
Decomposed into
“a cross-organizational reference... Objective

a definitive breakdown of drivers, goals,
and objectives... Met by
to identify synergies across the Organization

organization” Unit

What is a business system?
Avancier


From business planning to business system planning
Avancier
► “EA structures the business planning into an integrated framework that

regards the enterprise as a system or system of systems.” (Ch. 5)
EA is about business system planning.
Business
Direction

What is a business system?
Avancier
► One or more business operations that we can model as
► A discrete event-driven system in which

■ events trigger
■ active structures (actors) to perform
■ behaviors (repeatable activities )

Active structures
Avancier
► Active structures ► Subsystems or components

■ Actor that can be encapsulated by
■ Organisation unit the services they perform, in
■ Component response to events.
■ Module
■ Node Service Bar Person Barperson services
Portfolio Services • Serve customer
• Take Order
Realized by Realized by
• Serve Product
• Take Payment
• Open doors
• Close doors
Active
Bar Person • Clean up
Structure

Service
Avancier
► A behavior exposed at the interface of a

system or component.
Found in Service
Service
Portfolio
► It may Realized by
■ update the internal state of the system

● “add value” to an artifact or activity.
Active
■ consume and produce I/O flows Structure
● flows of data and sometimes materials

A service is definable by a contract
Avancier
► A service contract comprises

■ Name
Found in Service
■ Inputs Service
Portfolio
■ Outputs Realized by
■ Rules
■ Quality measures
Active
Structure

Services encapsulate processes
Avancier
► one or more processes are needed to

complete a service.
Found in Service
Service
Portfolio
Realized by
Process flow Realize
● A sequence of sub processes (stages, steps or activities) Active

Process
Perform Structure
● Terminates in the production of a flow or other result of value.
Initiate Discuss Configure Verify Price Confirm Place Capture

sale needs products delivery order order Order signature

Behaviors cannot perform behaviors!
Avancier
► Two behaviors can collaborate

■ one can invoke the other.
Sales Discuss Configure Verify Price order

► A behavior cannot perform another
Actor needs products delivery
behavior; you need an
Supply Confirm ■ actor to perform an activity (aka)
Actor availability
■ active structure to perform a behavior
Delivery Assign
resources
Actor

A passive structure
Avancier
► A structure that does not act, but is acted on.

► It can be a material or data structure.
Found in Service
Service
Portfolio
Realized by
Realize
Passive Active
Process
Structure Acts on Perform Structure

Data entities and components in TOGAF
Avancier
IS Found in Service
Service Portfolio
Realized by
Data entity Realize
– A unit of data recognized by a Data Application

domain expert Entity Create & Use Perform Component
– identified with a thing or concept Held in
of importance in their domain,

– part of a data component. Data
Component
Data component
– A data structure composed of data entities

Business objects in ArchiMate
Avancier
► Business Object
■ a material thing?
Business Accessed via Business
■ a data representation of it? Service Interface
■ a data sent/received in a data flow
■ a data entity created/used in a data store?
■ any of the above? Realizes
Business
Business Business Role
Process or
Object Accesses Assigned to or Actor
Interaction
► ArchiMate standard example suggests

■ a logical data flow, containing a data structure, which may be
■ conveyed in different physical forms

Service-orientation in the TOGAF standard
Avancier


The Open Group’s general principle
Avancier
► Standards should be based on AutoXpress Services

“executable specification”. Fit tyres
Check-up and oil change
Service AutoXpress Full annual service
► Specify a system by defining Portfolio Services Check brakes
the behaviors it is required to Realized by Realized by Repair brakes
perform, and their results. Check exhaust
Replace exhaust
Inspect battery
► TOGAF applies this principle to Business
AutoXpress
Replace battery
System Align wheels
the specification of business
Replace windscreen wipers
systems as well as IT systems. Fit bulbs
Replace shock absorbers

The unit of behavior - a service
Avancier
► a required behavior or unit of work AutoXpress Services

Fit tyres
Check-up and oil change
► defined as a service requester sees it. Full annual service
■ hides how a system works. Check brakes
Repair brakes
Check exhaust
► may be short or long Replace exhaust
Inspect battery
■ depending on what the requester wants and the Replace battery
resources available to the service provider. Align wheels
Fit bulbs
► realised by one or more components Replace shock absorbers
performing one or more processes.

The unit of structure - a “building block” (or component)
Avancier
► a subsystem or actor of any kind,

including human and computer actors.
Business System
► may be coarse-grained or fine-grained
► can realise one or more services Building Block

Building
■ on its own or in collaboration with others Block
► can play the

Client
■ client role of service requester and/or
■ server role of service provider.
Server
& Client
Server

Service or Building Block? Which is bigger?
Avancier
► Services may be long or short

■ One long service (e.g. package delivery)
Business System
may require the participation of very
many BBs.
Building Block
Building
Block

The trouble with “building block” and “service”
Avancier
► Changes in successive versions of the

standard have left the terms ambiguous.
Business System
► In this presentation
► building block and component are

synonyms Building Block
Building
Block
► service is an external view of processes

Abstraction in TOGAF
Avancier


Abstraction in ArchiMate and TOGAF
Avancier
Delegator Composition Generalisation Idealisation

a client element a composite a generalised element an idealised
or aggregate element or logical element
server element(s) smaller or shorter elements particular subtypes “physical” features

Servant Decomposition Specialisation Realisation
Delegator Composition Generalisation Idealisation
Foundation Services
Business Enterprise
Common System Logical ABBs
Applications Segments
Industry Physical SBBs
Technologies Capabilities/Solutions
Organisation Deployed Solutions
Servant Decomposition Specialisation Realisation

Abstraction by generalisation of system description
Avancier
Generic TOGAF
Generic Universal Foundation
Common
Widespread Common
system
Domain
Parochial Industry
specific
Specific Unique Organisation
Specific

Abstraction by idealisation of system description
Common OMG MDA Zachman TOGAF
Avancier
Idealised description Contextual Goals &

Objectives
Computation Service
Conceptual Independent Conceptual Contracts
Model
Platform Architecture
Logical Independent Logical BBs
Model
Platform Solutions
Physical Specific Model Physical BBs
Executable
Artifact Configuration
Executable description
Realisation Executing Instantiation Deployed

Artifact Solutions
Realisation

TOGAF’s Enterprise Continuum
Avancier
Generalisation
Common
Foundation Industry Organisation
Idealisation system
Requirements and context

Service
Contracts
Architecture continuum
Architecture
BBs
Solution continuum
Solutions
BBs
Deployed solutions
Deployed
Solutions

Level of idealisation in TOGAF’s Enterprise Continuum
Avancier
Generalisation
Common
Foundation Industry Organisation
Idealisation system
Requirements and context Architecture Requirements Specification includes Business and

Service Application/IS Services contracts.
Contracts
Architecture continuum Logical Components are defined by the services they provide to each other
Architecture and to external entities, also by the abilities and data resources they need.
BBs
Solution continuum Physical Components are procurable; they can be hired, bought or built to
Solutions realise Logical Components, and so deliver the required Services.
BBs
Deployed solutions Real world components are employed or deployed to do work at run-time
Deployed (might be called Operational Components).
Solutions

The content framework is based on a generic relation
Avancier
Idealised description
Services
<are clustered and

assigned to>
Logical Components ► Logical: “An implementation-independent definition" ,

portable and supplier-neutral.
<are realised by>
Physical Components ► Physical: “A description of a real-world entity”, still

“considerably abstracted from implementation“.
<are instantiated as>
Deployed solutions
Realisation

TOGAF generic relation
Avancier
Logical ABBs Physical SBBs
<are clustered Logical Physical

Services <are realised by>
and assigned to> Components Components
Business
Business Organization
Service/ Function Functions
Services Units
catalog
Role catalog +
Activities Roles Actors
Actor/Role matrix
Logical Physical
Application
IS Services Application Application
portfolio catalog
Components Components
Logical Physical
Technology Technology
Technology Technology
portfolio catalog Services
Components Components

The service to component relationship
Avancier
► TOGAF encourages architects

► to assign the responsibility for one service to one component and
► to minimise duplication of service provision by different components.
N Business Services <are clustered and assigned to> 1 Function

1 Logical Application
N IS Services <are clustered and assigned to>
Component
1 Logical Technology
N Technology Services <are clustered and assigned to>
Components
► However, a component can delegate work to other components. So,

► one component may perform many services, and
► one service may be performed by many components.

The logical component to physical component relationship
Avancier
► In the application and technology domains, the ideal is a 1-to1 relation

IDEALLY
1 Logical Application Component 1 Logical Application Component
<realised by>
IDEALLY
1 Logical Technology Components Logical Technology Component1
<realised by>
► In practice, the relationships may be more complex, or logical

components may be reverse-engineered to keep the relationship simple.
► In the business domain, there are artifacts to capture the many-to-many

logical-to-physical relationship .
Function/Organization matrix N Functions <are realised by> N Organization Units

Actor/Role matrix N Roles <are realised by> N Actors

The Logical/Physical distinction in the business domain
Avancier
Goal/
Objective
Business
Service
Business Component
Or Package of Capability
►Functions are logical Function Role ►Roles are logical Actors

organization units Realized by Realized by
►Organization units Organization ►Actors realize Roles

Actor
realize Functions Unit

The Logical/Physical distinction in other domains
Avancier
►Strictly, Architecture BBs don’t perform Processes or deliver Services.

►They specify Solution BBs that can do those things, and realize the Architecture BBs
Goal/
Objective
Business IS Technology
Data Entity
Service Service Service
Business Component Application Data Component Technology

Process
Or Package of Capability Component Component
Logical App Logical Data Logical Tech

Function Role
Component Component Component
Realized Realized Realized Realized Realized
by by by by by
Organization Physical App Physical Data Physical Tech

Actor
Unit Component Component Component

The general approach in TOGAF
Avancier
Baseline analysis abstracts performed services from building blocks
Identify performed Services Study Physical SBBs
Target design starts from the required services
Map Logical ABBs

Identify Goals and Objectives Identify Required Services Map Services to Logical ABBs
to Physical SBBa
Map Functions
Business Define Business Services Map Services to Functions
to Organization Units
Map Data Entities to Logical Data Map Logical Data Components to

Data Define Data Entities
Components Physical ones
Map Services to Map Logical App Components

Apps Define IS Services
Logical App Components to Physical ones
Map Services to Logical Technology Map Logical Tech Components to

Technology Define Technology Services
Components Physical ones

The generic meta model that underpins ArchiMate
Avancier


ArchiMate generic meta model
Avancier
Behaviour Structure
what the system does what the system is made of
External
requirements of
external entities
Internal
the workings of
the system

ArchiMate generic meta model - simplified
Avancier
Behaviour Structure
what the system does what the system is made of
Service: an explicitly defined exposed behavior Interface: a point of access where one or more
External services are provided to the environment
requirements of
external entities Accessed via Service
Service
Portfolio
Data
Realizes
Process or
Component
Accesses Interaction Assigned to
Internal
the workings of
the system A unit of activity performed by one or more An entity that is capable of performing behavior
active structure elements (e.g. process). (e.g. component).

Recursive architecture description
Avancier
► Both building blocks and services are

recursively composed
Business System
► One building block perform many
services
► One service may require many Building Block

building blocks (be they nested or Building
Block
sequential).

Mapping terms in the two standards
Avancier


Mapping ArchiMate to General System Theory
Avancier
Passive Structure Behavior Active Structure GST
Found in Service
Service
Service Service Portfolio
External
Portfolio
Realized by
Deliver
Data Entity
An encapsulated
Data Create & Use
Entity
Process
Process
Perform
Architecture Building Block
Component
Solution Building Block package of Internal
capability
Passive Structure Behavior Active Structure ARCHIMATE
Found in
Service Interface External
Realized by
Deliver
An encapsulated
Passive Process OR Active
Structure Act on Function Perform Structure
package of
capability
Internal

Mapping TOGAF to ArchiMate
Avancier
Passive Structure Behavior Active Structure TOGAF
Found in Service
Service
External
Portfolio
Assigned to
Architecture A logical
Building specification
Logical
Deliver
Block of below
Data
Data Entity
Create & Use Realized by
Entity
Process
Process
Internal
Solution An encapsulated
Building package of
Perform
Block capability
Physical
Passive Structure Behavior Active Structure ARCHIMATE
Found in
Service Interface External
Realized by
Deliver
An encapsulated
Passive Process OR Active
Structure Act on Function Perform Structure
package of
capability
Internal

Putting Function in its rightful place
Avancier
Passive Structure Behavior Active Structure TOGAF
Found in Service
Service
External
Portfolio
Assigned to
Function A logical
Logical
OR Role specification
Deliver
of below
Data
Data Entity
Create & Use Realized by
Entity
Process
Process
Internal
An encapsulated
Organization
package of
Perform unit OR Actor capability
Physical
► ArchiMate’s structure/behavior distinction is peculiar

► The standard examples and users often apply the Function symbol to a Process
(which can confuse, since Functions are more like Roles than Processes).

Mapping ArchiMate to TOGAF
Avancier
►Label Logical Components using ArchiMate’s “Function” symbol?

Business App Technology
Business Component Application Node

Component
Application Technology
Function Role
Function ??? Function ???
Realized by Realized by Realized by Realized by
App
Actor (Org) Actor Node
Component
►OK. Provided this caveat is understood

● ArchiMate standard and users use the Function symbol for a Process instead
● Logical components in TOGAF (defined by service portfolios) might be seen as
closer to ArchiMate’s Interface.

Mapping ArchiMate to TOGAF
Avancier
Business IS Technology
Service
TOGAF Uses
Service
Create and use
Data Entity
Service
Realized Realized Held in Realized
by by by
Business Component Process Application Data Component Technology

Component Component
Logical App Logical Data Logical Tech
Function Role Perform Component Maintain Component Component
Realized by Realized by Realized by Realized by Realized by
Organization Physical App Physical Data Physical Tech

Actor
Unit Component Component Component
Business App Technology

ArchiMate Data Object
Business Component Process Application Data Object Node

Component
Application Technology
Function Role Data Object
Function Function
Realized by Realized by Realized by Realized by Realized by
Actor Actor App Component Data Object Node

Terminology torture – aargh!
Avancier
Behavior Physical Active

Generic Logical Active Structures
Units Structures
Human Activities Roles Actors
TOGAF Services Logical Components Physical Components
UML Operations Interfaces or Services Components
WSDL Operations Web Services Components
Fashion Operations APIs MicroServices

What is the function/process distinction?
Avancier


A 3 level Functional Decomposition Structure
Avancier
Strategic management functions
Fiscal and Risk and

Strategy Performance
accounting Compliance
Operational functions
Products Marketing Sales Customer care
Product Market Distribution Customer Customer

definition development channels service relations
Product
Campaigning Sakes execution Service channel Customer data
engineering
Assets Money Claims

Investment Contracts
Investment Banking Accounts Claim settlement
performance life cycle
Investment
Asset inventory Cash flow Money market Contract admin. Claim admin.
portfolio
Support functions
Organization HR Process Office Facility ITSM
This diagram uses ArchiMate symbols

A process – sequencing atomic activities in a flow
Avancier
Sales
roles
Salesman Customer
Sales
Initiate Discuss Configure Verify Price Confirm Place Capture
function sale needs products delivery order order Order signature
Supply Confirm
availability
function of stock
Delivery Assign
resources
function

Mapping atomic activities to 2nd level nodes of a functional decomposition
Avancier
Strategic Vision and Strategy Finance Product Design Operations
management
functions
Sales & Marketing Supply Manufacture Delivery Customer Service

Advertise Select suppliers Assign resources
Identify prospect Purchase goods Deliver products
Initiate sale Receive goods Install products
Discuss needs Inspect goods
Operational Configure products Return goods
functions Verify delivery Despatch goods
Price order Confirm availability
Confirm order of stock
Place Order
Human Resources Accounts Facilities Knowledge ITSM

and Change
Support
functions
Legal

The Function/Process distinction
Avancier
Goal/
Objective
Business
Service
Deliver
Business Component
A function is a package Process
Function Role
of capability
Realized by Realized by
Perform
It can be bounded by a A process flows over time from
service portfolio Organization
start to end.
Actor
Unit It may be
► encapsulated by one service.
► one of several processes
needed to deliver one service.
► contribute to the delivery of
more than one service

Data architecture in TOGAF
Avancier


Data architecture in TOGAF
Avancier
► Data architecture is about

■ data at rest (in store)
■ data in motion (in flows).
► What TOGAF classifies under data architecture are artifacts that

record the creation and use of data entities in persistent data
components.
Data entity/data Data <are related Logical Data <are Physical Data
component catalog entities together in> Components realised by Components
► What about data flows?

The Flow concept implicit in TOGAF artifacts
Avancier
►Service
■ “can be defined in a logical service contract that
defines input and output flows and/or state changes.” Service
Found in Service
Portfolio
Realized by
►Flow
□ A movement of a data and/or material structure Realize
between sender and receiver components.

Process Component
Perform
● Q) What about flows that architects choose not

specify in service contracts?

Services v data flows in architecture artifacts
Avancier
► Different concepts, related, but difficult to combine in an artifact
Using ArchiMate symbols
Using ArchiMate symbols
Application Co-operation Viewpoint

Mapping the concepts to TOGAF artifacts
Avancier


Remember terminology torture
Avancier
Driver
Stimulate
BMM
Goal Desired
Result
Decomposed into
Objective
Met by
Business
► Cap Gemini call services building blocks Service
Delivered by
► Some call building blocks services Business Building Block

Function Role
Organization
Actor
Unit

A service-oriented view of business building blocks
Avancier
Driver
Stimulate
BMM
Goal Desired
Result
Decomposed into
Objective
Met by
Objectives Business
met by services Service
Delivered by
performed by components
Business Component
Function Role
Organization
Actor
Unit

The start of a Business Architecture artifact map
Avancier
Driver
Driver/Goal/Objective catalog
Stimulate
BMM
Goal Desired
Goal/Objective/Service diagram Result
Decomposed into
Objective
Contract Measure catalog
Met by
Business
Business Service/Function catalog Service
Delivered by
Business Component
Functional Decomposition diagram Or Package of Capability
Function Role
Function/Organization matrix
Organization
Actor
Organization Decomposition diagram Unit

A BA artifact map with Capability and Value Stream artifacts?
Avancier
Driver
Stimulate
BMM
Goal Desired
Result
Decomposed into
Objective
Met by
Strategy/Capability Map? Business

Service
Delivered by
Capability?
Business Capability Map?
Business
Role
Business Capability/ Capability?
Perform
Organization matrix? Realized by Realized Process
by
Organization
Actor
Unit Value Stream
Organization Map?
Capability/Organization matrix? Value stream / Capability matrix? Value stream catalog

Value stream map
A BA artifact map for TOGAF 9.1 and 9.2
Avancier
Driver
Stimulate
BMM
Driver/Goal/Objective catalog Goal Desired
Result
Decomposed into
Goal/Objective/Service diagram Objective
Met by
Business Interaction matrix
Business Information Exchange matrix
Business Service/Function catalog Service Node Connectivity diagram
Delivered by
Business Component
Or Package of Capability Role catalog
Functional Decomposition diagram Actor/Role matrix
Function Role
Perform
Realized by Realized by Process
Function/Organization matrix
Organization
Actor
Process catalog
Process Flow diagram
Organization/Actor catalog Event diagram

The same BA artifact map after some of the draft CRs
Avancier
Driver
Stimulate
BMM
Driver/Goal/Objective catalog Goal Desired
Result
Decomposed into
Goal/Objective/Service diagram Objective
Met by
Business Interaction matrix
Business Business Interaction diagram
Business Service/Function catalog Service Business Flow catalog
Delivered by
Business Component
Or Package of Capability Role catalog
Functional Decomposition diagram Actor/Role matrix
Function Role
Perform Create & Use Business
Realized by Realized by Process
Function/Organization matrix Data Entty
Business Data catalog
Organization Conceptual Data diagram
Actor
Process catalog
Organization/Role catalog Business Event diagram

A possible solution design sequence
Avancier
Driver Presuming the baseline organisation structure

Stimulate
and functional decomposition are a given
Driver/Goal/
Objective Goal
catalog
Decomposed into
Met by Business I/O

Objective
Flow
Produced &
Consumed by
Business Held in Logical Data Realized by Physical Data

Data Entity
Service Component Component
Goal/Objective/
Service diagram Delivered by
Create & use
Enter &
Retrieve Application I/O IS Provided by Logical App Realized by Physical App
Process Component Component
Process catalog Flow (Message) Service
Performed by Uses
Event diagram
Assigned to Organization Technology Provided by Logical Tech Realized by Physical Tech

Role catalog Role
Unit Service Component Component
Organization Organization Business

Actor catalog Decomposition Interaction
diagram matrix

Read the associated paper for further discussion of
Avancier
► In TOGAF Communication requires that

■ Architecture v solution building blocks
■ The generic relation Speakers and hearers share an
► In ArchiMate
spoken words represent.
■ Service v Process (same thing in IAF)
■ Service v Interface (same thing in UML) Drawers and readers share an
■ Actor v Role (same thing in UML) understanding of the concepts
diagrams symbols represent.
■ Process v Function (same thing in some sources)
■ Structure v Behavior (peculiar in ArchiMate)
■ Data Object v Business Object

An alternative Business Architecture approach
Avancier


A BA artifact map with Capability and Value Stream artifacts?
Avancier
Driver
Stimulate
BMM
Goal Desired
Result
Decomposed into
Objective
Met by
Strategy/Capability Map? Business

Service
Delivered by
Capability?
Business Capability Map?
Business
Role
Business Capability/ Capability?
Perform
Organization matrix? Realized by Realized Process
by
Organization
Actor
Unit Value Stream
Organization Map?
Capability/Organization matrix? Value stream / Capability matrix? Value stream catalog

Value stream map
Capability-oriented artifacts
Avancier
► Business Capabilities Catalog

■ A definitive listing of particular abilities that a business may possess or exchange to achieve
a specific purpose.
► Business Capability Map
■ A family of diagrams representing a definitive listing of the particular abilities that a business
may possess or exchange to achieve a specific purpose.
► Strategy/Capability Matrix
■ The purpose of this matrix is to show the capabilities required to support specific strategy
statements.
► Organization Map
■ A diagram showing the relationships between the primary entities that make up the
enterprise, its partners, and stakeholders.
► Capability/Organization Matrix
■ The purpose of this matrix is to show the organization elements that implement each
capability. The Capability/Organization matrix includes the following metamodel entities:
● Business Capability, Value Stream, Organization Unit

About Capabilities and Purposes
Avancier
► In the BMM, Desired Result is the catch all for Goals and
Objectives
► In TOGAF, Business Drivers > Goals > Objectives > Services
► How does a Capability’s Purpose relate to the above?

► Can you have a Purpose without a Capability? Or are they 1 to 1?

About Capabilities and Building Blocks
Avancier
► To perform its required behaviors, does every Building Block need

a Capability?
■ If they are not 1 to 1, why not?
■ Where are Capabilities recorded?
► To perform its required behaviors, does every Business Function

need a Business Capability?
■ If they are not 1 to 1, why not?
■ How does a Business Capability Map differ in purpose or use from a
Functional Decomposition diagram?

Value stream-oriented artifacts
Avancier
► Value Stream Catalog

■ A definitive listing of end-to-end collections of value-adding activities that create an overall
result for a customer, stakeholder, or end user.
► Value Stream Stages Catalog
■ A definitive listing of end-to-end collections of the different stages for the value-adding
activities that create an overall result for a customer, stakeholder, or end user; it includes the
following metamodel entities:
■ Business Capability
■ Value Stream
► Value Stream/Capability Matrix
■ The purpose of this matrix is to show the capabilities required to support each stage of a
value stream.
► Value Stream Map
■ A family of diagrams representing a definitive listing of end-to-end collections of value-adding
activities that create an overall result for a customer, stakeholder, or end user.
■ The Value Stream map includes the following metamodel entities:
■ Business Capability
■ Value Stream

About Value Streams and Results
Avancier
► In the BMM, Desired Result is the catch all for Goals and
Objectives
► In TOGAF, Business Drivers > Goals > Objectives > Services
► How does a Value Stream’s Result relate to the above?.

► Is a Value Stream’s Result
a) the exit condition of the process (output flows and system state
changes)?
b) the desired outcome of those being used by some actor to meet some
goal or objective?
► Can a Value Stream Stage be further decomposed?

► Does the Value Stream/Capability Matrix map to all Capabilities, or only to
Business Capabilities?

Connecting artifacts together
Avancier
► TOGAF does not prescribe which artifacts to produce

► Nor the sequence to produce them
► But the artifacts do connect together
Business Logical Actors playing Create & Business

Business Stimulate Met by Business Encapsulate Realized by Perform Business
Goals & Business Roles in Use Data
Drivers Services Processes
Objectives Functions Organization Units Entities
Driver/Goal/Objective Goal/Objective Service Functional Function/Organization Process & Role Conceptual Data Dgrm
catalog Dgrm Decomposition Dgrm Matrix Catalogs Data/Entity Business
Organization Business Service Catalog Business Organization Business Scenario Function
Decomposition Dgrm Service/Function Catalog Decomposition Dgrm document(s) Business Service/Data
Process flow Dgrm(s) Dgrm

Alternative business architecture approaches
Avancier
► BA approach 1
Business Logical Actors playing
Business Business
Stimulate Goals & Met by Encapsulate Business Realized by Roles in
Drivers Services
Objectives Functions Organization Units
Perform
Business
Processes
► BA approach 2
Strategy/Capability Matrix Capability/Organization Matrix
Organization Map
Purposes/ Organization
Strategy Fulfilled by Realized by
Capabilities Units
Value
Business Capabilities Catalog Results/ Realized by Additions/
Value Steams
Business Capability Map Value Stages
Value Stream/ Capability Matrix

Value Stream Map Value Stream Stages Catalog
Value Stream Catalog

Footnotes
Avancier
► Left overs

Application/Function Matrix drawn as a diagram
Avancier
Strategic Vision and Strategy Finance Product Design Operations
management Costing Engineering
Business Data
Intelligence Warehouse
functions
Sales & Marketing Supply Manufacture Delivery Customer Service

Sales and Supply Chain Manufacturing Customer
Marketing Planning Scheduling
Projects Contact
Product Manufacturing Activity Call Center
Purchasing
Configurator Process Management support
Order Supplier Manufacturing Workflow
Operational Entry Scheduling Flow Management
Service
functions Inspection Bills of Time and
Pricing
of goods Material Expenses
Billing Inventory Cost

Management Capacity
Commissions Quality
Control
Human Resources Accounts Facilities Knowledge ITSM

Human Accounts and Change Identity
Resources Receivable management
Training
Accounts IT Service
Benefits
Payable Management
Support Project
General Server
functions Payroll
Ledger
Management
Management
Legal Doc
Fixed Management Network
Rostering Assets Management
Time and Cash EAI
Attendance Management Middleware

A Business Scenario (after TOGAF 8 example)
Avancier
Roles
(human actors) Salesman Customer
Process Initiate Discuss Configure Verify Price Confirm Place

Order
Capture
signature
Applications
Product Order
Inventory Scheduling Pricing
(computer actors) configurator Entry

“Service Portfolio”
Avancier
► “a collection of services, AutoXpress Services

potentially an interface Fit tyres
definition. Check-up and oil change
Service AutoXpress Full annual service
Portfolio Services Check brakes
Repair brakes
► “used in the TOGAF Realized by Realized by
Check exhaust
framework to define the Replace exhaust
requirement for a building Inspect battery
Business Replace battery
block or system.” (Ch. 3) System
AutoXpress
Align wheels
Fit bulbs
► “For each building block, build Replace shock absorbers
up a service description
portfolio as a set of non-
conflicting services.”

Subdividing a system into subsystems
Avancier
► The service portfolio of a system may be divided

into service bundles assignable to different
subsystems.
► For Portability, Interoperability and Boundaryless

Information Flowtm.
■ “An architectural framework.. should describe a method for designing
an information system in terms of a set of building blocks, and for
showing how the building blocks fit together.” TOGAF 7
► For IT architecture.
■ “The TOGAF Technical Reference Model ... contains all possible
services.
■ Service bundles are represented .. in the form of "Building Blocks".
■ The IT architect must analyse the services actually needed [to]
define the set of optimal solution building block. TOGAF 7

“Systems are built up from collections of building blocks” (Ch. 33)
Avancier
►... building blocks have to interoperate

with other building blocks.”
Business System
• “An architecture is a set of building blocks
depicted in an architectural model,
• and a specification of how those building
blocks are connected to meet the overall Building Block
requirements of the business.” Building
Block

“Building block” in TOGAF chapter 33
Avancier
► “has a defined boundary”

■ Is encapsulated by IO flows
Business System
► “recognizable as "a thing" by domain experts”
■ Is a structure rather than a transient behavior
► “may interoperate.”
■ Building blocks cooperate in a network
Building Block
► “A good building block Building
■ considers implementation and usage, and Block
■ evolves to exploit technology and standards

● Is logical, but not divorced from physical reality
■ may be assembled from other building blocks, and a subassembly of others
● may be composed and decomposed in a hierarchical structure
■ is re-usable and replaceable, and well specified.”
● Is a plug and play component

“Building block” in TOGAF chapter 3
Avancier
► “a (potentially re-usable) component of

enterprise capability
Business System
► can be combined with other building
blocks to deliver architectures and
solutions.”
Building Block
► The granularity varies from situation to Building
situation. Block
► A service can be
► “coarse-grained (build a house) or
► fine-grained (retrieve an address).” (Ch. 3)

Abstraction by idealisation
Avancier
Goal/
Objective
Objectives <are met by delivery of> Services
Service
Services <are assigned to> ABBs

► “A building block’s boundary and specification
should be loosely coupled to its implementation.” Architecture A logical
(Ch. 33) Building specification
Block of below
ABBs <are realized by>

► “It should be possible to realize a building block in SBBs
several different ways without impacting [its]
boundary or specification.” (Ch. 33) Solution An encapsulated
package of
Building capability
Block

Abstraction by idealisation
Avancier
Goal/
Objective
Objectives <are met by delivery of> Services
► “The major work… consists of identifying the

Service
architecture building blocks required to meet the
business goals and objectives.
Services <are assigned to> ABBs
► “The selected set of architecture building blocks is then

refined in an iterative process.... Architecture A logical
Building specification
► to arrive at a set of solution building blocks which can Block of below
either be bought off-the-shelf or custom developed.”

(Ch. 33)
ABBs <are realized by>
SBBs
► IOW: you hire, buy or build physical components to
Solution An encapsulated
perform the required behaviors assigned to the logical package of
Building capability
components. Block

Abstraction by generalisation
Avancier
Resource
Material Data
Energy
Entity structure
TOGAF
Other Foundation
Human Machine
Object
Common
Computer Vehicle
system
Client Server Industry

Device Device
Lap Top Organisation
A Lap
Top

Note
Avancier
► Structures perform behaviors Logical

■ Roles perform Processes? Hmm... Business Function Role
Components
■ Functions perform Services? Hmm...
► Logical structures only specify what can perform Physical Organization
Actor
behaviors Business Unit
Components
► Behaviors do not perform behaviors

Business
■ Processes do not perform processes. Behaviors
Service Process
■ Services do not perform services.
► But processes can communicate with each other
and access data

TOGAF With ArchiMate Concepts

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TOGAF With ArchiMate Concepts

Uploaded by

Copyright:

Available Formats

Avancier

Harmonising two conceptual

Mapping TOGAF® to ArchiMate®

AKA Terminology Torture

Including some slides from Avancier’s training to

Copyright Avancier Ltd 2018

► What is needed for the ► Processes

Copyright Avancier Ltd 2018

► TOGAF best known for its process

Copyright Avancier Ltd 2018

Business Capabilities Catalog Organization Map Value Stream (Stages) Catalog

Copyright Avancier Ltd 2018

Copyright Avancier Ltd 2018

► Not about diagrams! ► Rather, about the concepts in

Copyright Avancier Ltd 2018

► The bride and groom come from

Copyright Avancier Ltd 2018

► If you know the history of TOGAF, you can find a coherent

► This presentation compares and contrasts

Copyright Avancier Ltd 2018

1. The initial direction to EA

Copyright Avancier Ltd 2018

► “Business planning at the strategy level provides the initial direction

Copyright Avancier Ltd 2018

Business Mission Business

Copyright Avancier Ltd 2018

► TOGAF’s Principles are “Directives”

A business strategy document

Copyright Avancier Ltd 2018

“Means” and “End” words in the Business Business

Business Business Architecture

Copyright Avancier Ltd 2018

Copyright Avancier Ltd 2018

“a cross-organizational reference... Objective

to identify synergies across the Organization

Copyright Avancier Ltd 2018

1. The initial direction to EA

Copyright Avancier Ltd 2018

► “EA structures the business planning into an integrated framework that

EA is about business system planning.

Copyright Avancier Ltd 2018

► One or more business operations that we can model as

► A discrete event-driven system in which

Copyright Avancier Ltd 2018

► Active structures ► Subsystems or components

Copyright Avancier Ltd 2018

► A behavior exposed at the interface of a

■ update the internal state of the system

Copyright Avancier Ltd 2018

► A service contract comprises

Copyright Avancier Ltd 2018

► one or more processes are needed to

Process flow Realize

● A sequence of sub processes (stages, steps or activities) Active

Initiate Discuss Configure Verify Price Confirm Place Capture

Copyright Avancier Ltd 2018

► Two behaviors can collaborate

Sales Discuss Configure Verify Price order

Copyright Avancier Ltd 2018

► A structure that does not act, but is acted on.

Copyright Avancier Ltd 2018

Data entity Realize

– A unit of data recognized by a Data Application