ArchiMate 3.0 to TOGAF 9.1 mapping table

 

 

In 2008, work commissioned by the British Computer Society required reconciliation of terms and concepts in TOGAF, ArchiMate and UML.

This proved difficult until we mapped general system theory concepts to the ArchiMate generic meta model, and then to TOGAF.

The tables below are simplistic; you can learn much more in this TOGAF-ArchiMate alignment slide show.

 

TOGAF 9.1 IN A TABLE

Business Planning

Architectural Description of Business System Change as in TOGAF

Business & IT Operations

Business Mission,

Vision, Drivers,

Principles,

Strategy

ADM Deliverables

Architecture Requirements Spec.

Architecture Definition Document

Architecture Road Map

Enterprise Repository

Requirements Repository

Architecture Repository

Solutions Repository

CMDB

Enterprise Continuum

Requirements and Context

Architecture Continuum

Solution Continuum

Deployed Solutions

Building Blocks

 

Architecture Building Blocks

Solution Building Blocks

 

Required behaviors

run over time

Delivery behaviors

sequence behaviors

Logical structures

group behaviors

Physical structures

nominated to perform behaviors

Real structures

instantiated to perform

Goals & Objectives

Business

Business Services

Processes

Functions & Roles

Organisation Units & Actors

Organisation Units & Actors

 

Information Systems

IS (Application) Services

(Use cases)

Logical Application Components

Physical Application Components

Application Instances

 

Technology

Platform (Technology) Services

Logical Technology Components

Physical Technology Components

Technology Instances

 

A SIMPLE ARCHIMATE 3.0 TO TOGAF 9.1 MAPPING

Required behaviors

run over time

assigned to

Logical structures

group behaviors

realised by

Physical structures

nominated to perform behaviors

Business

Business Services & Processes

Functions & Roles

Organisation Units & Actors

Both

Scenarios & Value Streams

Capabilities

Other

Information Systems

IS Services

Logical Application Components

Physical Application Components

TOGAF

Application Services

Application Interfaces (or Functions)

Application Components

ArchiMate

Technology Infrastructure

Platform Services

Logical Technology Components

Physical Technology Components

TOGAF

Technology Services

Technology Interfaces (or Functions)

Nodes: System Software & Devices

ArchiMate

 

Note: some concepts in both sources are ambiguous, and a fully satisfactory mapping is not possible because the generic meta models are different.

 

ANOTHER TABLE DRAWN UP DURING ANALYSIS (no longer being updated).

TOGAF entities

 

ArchiMate entities

Principles visions & requirements

 

 

 

Motivation

Architecture principle

 

 

 

 

Principle

Business strategy, Technology strategy

 

 

 

 

Goal

Business principle, Objective, Driver

 

 

 

 

Principle, Goal

Architecture vision

 

 

 

 

 

Stakeholder

 

 

 

 

Stakeholder

Requirement

 

 

 

 

Requirement

Constraint

 

 

 

 

Constraint

Assumption

 

 

 

 

 

Gaps

 

 

 

 

Gap

Business architecture

 

Behavior

Active structure

Passive structure

Driver

 

 

 

 

Assessment?

Goal, Objective, Measure

 

 

 

 

Goal

Location

 

 

 

Location

 

Business Service, Contract, Quality

 

Business Service

 

Contract, Product

 

Process, Event, Control, Product

 

Business Process

 

Product

 

Function

 

Business Function

Business Interface (Function?)

 

 

Role

 

 

Business Role

 

 

Organisation unit

 

 

Actor

 

 

Actor

 

 

Actor

 

 

Data architecture

 

Behavior

Active structure

Passive structure

Data entity

 

 

 

Business Object, Data Object, Meaning?

 

Logical Data Component

 

 

 

 

 

Physical Data Component

 

 

 

Representation (physical data structure)?

 

(Deployed solution?)

 

 

 

Artifact (deployable)?

 

Application(s) architecture

 

Behavior

Active structure

Passive structure

 

Information System Service

 

Application Service

 

 

 

Logical Application Component

 

Application Function

Application Interface (or Function?)

 

 

Physical Application Component

 

 

Application Component

 

 

(Deployed solution?)

 

 

 

Artifact (deployable)?

 

Technology architecture

 

Behavior

Active structure

Passive structure

 

Platform Service

 

Technology Service

 

 

 

Logical Technology Component

 

Technology Function

Technology Interface (or Function?)

 

 

Physical Technology Component

 

 

Node: System Software or Device

 

 

(Deployed solution?)

 

 

 

Artifact (deployable)?

 

Architecture realisation

 

 

 

 

 

Capability

 

Business Function

 

Project result?

Work package

 

 

 

 

Project, Project result?

Architecture contract

 

 

 

 

 

Standard

 

 

 

 

 

Guideline

 

 

 

 

 

Specification