ArchiMate® for NAF v4
Update from The Open Group NATO/NAF
ArchiMate Mapping Working Group
Marc Lankhorst, BiZZdesign
Eugene McSheffrey, MEGA International
June 19, 2019
1
Copyright © The Open Group 2018
Agenda
1. Mapping NAFv4 to the ArchiMate® standard: background and
challenges
2. Addressing the challenges using ArchiMate®
2
Copyright © The Open Group 2018
Mapping ArchiMate® to NAFv4
» NAFv4: One framework, two metamodels:
NATO Architecture Framework Version 4
» Not prescribed in the standard:
– The mapping of NAF viewpoints and concepts to ArchiMate and UAF
– How to implement the suggested representations for viewpoints using the metamodels
» The Open Group is working to establish a standardized mapping for the
ArchiMate standard and NAFv4
3
Copyright © The Open Group 2019
NAF, UAF® and ArchiMate®
Software/ Systems Engineering / Enterprise Architecture
UML
notation
SysML
notation
UML
meta-model
SysML
meta-model
Semantic
Domain:
Software
Engineering
Semantic
Domain:
Systems
Engineering
NAFv4
Enterprise Architecture
UAF
recommended
notations
NAFv4
suggested view
representations
ArchiMate
notation
UAF
meta-model
(DMM)
NAF v4
simplified metamodel (SMM)
ArchiMate
meta-model
Semantic Domain:
Defense Enterprise
Architecture
+ Business
requirements
Semantic Domain:
Enterprise
Architecture
ArchiMate® vs. UAF® Domain Metamodel (UAF-DMM)
Stakeholders & goals
» ArchiMate standard:
ArchiMate®
– Focused on enterprise architecture, stakeholders &
goals, translating strategy into action, problem space
– Upstream, communication of the essentials
Problem analysis
Enterprise
architecture
» UAF-DMM:
– Focuses on acquisition and enterprise architecture
– Can handle systems engineering, requirements of
contractors & realization in the solution space
– Upstream, communication of acquired capabilities
– Downstream, implementation-level details
Strategy
Solution
architecture
Solution
design
UAF-DMM
Implementation
Contractors & realization
6
Copyright © The Open Group 2019
ArchiMate®, UAF® and the NAFv4 Simplified Meta-Model (SMM)
» ArchiMate® and UAF-DMM have
a different focus but have the
potential to be combined
» ArchiMate is a single language,
allowing different visualizations
(views)
» Uaf-DMM is an open meta-model
that can be implemented by
different language profiles
7
Copyright © The Open Group 2019
Correspondences between frameworks
NAFv4
ArchiMate®
Concept
Strategy
Service
Specification
Services specified
in each “core” layer
Logical
Specification
Business
Application
Physical
Resource
Specification
Technology
Architecture
Meta-Data
No corresponding
layer or aspect
Roadmap
Implementation &
Migration
Constraint
Motivation
Physical
Layers and viewpoints
Prescribed viewpoints
Example viewpoints (informative)
» Most viewpoints are defined for specific cells in the grid,
with relatively few elements from other layers.
ArchiMate Elements (by layer)
ArchiMate®
NAFv4 SMM Elements (by layer)
NAF v4
» Viewpoints often cross layers to
provide an overview. New viewpoints
can be defined as required
Metamodel concepts
NAFv4
> 120 concepts
(in SMM)
> 200 concepts
(including type/ instance
and composite structures)
71 concepts
(60 elements +
11 relationship types)
» A one-to-one mapping
for all concepts in the
different metamodels
should not be expected
» The underlying
ontologies are different
Scope
The ArchiMate standard provides a way to show dependencies between models of
different architecture domains that are typically created using specialized notations
Enterprise Model (ArchiMate®)
Simple
Taxonomy
Structure
Connectivity
Behaviour
Information
Constraints
Roadmap
Detailed
Scope
(NAF aspects of concern)
Copyright © The Open Group 2019
12
Some differences between the ArchiMate language and UML/SysML
» The ArchiMate language was designed with communication in mind, more than
engineering
» UML supports additional specificity that is not available in the ArchiMate language. e.g.
– UML Class Diagrams can be used to elaborate ArchiMate Active Structure Elements such as Application
Components, and information elements such as business and data objects.
– UML State Machine Diagrams can be used to represent state transitions of elements defined in ArchiMate
models.
– UML Sequence Diagrams express object interactions and can be used to elaborate ArchiMate behaviour
elements.
» No type-instance distinction
– The ArchiMate language intentionally does not support a difference between types and instances. This is less
relevant in enterprise architecture (which is mostly concerned with types) and makes models more difficult to
understand for non-technical audiences.
» Simple composition model
– In comparison, SysML has a structured composition model (block/part) with structured boundaries (ports etc.)
– ArchiMate interface and service concepts can be used to model such boundaries but you may need to
enforce a modeling convention
13
Copyright © The Open Group 2019
Challenges
1. How should the ArchiMate metamodel be used to construct NAFcompliant architectures?
– How can NAF viewpoints be expressed in the ArchiMate language?
– Should the language be extended to enable the use of concepts and/or viewpoint
representations that are not supported in the ArchiMate standard ?
2. How can NAF architectures be constructed in a way that enables the
best use of both the ArchiMate® and UAF® metamodels?
– How should teams using different metamodels exchange model content?
– How should teams using both metamodels integrate their work to produce a
consistent architecture?
3. How to encourage adoption and promote best practice for using the
ArchiMate and UAF standards for NAF?
14
Copyright © The Open Group 2019
Agenda
1. Mapping NAFv4 to the ArchiMate® standard: background
and challenges
2. Addressing the challenges using the ArchiMate language
15
Copyright © The Open Group 2018
How to make the ArchiMate language work for NAF?
Work in progress by The Open Group ArchiMate Forum Working Group:
1. Map NAF terms to corresponding ArchiMate concepts
– Close match found (so far) for many of the NAF terms,
and more with some specializations
2. Express NAF v4 views in ArchiMate notation
– Mapping of applicable views
– Good examples are key, e.g. the
Federated Mission Networking architecture
is already being expressed in ArchiMate
3. Let ArchiMate notation work with other standards
–
It was designed to do so from the beginning
16
Copyright © The Open Group 2019
ArchiMate Layer/ Aspect
ArchiMate Element
Motivation
Stakeholder
Motivation
Driver
Motivation
Assessment
Motivation
Goal
Motivation
Outcome
Motivation
Principle
Motivation
Requirement
Motivation
Constraint
Motivation
Meaning
Motivation
Value
Strategy
Resource
Strategy
Capability
Strategy
Course of Action
Business
Business Actor
Business
Business Role
Business
Business Collaboration
Business
Business Interface
Business
Business Process
Business
Business Function
Business
Business Interaction
Business
Business Event
Business
Business Service
Business
Business Object
Business
Contract
Business
Representation
Business
Product
Application
Application Component
Application
Application Collaboration
Application
Application Interface
Application
Application Function
Application
Application Interaction
Application
Application Process
Application
Application Event
Application
Application Service
Application
Data Object
Technology
Node
Technology
Device
Technology
System Software
Technology
Technology Collaboration
Technology
Technology Interface
Technology
Path
Technology
Communication Network
Technology
Technology Function
Technology
Technology Process
Technology
Technology Interaction
Technology
Technology Event
Technology
Technology Service
Technology
Technology Object
Technology
Artifact
Physical
Equipment
Physical
Facility
Physical
Distribution Network
Physical
Material
Implementation & Migration Work Package
Implementation & Migration Deliverable
Implementation & Migration Implementation Event
Implementation & Migration Plateau
Implementation & Migration Gap
Composite Elements
Grouping
Composite Elements
Location
ArchiMate elements with at least one analogous NAF term:
Copyright © The Open Group 2019
#
1
SERVICE SPECIFICATION
Architecture Project
Architecture Standard*
Architecture Framework*
Architecture Version
View Attribute
Architecture Methodology
Correspondence Rule
Architecture Dependency
Stakeholder Concern*
Architecture Stakeholder*
Enterprise Phase
Architecture Product
Architecture Structure
Viewpoint*
View*
Architecture Element
Meta-data Tag
Architecture Rule
PHYSICAL RESOURCE SPECIFICATION
Service Implementation
Textual Data Schema (e.g. SQL)
Physical Data Structure
Data Element
Resource Function
Physical Link Capacities
Physical Link Attributes
Physical Flow
Artefact*
Human Resource
Organisational Structure
Requirement*
Capability Configuration
Resource Interaction
Post
Logical Architecture Element
Sub-system
Future Impact
Future Trend
Competency
Technology
Port
Hardware Specification
Interface protocol
Rich picture
Arbitrary interaction
Arbitrary element
Project Milestone
Project Deliverable*
Business Rule
Data Entity
Information Element Attribute
Information Element
Event
Properties of Logical Flows
Location
Logical Flow
Activity Sequence
Logical Activity
LOGICAL SPECIFICATION
ARCHITECTURE META-DATA
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
1
1
3
S
S
1
1
1
1
1
1
1
1
2
S
S
1
1
1
1
S
S
S
S
S
S
S
S
S
S
S
S
S
FF
S
S
1
1
1
1
1
S
S
S
S
S
1
1
FF
S
1
3
2
3
2
S
1
1
1
1
1
1
1
7
1
1
1
S
S
1
1
S
S
S
S
S
1
S
S
S
2
3
1
S
S
1
1
1
43
Role*
Node
Service Level
Data Type
Parameter
Service Consumer
State Transition
State
Service Function
Service Operation
Required Service Interface
Provided Service Interface
Service Attribute
Measure
Service/ Service Specification
Project*
Programme*
Capability Increment
Assumed benefit
Constraint
Measure Category
Resource Type
Effects
Standard Activity
Time Period
Enduring Task
Measurable Benefit
Outcome
Goal*
CONCEPT
1
1
1
4
1
4
1
1
Vision*
Measure of Effectiveness (MoE)
Capability Dependency
Capability*
NAF Term
*indicates a term in the NAF
Glossary
Terminology mapping (work in progress)
3
1
1
1
1
1
1
1
S
1
4
2
1
1
1
S
S
S
S
2
2
1
1
1
4
2
1
1
2
1
1
1
1
17
ArchiMate Layer/ Aspect
Motivation
Motivation
Motivation
Motivation
Motivation
Motivation
Motivation
Motivation
Motivation
Motivation
Strategy
Strategy
Strategy
Business
Business
Business
Business
Business
Business
Business
ArchiMate Element
Stakeholder
Driver
Assessment
Goal
Outcome
Principle
Requirement
Constraint
Meaning
Value
Resource
Capability
Course of Action
Business Actor
Business Role
Business Collaboration
Business Interface
Business Process
Business Function
Business Interaction
#
1
Service Level
Data Type
Parameter
Service Consumer
State Transition
State
Service Function
Service Operation
Required Service Interface
Provided Service Interface
Service Attribute
Measure
Service/ Service Specification
Project*
Programme*
Capability Increment
Assumed benefit
Constraint
Measure Category
Resource Type
Effects
Standard Activity
Time Period
Enduring Task
Measurable Benefit
Outcome
Goal*
CONCEPT
1
1
1
4
1
4
1
1
Vision*
Measure of Effectiveness (MoE)
Capability Dependency
Capability*
NAF Term
*indicates a term in the NAF
Glossary
Terminology mapping (work in progress)
SERVICE SPECIFICATION
S
S
S
S
S
S
S
S
S
1
1
2
3
1
S
S
S
S
S
18
Copyright © The Open Group 2019
Viewpoint mapping
Many possible representations:
1. Lists, matrices and other tables can of course be generated from models in
any modeling language, including ArchiMate
2. ArchiMate standard notation is well-suited for many NAF views
3. Next to the standard notation, the ArchiMate language also allows for other
representations. See the chapter on Architecture Views & Viewpoints in the
standard
Mapping on the next slides is provisional!
19
Copyright © The Open Group 2019
NAF v4 viewpoint representations (work in progress)
NAFv4 View
C1 – Capability Taxonomy
C1 – Capability Taxonomy
C1 – Capability Taxonomy
C1 – Capability Taxonomy
C2 – Enterprise Vision
C2 – Enterprise Vision
C2 – Enterprise Vision
C2 – Enterprise Vision
C3 – Capability Dependencies
C3 – Capability Dependencies
C3 – Capability Dependencies
C3 – Capability Dependencies
C3 – Capability Dependencies
C4 – Standard Processes
C4 – Standard Processes
C4 – Standard Processes
C5 – Effects
C5 – Effects
C5 – Effects
C5 – Effects
C6 – Not Used
C7 – Performance Parameters
C7 – Performance Parameters
C7 – Performance Parameters
C8 – Planning Assumptions
C8 – Planning Assumptions
C8 – Planning Assumptions
Cr– Capability Roadmap
Cr– Capability Roadmap
S1 – Service Taxonomy
S1 – Service Taxonomy
S1 – Service Taxonomy
S1 – Service Taxonomy
S2 – Not Used
S3 – Service Interfaces
S3 – Service Interfaces
S3 – Service Interfaces
S4 – Service Functions
S4 – Service Functions
S4 – Service Functions
S5 – Service States
S5 – Service States
S6 – Service Interaction
S6 – Service Interaction
S7 – Service Interface Parameters
S7 – Service Interface Parameters
S7 – Service Interface Parameters
S8 – Service Policy
S8 – Service Policy
S8 – Service Policy
Sr – Service Roadmap
NAFv3 ID
Suggested Representation
Tabulation.
Hierarchical (Connected Shapes).
ArchiMate Capabilities
Class Diagram (with generalization relationships and property definitions).
Structured Text.
ArchiMate Stakeholder, Goal, Outcome concepts
UML Composite Structure Diagram.
SysML Structural Diagrams.
ArchiMate Capabilities
‘Nested box’ diagram.
UML Class diagram.
UML Composite Structure diagram.
SysML Structural diagram.
ArchiMate Business Processes
Tabular.
Tracing Diagram.
Tabular.
Structural diagram.
Histogram.
Finite state diagram.
Representation Type
Table
Hierarchical (Connected Shapes)
ArchiMate view
UML Class diagram
Structured Text
ArchiMate view
UML Composite Structure Diagram
SysML Structural Diagram
ArchiMate view
‘Nested box’ diagram
UML Class Diagram
UML Composite Structure Diagram
SysML Structural Diagram
ArchiMate view
Table
Tracing Diagram
Table
Structural diagram
Histogram
State Diagram
NCV-1
NCV-1
NCV-1
ArchiMate concepts with attribute definitions
Tabular (capabilities on one axis, measure categories on the other).
UML Classes with property definitions.
ArchiMate Stakeholder, Goal, Outcome concepts
Tabular.
Benefits diagram
A time based chart in the style of a Gantt chart.
ArchiMate Implementation & Migration concepts (e.g. Plateau, Impl. Event, Deliverable,
Work Package)
ArchiMate Business & Application Service concepts
Tabulation.
Hierarchical (connected shapes).
UML class diagram.
ArchiMate model
Table
UML Class Diagram
ArchiMate view
Table
Benefits diagram
Gantt Chart
ArchiMate view
Table
ArchiMate view
UML
Table
UML
ArchiMate view
UML
State Diagram
ArchiMate view
UML Sequence Diagram
Table
ArchiMate view
UML
Table
ArchiMate view
UML
ArchiMate view
UML Object Diagram
SysML block diagram
Topological (connected shapes)
ArchiMate view
UML Composite Structure Diagram
SysML Structural Diagram
Table
Topological (connected shapes)
ArchiMate view
NAV-1, NCV-2
NAV-1, NCV-2
NAV-1, NCV-2
NAV-1, NCV-2
NCV-1
NCV-1
NCV-1
NCV-1
NCV-4
NCV-4
NCV-4
NCV-4
NCV-4
NCV-6
NCV-6
NCV-6
NOV-6b
NOV-6b
NOV-6b
NOV-6b
NCV-3
NCV-3
NAV-2, NSOV-1
NAV-2, NSOV-1
NAV-2, NSOV-1
NAV-2, NSOV-1
NSOV-2
NSOV-2
NSOV-2
NSOV-3
NSOV-3
NSOV-3
NSOV-4b
NSOV-4b
NSOV-4c
NSOV-4c
NSOV-2
NSOV-2
NSOV-2
NSOV-4a
NSOV-4a
NSOV-4a
L4 – Logical Activities
L4 – Logical Activities
L4 – Logical Activities
L4 – Logical Activities
L5 – Logical States
L5 – Logical States
L6 – Logical Sequence
L6 – Logical Sequence
L6 – Logical Sequence
L6 – Logical Sequence
L7 – Logical Data Model
L7 – Logical Data Model
L7 – Logical Data Model
L8 – Logical Constraints
L8 – Logical Constraints
L8 – Logical Constraints
L8 – Logical Constraints
Lr – Lines of Development
NOV-5
NOV-5
NOV-5
NOV-5
NOV-6b
NOV-6b
NOV-6c
NOV-6c
NOV-6c
NOV-6c
NSV-11a
NSV-11a
NSV-11a
NOV-6a
NOV-6a
NOV-6a
NOV-6a
NPV-2
Lr – Lines of Development
Lr – Lines of Development
L2-L3 – Logical Concept Viewpoint
L2-L3 – Logical Concept Viewpoint
L2-L3 – Logical Concept Viewpoint
L2-L3 – Logical Concept Viewpoint
P1 – Resource Types
P1 – Resource Types
P1 – Resource Types
P1 – Resource Types
P1 – Resource Types
P1 – Resource Types
P1 – Resource Types
P1 – Resource Types
P2 – Resource Structure
P2 – Resource Structure
P2 – Resource Structure
NPV-2
NPV-2
NOV-1
NOV-1
NOV-1
NOV-1
NSV-2a, 7, 9, 12
NSV-2a, 7, 9, 12
NSV-2a, 7, 9, 12
NSV-2a, 7, 9, 12
NSV-2a, 7, 9, 12
NSV-2a, 7, 9, 12
NSV-2a, 7, 9, 12
NSV-2a, 7, 9, 12
NOV-4, NSV-1
NOV-4, NSV-1
NOV-4, NSV-1
P2 – Resource Structure
P2 – Resource Structure
P3 – Resource Connectivity
P3 – Resource Connectivity
P3 – Resource Connectivity
P3 – Resource Connectivity
P3 – Resource Connectivity
P4 – Resource Functions
P4 – Resource Functions
NOV-4, NSV-1
NOV-4, NSV-1
NSV-2, NSV-6
NSV-2, NSV-6
NSV-2, NSV-6
NSV-2, NSV-6
NSV-2, NSV-6
NSV-4
NSV-4
UML instances (actual).
SysML block diagram.
Topological (connected shapes).
ArchiMate Technology & Physical concepts with Triggering & Flow relationships
UML composite structure diagram.
SysML structural diagram.
Tabulation.
Topological (connected shapes).
ArchiMate Technology & Physical (behavior) concepts with Triggering & Flow relationships
P4 – Resource Functions
P4 – Resource Functions
P4 – Resource Functions
P5 – Resource States
P6 – Resource Sequence
P6 – Resource Sequence
P6 – Resource Sequence
P7 – Physical Data Model
P7 – Physical Data Model
P7 – Physical Data Model
P7 – Physical Data Model
P8 – Resource Constraints
P8 – Resource Constraints
P8 – Resource Constraints
P8 – Resource Constraints
Pr – Configuration Management
Pr – Configuration Management
NSV-4
NSV-4
NSV-4
NSV-10b
NSV-10c
NSV-10c
NSV-10c
NSV-11b
NSV-11b
NSV-11b
NSV-11b
NSV-10a
NSV-10a
NSV-10a
NSV-10a
NSV-8
NSV-8
UML activity diagram (with swim lanes to represent resources).
UML Activity Diagram
Functional Breakdown (decomposition).
Hierarchical (Connected Shapes)
SysML activity diagram.
SysML Activity Diagram
UML state diagram.
UML Statechart diagram
Topological (connected shapes).
Topological (connected shapes)
ArchiMate Technology & Physical (behavior) concepts with Triggering relationships
ArchiMate view
UML Sequence Diagram (preferred).
UML Sequence Diagram
Formal text data modelling language (e.g. SQL, ISO10303-11, etc.).
Formal Text
Topological (connected shapes).
Topological (connected shapes)
ArchiMate Data Objects & Artifacts
ArchiMate view
UML class diagram.
UML Class Diagram
Text (preferably specified in a computer-interpretable constraint language such as OCL).
Structured Text
Tabular.
Table
ArchiMate Requirements & Constraints
ArchiMate view
<Note: The example given in NAF uses none of the specified representations>
Miscellaneous
Timeline View.
Timeline
ArchiMate Implementation & Migration concepts (e.g. Plateau, Impl. Event, Deliverable,
ArchiMate view
Work Package)
‘Herringbone’ diagram.
"Herringbone" Diagram
Tabular.
Table
Tables.
Table
Text.
Text
NAF grid representation.
NAF Grid
Other representations suitable for the architect.
Miscellaneous
Tabular.
Table
Graphical elements linked by tracing lines.
Topological (connected shapes)
Tabular.
Table
Text Document.
Text
Tabular.
Table
Text Document.
Text
Timeline representation.
Timeline
<Note: The example given in NAF uses none of the specified representations>
Miscellaneous
Tabular.
Table
Text document.
Text
Tabular.
Table
ArchiMate Principles, Requirements & Constraints
ArchiMate view
An Ar View is usually shown as a timeline annotated with architecture releases and meta-da Timeline
ArchiMate Implementation & Migration concepts (e.g. Plateau, Impl. Event, Deliverable,
ArchiMate view
Work Package)
<Note: The example given in NAF uses none of the specified representations>
Miscellaneous
Sr – Service Roadmap
Sr – Service Roadmap
C1-S1 – Capability to Service Mappi NSOV-3
C1-S1 – Capability to Service Mappi NSOV-3
C1-S1 – Capability to Service Mappi NSOV-3
L1– Node Types
NAV-2
L1– Node Types
NAV-2
L1– Node Types
NAV-2
L2 – Logical Scenario
NOV-2
L2 – Logical Scenario
NOV-2
L2 – Logical Scenario
NOV-2
L3 – Node Interactions
NOV-2, NOV-3
L3 – Node Interactions
NOV-2, NOV-3
L3 – Node Interactions
NOV-2, NOV-3
L4 – Logical Activities
NOV-5
Pr – Configuration Management
NSV-8
L4-P4 – Activity to Function MappingNSV-5
A1 – Meta-Data Definitions
NAV-3
A1 – Meta-Data Definitions
NAV-3
A2 – Architecture Products
A2 – Architecture Products
A3 – Architecture Correspondence
A3 – Architecture Correspondence
A4 – Methodology Used
A4 – Methodology Used
A5 – Architecture Status
NAV-1
A5 – Architecture Status
NAV-1
A6 – Architecture Versions
NAV-1
A6 – Architecture Versions
NAV-1
A7 – Architecture Meta-Data
NAV-1, NAV-3
A7 – Architecture Meta-Data
NAV-1, NAV-3
A8 – Standards
NTV-1, NTV-2
A8 – Standards
NTV-1, NTV-2
Ar – Architecture Roadmap
Ar – Architecture Roadmap
Ar – Architecture Roadmap
Copyright © The Open Group 2019
ArchiMate view
Table
Hierarchical (Connected Shapes)
UML Class Diagram
Tabular.
ArchiMate Application/Technology Interfaces
UML.
Tabular.
UML.
ArchiMate Application/Technology Functions
UML.
Other state transition models.
ArchiMate Flow relationships
Sequence Diagram
Tabular.
ArchiMate Application/Technology Interfaces with attributes
UML.
Tabular.
ArchiMate Contract concept
UML.
ArchiMate Implementation & Migration concepts (e.g. Plateau, Impl. Event, Deliverable,
Work Package)
A time based chart in the style of a Gantt chart.
Tabular.
Matrix (with capabilities on one axis, and services on the other one).
ArchiMate Capabilities & Business/Appl./Tech. Services
UML.
Topological (connected shapes).
ArchiMate (various concepts)
Tabular.
Topological (connected shapes).
ArchiMate (various concepts)
UML composite structure diagram.
Tabulation.
ArchiMate concepts connected with Flow relationships
Information flow diagram.
ArchiMate Bus. Processes, Appl. Functions, etc. with Aggregation, Composition & Flow
ationships
Hierarchy chart.
IDEF0 Diagram.
UML activity diagram.
UML activity diagram (with swim-lanes).
Topological (Connected Shapes).
UML state diagram.
ArchiMate behavior elements with Triggering relationships
UML sequence diagram.
Event-trace diagram.
Timing diagram.
ArchiMate Business & Data Objects
Entity-Relationship diagram (e.g. IDEF1X).
UML class diagram.
Structured Text.
ArchiMate Requirements & Constraints
UML diagram with associated UML constraints.
Business rules diagram.
ArchiMate Implementation & Migration concepts (e.g. Plateau, Impl. Event, Deliverable,
Work Package)
Timeline View.
Augmented Gantt Chart.
Graphic.
Rich Picture.
Concept diagram.
Project context diagram.
Tabulation.
Mapping (matrix).
Topological – connected shapes.
ArchiMate Technology & Physical concepts
UML Composite Structure Diagram.
SysML block diagram.
Timeline View.
‘Herringbone’ diagram.
Topological (connected shapes).
UML composite structure diagram (typical).
ArchiMate Technology & Physical concepts with Aggregation & Composition relationships
Gantt Chart
Table
Matrix
ArchiMate view
UML
Topological (connected shapes)
ArchiMate view
Table
Topological (connected shapes)
ArchiMate view
UML Composite Structure Diagram
Table
ArchiMate view
Information flow diagram
ArchiMate view
Hierarchical (Connected Shapes)
IDEF0
UML Activity Diagram
UML Activity Diagram
Topological (connected shapes)
UML Statechart diagram
ArchiMate view
UML Sequence Diagram
UML Sequence Diagram
Timing Diagram
ArchiMate view
ERD/IDEF1X
UML Class Diagram
Structured Text
ArchiMate view
UML
Business rules diagram
ArchiMate view
Timeline
Gantt Chart
Operational Concept Diagram
Operational Concept Diagram
Operational Concept Diagram
Project context diagram
Table
Matrix
Topological (connected shapes)
ArchiMate view
UML Composite Structure Diagram
SysML block diagram
Timeline
"Herringbone" Diagram
Topological (connected shapes)
UML Composite Structure Diagram
ArchiMate view
20
NAF v4 viewpoint representations (work in progress)
NAFv4 View
C1 – Capability Taxonomy
C1 – Capability Taxonomy
C1 – Capability Taxonomy
C1 – Capability Taxonomy
C2 – Enterprise Vision
C2 – Enterprise Vision
C2 – Enterprise Vision
C2 – Enterprise Vision
C3 – Capability Dependencies
C3 – Capability Dependencies
C3 – Capability Dependencies
C3 – Capability Dependencies
C3 – Capability Dependencies
C4 – Standard Processes
C4 – Standard Processes
C4 – Standard Processes
C5 – Effects
C5 – Effects
C5 – Effects
C5 – Effects
C6 – Not Used
C7 – Performance Parameters
C7 – Performance Parameters
C7 – Performance Parameters
C8 – Planning Assumptions
C8 – Planning Assumptions
C8 – Planning Assumptions
Cr– Capability
Copyright
© The OpenRoadmap
Group 2019
Cr– Capability Roadmap
NAFv3 ID
Suggested Representation
Tabulation.
Hierarchical (Connected Shapes).
ArchiMate Capabilities
Class Diagram (with generalization relationships and property definitions).
Structured Text.
ArchiMate Stakeholder, Goal, Outcome concepts
UML Composite Structure Diagram.
SysML Structural Diagrams.
ArchiMate Capabilities
‘Nested box’ diagram.
UML Class diagram.
UML Composite Structure diagram.
SysML Structural diagram.
ArchiMate Business Processes
Tabular.
Tracing Diagram.
Tabular.
Structural diagram.
Histogram.
Finite state diagram.
Representation Type
Table
Hierarchical (Connected Shapes)
ArchiMate view
UML Class diagram
Structured Text
ArchiMate view
UML Composite Structure Diagram
SysML Structural Diagram
ArchiMate view
‘Nested box’ diagram
UML Class Diagram
UML Composite Structure Diagram
SysML Structural Diagram
ArchiMate view
Table
Tracing Diagram
Table
Structural diagram
Histogram
State Diagram
NCV-1
NCV-1
NCV-1
ArchiMate concepts with attribute definitions
Tabular (capabilities on one axis, measure categories on the other).
UML Classes with property definitions.
ArchiMate Stakeholder, Goal, Outcome concepts
Tabular.
Benefits diagram
A time based chart in the style of a Gantt chart.
ArchiMate Implementation & Migration concepts (e.g. Plateau, Impl. Event, Deliverable,
ArchiMate model
Table
UML Class Diagram
ArchiMate view
Table
Benefits diagram
Gantt Chart
ArchiMate view
NAV-1, NCV-2
NAV-1, NCV-2
NAV-1, NCV-2
NAV-1, NCV-2
NCV-1
NCV-1
NCV-1
NCV-1
NCV-4
NCV-4
NCV-4
NCV-4
NCV-4
NCV-6
NCV-6
NCV-6
NOV-6b
NOV-6b
NOV-6b
NOV-6b
NCV-3
NCV-3
21
Customization and modeling conventions
» The ArchiMate language has a built-in language customization
mechanism, which you can use to define specializations of concepts
– E.g. ‘Organization Unit’ as specialization of ‘Business Actor’
– These can have their own specific sets of properties
» In addition, you can define modeling conventions to restrict the use of
ArchiMate concepts and notation, e.g.:
– Use services and interfaces instead of ‘direct’ connections between elements
– Use triggering relationships between processes and flows between functions to express
behavior
22
Copyright © The Open Group 2019
The ArchiMate language and other standards
Enterprise model (ArchiMate®)
Simple
Intentional overlap
Business
model
(BMC)
Motivation
model
(BMM)
Business
process
model
(BPMN)
Software
model
(UML)
Data
model
(ERD)
…
Detailed
Scope
23
Copyright © The Open Group 2019
Integrated architecture leveraging the two NAF meta-models
ArchiMate Meta-Model
Fit for
purpose
Architecture
Models
Enterprise models for analyzing and communicating concerns
of Enterprise Architectures as they change over time
Shared Building Blocks Capabilities, Applications, Infrastructures, Projects etc.
UAF Meta-Model
Structured assembly of building blocks for enterprise
transformation and systems engineering over multiple time scales.
How the ArchiMate language works with other standards
» The ArchiMate standard connects architectural domains
– It doesn’t replace other standards but provides an ‘umbrella’ on top
– Broader scope, but less detailed
– Those details can be expressed in other languages
» Some concepts in the ArchiMate standard are taken from BPMN, UML, BMM and
others
– This intentional overlap makes it possible to link to e.g. UML descriptions of detailed design
or BPMN process models
– In some cases there are structural differences between the languages that preclude a direct
concept-to-concept mapping, requiring a pattern-based approach
» This way you can combine stakeholder-oriented, enterprise-level ArchiMate models
with development-oriented, engineering-level models in other standards
» The ArchiMate Model Exchange File Format standard allows ArchiMate models
interchange between different tools supporting interoperability and information
25
sharing. This represents a key benefit while interacting with other standards
Copyright © The Open Group 2019
Conclusions (1)
» Viewpoints from Enterprise Architecture & Systems Engineering are
complementary
– You need both in a full design trajectory
– But there may be a difference in use between ‘upstream’ clients (e.g. from NATO
partners) and ‘downstream’ contractors (e.g. the defense industry)
» The ArchiMate language is well-suited for NAF v4
– Initial assessments suggest substantial coverage of concepts and viewpoints
– In particular for communication, strategy, enterprise architecture, coherence across
domains, and other ‘upstream’ products
– Avoids unnecessary complexity for stakeholders who don’t need that
» NATO’s requirements analysis for NAF v4 shows that neither standard covers
all, so a combination is needed
– UAF-DMM satisfied 37%, ArchiMate 65% of weighted requirements
26
Copyright © The Open Group 2019
Conclusions (2)
» The ArchiMate standard plays well with other standards like UML and
SysML
– It was designed to do so from the start
– This makes a combined ArchiMate® – UAF-DMM approach feasible
» The ArchiMate Model Exchange File Format makes it easy to share
architecture content with other organizations (and their tools)
– A key benefit in a collaborative environment like NATO
» Good examples are key!
– E.g. the Federated Mission Networking (FMN) ArchiMate model being developed by
NATO
27
Copyright © The Open Group 2019
Thank you!
28
Copyright © The Open Group 2019