Erhalten Sie Zugang zu diesem und mehr als 300000 Büchern ab EUR 5,99 monatlich.
- Herausgeber: Van Haren Publishing
- Kategorie: Bildung
- Sprache: Englisch
The ArchiMate® Specification, a standard of The Open Group, defines an open and independent modeling language for Enterprise Architecture that is supported by different tool vendors and consulting firms. The ArchiMate language enables Enterprise Architects to describe, analyze, and visualize the relationships among business domains in an unambiguous way.
This is the official specification of the ArchiMate 3.2 modeling language from The Open Group.
The contents of the specification include the following:
- The introduction, including the objectives, overview, conformance requirements, and terminology
- Definitions of the general terms used in the specification
- The structure of the modeling language
- The generic metamodel of the language
- The relationships in the language
- A detailed breakdown of the modeling framework covering the motivation elements, Strategy Layer elements, and the three core layers (Business/Application/Technology)
- Relationships between core layers
- Implementation and Migration Layer elements for expressing the implementation and migration aspects of an architecture
- The concepts of stakeholders, architecture viewpoints, and views, as well as the ArchiMate viewpoint mechanism
- Mechanisms for customizing the language for specialized or domain-specific purposes
- Notation overviews and summaries
The intended audience is threefold:
- Enterprise Architecture practitioners, such as architects (e.g., application, information, process, infrastructure, and, obviously, Enterprise Architects), senior and operational management, project leaders, and anyone committed to work within the reference framework defined by the Enterprise Architecture
- Those who intend to implement the ArchiMate language in a software tool; they will find a complete and detailed description of the language in this standard
- The academic community, on which we rely for amending and improving the language based on state-of-the-art research results in the architecture field
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 251
Veröffentlichungsjahr: 2023
Das E-Book (TTS) können Sie hören im Abo „Legimi Premium” in Legimi-Apps auf:
Ähnliche
ArchiMate® 3.2 Specification
The Open Group Publications available from Van Haren Publishing
The TOGAF® Standard, 10th Edition:
Introduction and Core Concepts
Architecture Development Method
Content, Capability, and Governance
Leader’s Guide
ADM Practitioners’ Guide
Business Architecture
Enterprise Agility and Digital Transformation
A Pocket Guide
The TOGAF Series:
The TOGAF® Standard, Version 9.2
The TOGAF® Standard, Version 9.2 – A Pocket Guide
TOGAF® 9 Foundation Study Guide, 4th Edition
TOGAF® 9 Certified Study Guide, 4th Edition
TOGAF® Business Architecture Level 1 Study Guide
The Open Group Series:
The IT4IT™ Reference Architecture, Version 3.0
IT4IT™ for Managing the Business of IT – A Management Guide
IT4IT™ Foundation Study Guide, 2nd Edition
The IT4IT™ Reference Architecture, Version 2.1 – A Pocket Guide
Cloud Computing for Business – The Open Group Guide
ArchiMate® 3.1 Specification – A Pocket Guide
ArchiMate® 3.2 Specification
The Digital Practitioner Pocket Guide
The Digital Practitioner Foundation Study Guide
Open Agile Architecture™ – A Standard of The Open Group
The Open Group Press:
The Turning Point: A Novel about Agile Architects Building a Digital Foundation Managing Digital
The Open Group Security Series:
O-TTPS – A Management Guide
Open Information Security Management Maturity Model (O-ISM3)
Open Enterprise Security Architecture (O-ESA)
Risk Management – The Open Group Guide
The Open FAIR™ Body of Knowledge – A Pocket Guide
All titles are available to purchase from:
www.opengroup.org
www.vanharen.net
and also many international and online distributors.
Title:
ArchiMate® 3.2 Specification
Series:
The Open Group Series
A Publication of:
The Open Group
Publisher:
Van Haren Publishing, ’s-Hertogenbosch, www.vanharen.net
ISBN Hard copy:
978 94 018 00955 9
ISBN eBook (pdf):
978 94 018 00956 6
ISBN ePub:
978 94 018 00957 3
Edition:
Seventh edition, first impression, January 2023
Layout:
The Open Group
Copyright:
© 2012-2023, The Open Group. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owner.
Document Number: C226
Published by The Open Group, January 2023.
Comments relating to the material contained in this document may be submitted to:
The Open Group
Apex Plaza
Reading
Berkshire, RG1 1AX
United Kingdom
or by electronic mail to: [email protected]
Contents
1 Introduction
1.1 Objective
1.2 Overview
1.3 Conformance
1.4 Normative References
1.5 Terminology
1.6 Future Directions
2 Definitions
2.1 ArchiMate Core Framework
2.2 ArchiMate Core Language
2.3 Architecture View
2.4 Architecture Viewpoint
2.5 Aspect
2.6 Attribute
2.7 Composite Element
2.8 Concept
2.9 Conformance
2.10 Conforming Implementation
2.11 Core Element
2.12 Element
2.13 Layer
2.14 Model
2.15 Relationship
2.16 Relationship Connector
3 Language Structure
3.1 Language Design Considerations
3.2 Top-Level Language Structure
3.3 Layering of the ArchiMate Language
3.4 The ArchiMate Core Framework
3.5 The ArchiMate Full Framework
3.6 Abstraction in the ArchiMate Language
3.7 Concepts and their Notation
3.8 Use of Nesting
3.9 Use of Colors and Notational Cues
4 Generic Metamodel
4.1 Behavior and Structure Elements
4.1.1 Active Structure Elements
4.1.2 Behavior Elements
4.1.3 Passive Structure Elements
4.2 Specializations of Structure and Behavior Elements
4.3 Summary of Structure and Behavior Elements
4.4 Motivation Elements
4.5 Composite Elements
4.5.1 Grouping
4.5.2 Location
5 Relationships and Relationship Connectors
5.1 Structural Relationships
5.1.1 Composition Relationship
5.1.2 Aggregation Relationship
5.1.3 Assignment Relationship
5.1.4 Realization Relationship
5.1.5 Semantics of Structural Relationships
5.2 Dependency Relationships
5.2.1 Serving Relationship
5.2.2 Access Relationship
5.2.3 Influence Relationship
5.2.4 Association Relationship
5.2.5 Semantics of Dependency Relationships
5.3 Dynamic Relationships
5.3.1 Triggering Relationship
5.3.2 Flow Relationship
5.3.3 Semantics of Dynamic Relationships
5.4 Other Relationships
5.4.1 Specialization Relationship
5.4.2 Semantics of Other Relationships
5.5 Relationship Connectors
5.5.1 Junction
5.6 Summary of Relationships
5.7 Derivation of Relationships
6 Motivation Elements
6.1 Motivation Elements Metamodel
6.2 Stakeholder, Driver, and Assessment
6.2.1 Stakeholder
6.2.2 Driver
6.2.3 Assessment
6.2.4 Example
6.3 Goal, Outcome, Principle, Requirement, and Constraint
6.3.1 Goal
6.3.2 Outcome
6.3.3 Principle
6.3.4 Requirement
6.3.5 Constraint
6.3.6 Example
6.4 Meaning and Value
6.4.1 Meaning
6.4.2 Value
6.4.3 Example
6.5 Summary of Motivation Elements
6.6 Relationships with Core Elements
7 Strategy Layer
7.1 Strategy Elements Metamodel
7.2 Structure Elements
7.2.1 Resource
7.3 Behavior Elements
7.3.1 Capability
7.3.2 Value Stream
7.3.3 Course of Action
7.4 Example
7.5 Summary of Strategy Elements
7.6 Relationships with Motivation and Core Elements
8 Business Layer
8.1 Business Layer Metamodel
8.2 Active Structure Elements
8.2.1 Business Actor
8.2.2 Business Role
8.2.3 Business Collaboration
8.2.4 Business Interface
8.2.5 Example
8.3 Behavior Elements
8.3.1 Business Process
8.3.2 Business Function
8.3.3 Business Interaction
8.3.4 Business Event
8.3.5 Business Service
8.3.6 Example
8.4 Passive Structure Elements
8.4.1 Business Object
8.4.2 Contract
8.4.3 Representation
8.4.4 Example
8.5 Composite Elements
8.5.1 Product
8.5.2 Example
8.6 Summary of Business Layer Elements
9 Application Layer
9.1 Application Layer Metamodel
9.2 Active Structure Elements
9.2.1 Application Component
9.2.2 Application Collaboration
9.2.3 Application Interface
9.2.4 Example
9.3 Behavior Elements
9.3.1 Application Function
9.3.2 Application Interaction
9.3.3 Application Process
9.3.4 Application Event
9.3.5 Application Service
9.3.6 Example
9.4 Passive Structure Elements
9.4.1 Data Object
9.4.2 Example
9.5 Summary of Application Layer Elements
10 Technology Layer
10.1 Technology Layer Metamodel
10.2 Active Structure Elements
10.2.1 Node
10.2.2 Device
10.2.3 System Software
10.2.4 Technology Collaboration
10.2.5 Technology Interface
10.2.6 Path
10.2.7 Communication Network
10.2.8 Example
10.3 Behavior Elements
10.3.1 Technology Function
10.3.2 Technology Process
10.3.3 Technology Interaction
10.3.4 Technology Event
10.3.5 Technology Service
10.3.6 Example
10.4 Passive Structure Elements
10.4.1 Artifact
10.4.2 Example
10.5 Physical Elements Metamodel
10.6 Physical Active Structure Elements
10.6.1 Equipment
10.6.2 Facility
10.6.3 Distribution Network
10.7 Passive Structure Elements
10.7.1 Material
10.8 Example
10.9 Summary of Technology Layer Elements
11 Relationships Between Core Layers
11.1 Alignment of the Business Layer and Lower Layers
11.2 Alignment of the Application and Technology Layers
11.3 Example
12 Implementation and Migration Layer
12.1 Implementation and Migration Elements Metamodel
12.2 Implementation and Migration Elements
12.2.1 Work Package
12.2.2 Deliverable
12.2.3 Implementation Event
12.2.4 Plateau
12.2.5 Gap
12.2.6 Example
12.3 Summary of Implementation and Migration Elements
12.4 Relationships
12.5 Relationships with Other Aspects and Layers
13 Stakeholders, Architecture Views, and Viewpoints
13.1 Introduction
13.2 Stakeholders and Concerns
13.3 Architecture Views and Viewpoints
13.4 Viewpoint Mechanism
13.4.1 Defining and Classifying Viewpoints
13.4.2 Creating the View
13.5 Example Viewpoints
14 Language Customization Mechanisms
14.1 Adding Attributes to ArchiMate Concepts
14.2 Specialization of Concepts
14.2.1 Examples of Specializations of Business Layer Elements (Informative)
14.2.2 Examples of Specializations of Application Layer Elements (Informative)
14.2.3 Examples of Specializations of Technology Layer Elements (Informative)
14.2.4 Examples of Specializations of Physical Elements (Informative)
14.2.5 Examples of Specializations of Motivation Elements (Informative)
14.2.6 Examples of Specializations of Strategy Elements (Informative)
14.2.7 Examples of Specializations of Implementation and Migration Elements (Informative)
14.2.8 Examples of Specializations of Composite Elements (Informative)
14.2.9 Examples of Specializations of Relationships and Relationship Connectors (Informative)
A Summary of Language Notation
A.1 Core Elements
A.2 Motivation, Strategy, Implementation and Migration Elements
A.3 Relationships and Relationship Connectors
B Relationships (Normative)
B.1 Specification of Derivation Rules
B.2 Derivation Rules for Valid Relationships
B.2.1 Valid Derivations for Specialization Relationships
B.2.2 Valid Derivations for Structural Relationships
B.2.3 Valid Derivations for Dependency Relationships
B.2.4 Valid Derivations for Dynamic Relationships
B.3 Derivation Rules for Potential Relationships
B.3.1 Potential Derivation for Specialization Relationships
B.3.2 Potential Derivation for Structural and Dependency Relationships
B.3.3 Potential Derivation for Dependency Relationships
B.3.4 Potential Derivation for Dynamic Relationships
B.3.5 Potential Derivation Rule for Grouping
B.4 Restrictions on Applying Derivation Rules
B.5 Relationship Tables
B.6 Grouping, Plateau, and Relationships Between Relationships
C Example Viewpoints
C.1 Basic Viewpoints in the ArchiMate Language
C.1.1 Organization Viewpoint
C.1.2 Application Structure Viewpoint
C.1.3 Information Structure Viewpoint
C.1.4 Technology Viewpoint
C.1.5 Layered Viewpoint
C.1.6 Physical Viewpoint
C.1.7 Product Viewpoint
C.1.8 Application Usage Viewpoint
C.1.9 Technology Usage Viewpoint
C.1.10 Business Process Cooperation Viewpoint
C.1.11 Application Cooperation Viewpoint
C.1.12 Service Realization Viewpoint
C.1.13 Implementation and Deployment Viewpoint
C.2 Motivation Viewpoints
C.2.1 Stakeholder Viewpoint
C.2.2 Goal Realization Viewpoint
C.2.3 Requirements Realization Viewpoint
C.2.4 Motivation Viewpoint
C.3 Strategy Viewpoints
C.3.1 Strategy Viewpoint
C.3.2 Capability Map Viewpoint
C.3.3 Value Stream Viewpoint
C.3.4 Outcome Realization Viewpoint
C.3.5 Resource Map Viewpoint
C.4 Implementation and Migration Viewpoints
C.4.1 Project Viewpoint
C.4.2 Migration Viewpoint
C.4.3 Implementation and Migration Viewpoint
D Relationship to Other Standards, Specifications, and Guidance Documents
D.1 The TOGAF Framework
D.2 The BIZBOK Guide
D.3 The ArchiMate Language and Other Modeling Languages
D.4 BPMN
D.5 UML
D.6 BMM
E Changes from Version 2.1 to Version 3.2
E.1 Changes from Version 2.1 to Version 3.0.1
E.2 Changes from Version 3.0.1 to Version 3.1
E.3 Changes from Version 3.1 to Version 3.2
List of Figures
Figure 1: Top-Level Hierarchy of ArchiMate Concepts
Figure 2: ArchiMate Core Framework
Figure 3: ArchiMate Full Framework
Figure 4: Hierarchy of Behavior and Structure Elements
Figure 5: Behavior and Structure Elements Metamodel
Figure 6: Generic Internal Active Structure Element Notation
Figure 7: Generic External Active Structure Elements (Interface) Notation
Figure 8: Generic Internal Behavior Element Notation
Figure 9: Generic External Behavior Element (Service) Notation
Figure 10: Generic Event Notation
Figure 11: Generic Passive Structure Element Notation
Figure 12: Specializations of Core Elements
Figure 13: Generic Process Notation
Figure 14: Generic Function Notation
Figure 15: Generic Interaction Notation
Figure 16: Generic Collaboration Notation
Figure 17: Generic Motivation Element Notation
Figure 18: Composite Elements
Figure 19: Grouping Notation
Figure 20: Location Notation
Figure 21: Overview of Relationships
Figure 22: Composition Notation
Figure 23: Aggregation Notation
Figure 24: Assignment Notation
Figure 25: Realization Notation
Figure 26: Serving Notation
Figure 27: Access Notation
Figure 28: Influence Notation
Figure 29: Association Notation
Figure 30: Triggering Notation
Figure 31: Flow Notation
Figure 32: Specialization Notation
Figure 33: Junction Notation
Figure 34: Motivation Elements Metamodel
Figure 35: Stakeholder Notation
Figure 36: Driver Notation
Figure 37: Assessment Notation
Figure 38: Goal Notation
Figure 39: Outcome Notation
Figure 40: Principle Notation
Figure 41: Requirement Notation
Figure 42: Constraint Notation
Figure 43: Meaning Notation
Figure 44: Value Notation
Figure 45: Relationships Between Motivation Elements and Core Elements
Figure 46: Strategy Elements Metamodel
Figure 47: Resource Notation
Figure 48: Capability Notation
Figure 49: Value Stream Notation
Figure 50: Course of Action Notation
Figure 51: Relationships Between Strategy Elements and Motivation and Core Elements
Figure 52: Business Layer Metamodel
Figure 53: Business Internal Active Structure Elements
Figure 54: Business Actor Notation
Figure 55: Business Role Notation
Figure 56: Business Collaboration Notation
Figure 57: Business Interface Notation
Figure 58: Business Internal Behavior Elements
Figure 59: Business Process Notation
Figure 60: Business Function Notation
Figure 61: Business Interaction Notation
Figure 62: Business Event Notation
Figure 63: Business Service Notation
Figure 64: Business Passive Structure Elements
Figure 65: Business Object Notation
Figure 66: Contract Notation
Figure 67: Representation Notation
Figure 68: Product Metamodel
Figure 69: Product Notation
Figure 70: Application Layer Metamodel
Figure 71: Application Internal Active Structure Elements
Figure 72: Application Component Notation
Figure 73: Application Collaboration Notation
Figure 74: Application Interface Notation
Figure 75: Application Internal Behavior Elements
Figure 76: Application Function Notation
Figure 77: Application Interaction Notation
Figure 78: Application Process Notation
Figure 79: Application Event Notation
Figure 80: Application Service Notation
Figure 81: Data Object Notation
Figure 82: Technology Layer Metamodel
Figure 83: Technology Active Structure Elements
Figure 84: Node Notation
Figure 85: Device Notation
Figure 86: System Software Notation
Figure 87: Technology Collaboration Notation
Figure 88: Technology Interface Notation
Figure 89: Path Notation
Figure 90: Communication Network Notation
Figure 91: Technology Internal Behavior Elements
Figure 92: Technology Function Notation
Figure 93: Technology Process Notation
Figure 94: Technology Interaction Notation
Figure 95: Technology Event Notation
Figure 96: Technology Service Notation
Figure 97: Technology Passive Structure Elements
Figure 98: Artifact Notation
Figure 99: Physical Elements Metamodel
Figure 100: Equipment Notation
Figure 101: Facility Notation
Figure 102: Distribution Network Notation
Figure 103: Material Notation
Figure 104: Relationships Between Business Layer and Application and Technology Layer Elements
Figure 105: Relationships Between Application Layer and Technology Layer Elements
Figure 106: Implementation and Migration Metamodel
Figure 107: Work Package Notation
Figure 108: Deliverable Notation
Figure 109: Implementation Event Notation
Figure 110: Plateau Notation
Figure 111: Gap Notation
Figure 112: Relationships of Implementation and Migration Elements with Core Elements
Figure 113: Relationships of Implementation and Migration Elements with Motivation Elements
Figure 114: Conceptual Model of an Architecture Description (from [14])
Figure 115: Framing Stakeholder Concerns using the Viewpoint Mechanism
Figure 116: Correspondence Between the ArchiMate Language and the TOGAF ADM
Figure 117: Correspondence Between the ArchiMate Language and Other Modeling Languages
List of Examples
Example 1: Grouping
Example 2: Composition
Example 3: Aggregation
Example 4: Assignment
Example 5: Realization
Example 6: Semantics of Structural Relationships
Example 7: Serving
Example 8: Access
Example 9: Influence
Example 10: Association
Example 11: Semantics of Dependency Relationships
Example 12: Triggering
Example 13: Flow
Example 14: Specialization
Example 15: (And) Junction
Example 16: Or Junction
Example 17: Derivation from a Chain of Relationships
Example 18: Stakeholder, Driver, and Assessment
Example 19: Goal, Outcome, Principle, Requirement, and Constraint
Example 20: Meaning and Value
Example 21: Capability, Resource, and Course of Action
Example 22: Value Stream with Capability Cross-Mapping
Example 23: Business Active Structure Elements
Example 24: Business Behavior Elements
Example 25: Business Passive Structure Elements
Example 26: Business Composite Element: Product
Example 27: Application Active Structure Elements
Example 28: Application Behavior Elements
Example 29: Application Passive Structure Elements
Example 30: Technology Active Structure Elements
Example 31: Technology Behavior Elements
Example 32: Technology Passive Structure Element: Artifact
Example 33: Physical Elements
Example 34: Cross-Layer Relationships
Example 35: Implementation and Migration Elements
Example 36: Specializations of Business Layer and Motivation Elements
Example 37: Transitivity of Specialization
Example 38: Derivation of Structural Relationships
Example 39: Derivation from a Chain of Structural Relationships
Example 40: Derivation from a Dependency and a Structural Relationship in Line
Example 41: Derivation from a Dependency and a Structural Relationship in the Opposite Direction
Example 42: Derivation from a Dynamic and a Structural Relationship in Line
Example 43: Derivation from a Flow and a Structural Relationship in the Opposite Direction
Example 44: Derivation from a Triggering and a Structural Relationship in Line
Example 45: Derivation from Dynamic Relationships
Example 46: Derivation from Triggering Relationships
Example 47: Derivation from Triggering and Structural Relationships
Example 48: Examples of Potential Derivation
Example 49: Potential Derivation from a Specialization and Another Relationship in Line
Example 50: Potential Derivation from a Specialization and Another Relationship in the Opposite Direction
Example 51: Potential Derivation from Another Relationship and a Specialization in Line
Example 52: Potential Derivation from Another Relationship and a Specialization in Line
Example 53: Specializations Used in Potential Derivations
Example 54: Potential Derivation from a Dependency and a Structural Relationship in Line
Example 55: Potential Derivation from a Dependency and a Structural Relationship in the Opposite Direction
Example 56: Potential Derivation from Two Dependency Relationships
Example 57: Potential Derivation from a Dynamic and a Structural Relationship in Line
Example 58: Potential Derivation from a Dynamic and a Structural Relationship in the Opposite Direction
Example 59: Potential Derivation from Two Flow Relationships
Example 60: Potential Derivation from a Triggering and Structural Relationships
Example 61. Potential Derivation with Grouping Element
List of Tables
Table 1: Core Elements
Table 2: Motivation Element
Table 3: Relationships
Table 4: Motivation Elements
Table 5: Strategy Elements
Table 6: Business Layer Elements
Table 7: Application Layer Elements
Table 8: Technology Layer Elements
Table 9: Implementation and Migration Elements
Table 10: Profile Examples
Table 11: Relationship Profile Example
Table 12: Example Specializations of Business Layer Elements
Table 13: Example Specializations of Application Layer Elements
Table 14: Example Specializations of Technology Layer Elements
Table 15: Example Specializations of Physical Elements
Table 16: Example Specializations of Motivation Elements
Table 17: Example Specializations of Strategy Elements
Table 18: Example Specializations of Implementation and Migration Elements
Table 19: Example Specializations of Composite Elements
Table 20: Example Specializations of Relationships and Relationship Connectors
Table 21: Grouping, Plateau, and Relationships Between Relationships
Table 22: Basic Viewpoints
Table 23: Organization Viewpoint Description
Table 24: Application Structure Viewpoint Description
Table 25: Information Structure Viewpoint Description
Table 26: Technology Viewpoint Description
Table 27: Layered Viewpoint Description
Table 28: Physical Viewpoint Description
Table 29: Product Viewpoint Description
Table 30: Application Usage Viewpoint Description
Table 31: Technology Usage Viewpoint Description
Table 32: Business Process Cooperation Viewpoint Description
Table 33: Application Cooperation Viewpoint Description
Table 34: Service Realization Viewpoint Description
Table 35: Implementation and Deployment Viewpoint Description
Table 36: Stakeholder Viewpoint Description
Table 37: Goal Realization Viewpoint Description
Table 38: Requirements Realization Viewpoint Description
Table 39: Motivation Viewpoint Description
Table 40: Strategy Viewpoint Description
Table 41: Capability Map Viewpoint Description
Table 42: Value Stream Viewpoint Description
Table 43: Outcome Realization Viewpoint Description
Table 44: Resource Map Viewpoint Description
Table 45: Project Viewpoint Description
Table 46: Migration Viewpoint Description
Table 47: Implementation and Migration Viewpoint Description
Preface
The Open Group
The Open Group is a global consortium that enables the achievement of business objectives through technology standards. With more than 870 member organizations, we have a diverse membership that spans all sectors of the technology community – customers, systems and solutions suppliers, tool vendors, integrators and consultants, as well as academics and researchers.
The mission of The Open Group is to drive the creation of Boundaryless Information Flow™ achieved by:
• Working with customers to capture, understand, and address current and emerging requirements, establish policies, and share best practices
• Working with suppliers, consortia, and standards bodies to develop consensus and facilitate interoperability, to evolve and integrate specifications and open source technologies
• Offering a comprehensive set of services to enhance the operational efficiency of consortia
• Developing and operating the industry’s premier certification service and encouraging procurement of certified products
Further information on The Open Group is available at www.opengroup.org.
The Open Group publishes a wide range of technical documentation, most of which is focused on development of Open Group Standards and Guides, but which also includes white papers, technical studies, certification and testing documentation, and business titles. Full details and a catalog are available at www.opengroup.org/library.
This Document
This document is the ArchiMate® 3.2 Specification, a standard of The Open Group. It has been developed and approved by The Open Group.
This edition of the standard includes a number of corrections, clarifications, and improvements to the previous edition, as well as several additions.
Intended Audience
The intended audience of this standard is threefold:
• Those working to shape and implement complex organization change Typical job titles include Enterprise Architecture practitioners, Business Architects, IT architects, application architects, data architects, information architects, process architects, infrastructure architects, software architects, systems architects, solutions architects, product/service managers, senior and operational management, project leaders, and anyone working within the reference framework defined by an Enterprise Architecture.
• Those who intend to implement the ArchiMate language in a software tool They will find a complete and detailed description of the language in this document.
• The academic community, on which we rely for amending and improving the language based on state-of-the-art research in the architecture field.
Structure
The structure of this standard is as follows:
•Chapter 1, Introduction, provides the introduction to this standard, including the objectives, a brief overview, conformance requirements, and terminology
•Chapter 2, Definitions, defines the general terms used in this standard
•Chapter 3, Language Structure, describes the structure of the ArchiMate modeling language, including the top-level structure, layering, the ArchiMate Core Framework, and the ArchiMate Full Framework
•Chapter 4, Generic Metamodel, describes the structure and elements of the ArchiMate generic metamodel
•Chapter 5, Relationships and Relationship Connectors, describes the relationships in the language
•Chapter 6, Motivation Elements, describes the concepts for expressing the motivation for an architecture, together with examples
•Chapter 7, Strategy Layer, provides elements for modeling the enterprise at a strategic level, together with examples
•Chapter 8, Business Layer, covers the definition and usage of the Business Layer elements, together with examples
•Chapter 9, Application Layer, covers the definition and usage of the Application Layer elements, together with examples
•Chapter 10, Technology Layer, covers the definition and usage of the Technology Layer elements, together with examples
•Chapter 11, Relationships Between Core Layers, covers the relationships between different layers of the language
•Chapter 12, Implementation and Migration Layer, describes the language elements for expressing the implementation and migration aspects of an architecture (e.g., projects, programs, plateaus, and gaps)
•Chapter 13, Stakeholders, Architecture Views, and Viewpoints, describes the ArchiMate viewpoint mechanism
•Chapter 14, Language Customization Mechanisms, describes how to customize the ArchiMate language for specialized or domain-specific purposes
• Appendix A, Summary of Language Notation, is an informative appendix
• Appendix B, Relationships (Normative), is a normative appendix detailing the required relationships between elements of the language and the rules to derive these
• Appendix C, Example Viewpoints, presents a set of architecture viewpoints, developed in ArchiMate notation based on practical experience
All viewpoints are described in detail. The appendix specifies the elements, relationships, usage guidelines, goals, and target groups for each viewpoint.
• Appendix D, Relationship to Other Standards, Specifications, and Guidance Documents, describes the relationships of the ArchiMate language to other standards and specifications, including the TOGAF® framework, the BIZBOK® Guide, BPMN™, UML®, and BMM™
• Appendix E, Changes from Version 2.1 to Version 3.2, is an informative appendix outlining the changes in the standard between Version 2.1 and Version 3.2
Trademarks
ArchiMate, DirecNet, Making Standards Work, Open O logo, Open O and Check Certification logo, Platform 3.0, The Open Group, TOGAF, UNIX, UNIXWARE, and the Open Brand X logo are registered trademarks and Boundaryless Information Flow, Build with Integrity Buy with Confidence, Commercial Aviation Reference Architecture, Dependability Through Assuredness, Digital Practitioner Body of Knowledge, DPBoK, EMMM, FACE, the FACE logo, FHIM Profile Builder, the FHIM logo, FPB, Future Airborne Capability Environment, IT4IT, the IT4IT logo, O-AA, O-DEF, O-HERA, O-PAS, Open Agile Architecture, Open FAIR, Open Footprint, Open Process Automation, Open Subsurface Data Universe, Open Trusted Technology Provider, OSDU, Sensor Integration Simplified, SOSA, and the SOSA logo are trademarks of The Open Group.
A Guide to the Business Architecture Body of Knowledge and BIZBOK are registered trademarks of the Business Architecture Guild.
Java is a registered trademark of Oracle and/or its affiliates.
UML and Unified Modeling Language are registered trademarks and BMM, BPMN, Business Motivation Model, and Business Process Modeling Notation are trademarks of the Object Management Group.
All other brands, company, and product names are used for identification purposes only and may be trademarks that are the sole property of their respective owners.
Acknowledgements
The Open Group gratefully acknowledges The Open Group ArchiMate Forum for developing this standard.
The Open Group gratefully acknowledges the contribution of the following people in the development of this and earlier versions of this standard:
• Iver Band, EA Principals & Cambia Health Solutions
• Thorbjørn Ellefsen, Capgemini
• William Estrem, Metaplexity Associates
• Maria-Eugenia Iacob, University of Twente
• Henk Jonkers, BiZZdesign
• Marc M. Lankhorst, BiZZdesign
• Dag Nilsen, Biner
• Carlo Poli, Macaw
• Erik (H.A.) Proper, Luxembourg Institute for Science and Technology & Radboud University Nijmegen
• Dick A.C. Quartel, BiZZdesign
• G. Edward Roberts, Elparazim
• Jean-Baptiste Sarrodie, BNP PARIBAS
• Serge Thorn, Metaplexity Fellow
The Open Group gratefully acknowledges the ArchiMate User Community for providing feedback on previous versions of this standard and providing valuable input to The Open Group ArchiMate Forum. The Open Group and ArchiMate project team would like to thank in particular the following individuals for their support and review of this and earlier versions of this standard:
• Adina Aldea
• Mary Beijleveld
• Alexander Bielowski
• Remco de Boer
• Steven Bradley
• Adrian Campbell
• John Coleshaw
• Jörgen Dahlberg
• Garry Doherty
• Ingvar Elmér
• Wilco Engelsman
• Roland Ettema
• Henry M. Franken
• Mats Gejnevall
• David Gilmour
• Sonia González
• Kirk Hansen
• Jos van Hillegersberg
• Judith Jones
• Andrew Josey
• Maria Karancsi
• Neil Kemp
• Ryan Kennedy
• Rolf Knoll
• Louw Labuschagne
• Antoine Lonjon
• Kalin Maldzhanski
• Leos Mates
• Patrick Michels
• Steven Mileham
• Veer Muchandi
• Michelle Nieuwoudt
• Erwin Oord
• Antonio Plais
• Stephane Renaud
• Milan Rubeš
• Daniel Simon
• Sergey Startcev
• Ed Walters
• Gerben Wierda
• Egon Willemsz
The first version of this standard was largely produced by the ArchiMate project. The Open Group gratefully acknowledges the contribution of the many people – former members of the project team – who have contributed to it.
The ArchiMate project comprised the following organizations:
• ABN AMRO
• Centrum voor Wiskunde en Informatica
• Dutch Tax and Customs Administration
• Leiden Institute of Advanced Computer Science
• Novay
• Ordina
• Radboud Universiteit Nijmegen
• Stichting Pensioenfonds ABP
Referenced Documents
The following documents are referenced in this standard. These references are informative.
(Please note that the links below are good at the time of writing but cannot be guaranteed for the future.)
[1] Enterprise Architecture at Work: Modeling, Communication, and Analysis, Fourth Edition, M.M. Lankhorst et al., Springer, 2016.
[2] The Anatomy of the ArchiMate® Language, M.M. Lankhorst, H.A. Proper, H. Jonkers, International Journal of Information Systems Modeling and Design (IJISMD), 1(1):1-32, January-March 2010.
[3] Extending Enterprise Architecture Modeling with Business Goals and Requirements, W. Engelsman, D.A.C. Quartel, H. Jonkers, M.J. van Sinderen, Enterprise Information Systems, 5(1):9-36, 2011.
[4] TOGAF® Standard, 10th Edition, a standard of The Open Group (C220), April 2022, published by The Open Group; refer to: www.opengroup.org/library/c220.
[5] Extending and Formalizing the Framework for Information Systems Architecture, J.F. Sowa, J.A. Zachman, IBM Systems Journal, Volume 31, No. 3, pp.590-616, 1992.
[6] How to Use the ArchiMate® Modeling Language to Support the TOGAF® Standard, The Open Group Guide (G21E), April 2022, published by The Open Group; refer to: www.opengroup.org/library/g21e.
[7] Unified Modeling Language®: Superstructure, Version 2.0 (formal/05-07-04), Object Management Group, August 2005.
[8] Unified Modeling Language®: Infrastructure, Version 2.4.1 (formal/201-08-05), Object Management Group, August 2011.
[9] A Business Process Design Language, H. Eertink, W. Janssen, P. Oude Luttighuis, W. Teeuw, C. Vissers, in Proceedings of the First World Congress on Formal Methods, Toulouse, France, September 1999.
[10] Enterprise Business Architecture: The Formal Link Between Strategy and Results, R. Whittle, C.B. Myrick, CRC Press, 2004.
[11] Composition of Relations in Enterprise Architecture, R. van Buuren, H. Jonkers, M.E. Iacob, P. Strating, in Proceedings of the Second International Conference on Graph Transformation, pp.39-53, edited by H. Ehrig et al., Rome, Italy, 2004.
[12] Business Process Modeling Notation™ (BPMN™), Version 2.0 (formal/2011-01-03), Object Management Group, 2011.
[13] Performance and Cost Analysis of Service-Oriented Enterprise Architectures, H. Jonkers, M.E. Iacob, in Global Implications of Modern Enterprise Information Systems: Technologies and Applications, edited by A. Gunasekaran, IGI Global, 2009.
[14] ISO/IEC 42010:2011, Systems and Software Engineering – Recommended Practice for Architectural Description of Software-Intensive Systems, Edition 1.
[15] Business Motivation Model™ (BMM™), Version 1.1 (formal/2010-05-01), Object Management Group, 2010.
[16] Using the ArchiMate® Language with UML®, White Paper (W134), September 2013, published by The Open Group; refer to: www.opengroup.org/library/w134.
[17] TOGAF® Series Guide: Value Streams (G178), April 2022, published by The Open Group: refer to: www.opengroup.org/library/g178.
[18] Business Architecture Guild. A Guide to the Business Architecture Body of Knowledge® (BIZBOK® Guide), Version 7.0, 2018; refer to: www.businessarchitectureguild.org.
[19] TOGAF® Series Guide: The TOGAF® Technical Reference Model (TRM) (G175), September 2017, published by The Open Group: refer to: www.opengroup.org/library/g175.
[20] ArchiMate® Model Exchange File Format for the ArchiMate Modeling Language, Version 3.0, The Open Group Standard (C174), May 2017, published by The Open Group; refer to: www.opengroup.org/library/c174.
[21] TOGAF® Series Guide: Business Capabilities, Version 2 (G211), April 2022, published by The Open Group; refer to: www.opengroup.org/library/g211.
1 Introduction
1.1 Objective
This standard is the specification of the ArchiMate Enterprise Architecture modeling language, a visual language with a set of default iconography for describing, analyzing, and communicating many concerns of Enterprise Architectures as they change over time. The standard provides a set of entities and relationships with their corresponding iconography for the representation of Architecture Descriptions. The ArchiMate ecosystem also supports an exchange format in XML which allows model and diagram exchange between tools [20].
1.2 Overview
An Enterprise Architecture is typically developed because key people have concerns that need to be addressed by the business and IT systems within an organization. Such people are commonly referred to as the “stakeholders” of the Enterprise Architecture. The role of the architect is to address these concerns by identifying and refining the motivation and strategy expressed by stakeholders, developing an architecture, and creating views of the architecture that show how it addresses and balances stakeholder concerns. Without an Enterprise Architecture, it is unlikely that all concerns and requirements are considered and addressed.
The ArchiMate Enterprise Architecture modeling language provides a uniform representation for diagrams that describe Enterprise Architectures. It includes concepts for specifying inter-related architectures, specific viewpoints for selected stakeholders, and language customization mechanisms. It offers an integrated architectural approach that describes and visualizes different architecture domains and their underlying relations and dependencies. Its language framework provides a structuring mechanism for architecture domains, layers, and aspects. It distinguishes between the model elements and their notation, to allow for varied, stakeholder-oriented depictions of architecture information. The language uses service-orientation to distinguish and relate the Business, Application, and Technology Layers of Enterprise Architectures, and uses realization relationships to relate concrete elements to more abstract elements across these layers.
1.3 Conformance
The ArchiMate language may be implemented in software used for Enterprise Architecture modeling. For the purposes of this standard, the conformance requirements for implementations of the language given in this section apply. A conforming implementation:
1. Shall support the language structure, generic metamodel, relationships, layers, cross-layer dependencies, and other elements as specified in Chapters 3, 4, 5, 6, 7, 8, 9, 10, 11, and 12
2. Shall support the standard iconography as specified in Chapters 4, 5, 6, 7, 8, 9, 10, and 12, and summarized in Appendix A
3. Shall support the viewpoint mechanism as specified in Chapter 13
4. Shall support the language customization mechanisms as specified in
