by Phil Chudley, Principal Consultant at Dunstan Thomas Consulting
The Open Group released the official specification of ArchiMate 3.0 in June 2016, and this new specification is supported in Enterprise Architect version 13. This article summarises the new features and changes within ArchiMate 3.0 and provides an example of how to migrate an existing ArchiMate 2.0 model to ArchiMate 3.0 model using Enterprise Architect v.13.
Summary of Changes
The following is a summary of the changes made within ArchiMate 3.0:
- Motivation Extension;
- New element for modelling Outcomes.
- New set of Strategy Elements, Resource, Capability, Course of Action.
- Business Layer;
- Representation of the Contract element modified so as to be different from the Business Object Element.
- Location element removed (although Enterprise Architect has re-located this element to the Technology Layer – Physical Extension).
- Application Layer;
- Two new elements added, Application Process and Application Event
- Technology layer;
- Elements called Infrastructure in ArchiMate 2.0 are now called Technology in ArchiMate 3.0.
- Four new elements added, Technology Process, Technology Interaction, Technology Event and Technology Collaboration.
- New set of Physical Elements, Equipment, Facility, Distribution Network and Material. These elements are known as the Physical Extension.
- Implementation and Migration Extension;
- One new element added, Implementation Event.
- Representation of Assignment modified to have a directional arrow.
- Bi-directional Access relationship added.
- Plus (positive) and Minus (negative) symbols added to Influence Relationship.
- New relationship, Serving.
Detail of Changes
The following tables provided an example of the changes for each of the sections listed in the Summary of Changes above.
|Outcome||An end result that has been achieved.|
|Resource||An asset owned or controlled by an individual or organisation.|
|Capability||An ability that an active structure element, such as an organisation, person, or system possesses.|
|Course of Action||An approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal.|
|Contract||A formal or informal specification of an agreement between a provided and consumer that specifies the rights and obligations associated with a product.|
|Application Process||A sequence of application behaviours that achieves a specific outcome.|
|Application Event||An application behaviour element that denotes a state change.|
|Technology Collaboration||An aggregate of two or more nodes that work together to perform collective technology behaviour.|
|Technology Process||A sequence of technology behaviours that achieves a specific outcome.|
|Technology Event||A technology behaviour element that denotes a state of change.|
|Technology Interaction||A unit of collective technology behaviour performed by (a collaboration of) two or more nodes.|
|Equipment||One or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.|
|Facility||A physical structure or environment.|
|Distribution Network||A physical network used to transport materials or energy.|
|Material||Tangible physical matter or physical elements.|
Implementation & Migration Extension
|Implementation Event||A behaviour element that denotes a change of state related to an implementation or migration.|
|Assignment||Expresses the allocation of responsibility, performance of behaviour, or execution.|
|Serving||Models that an element provides its functionality to another element.|
|Access||Models the ability of behaviour and active structure elements to observe or act upon passive structure elements.|
|Influence||Models that an element affects the implementation or achievement of some motivation element.|
Implications to existing ArchiMate models
If an organisation has modelled their Enterprise Architecture using Enterprise Architect and ArchiMate 2, and are now using Version 13 of Enterprise Architect, they have two courses of action:
- Continue to model using ArchiMate 2.0. In this case no action is required either for Enterprise Architect or the model repository. An organisation would continue to model using ArchiMate 2.0 if they do not wish to make use of any of the new features in ArchiMate 3.0.
- Migrate their existing ArchiMate 2.0 model to ArchiMate 3.0, and then continue to model using ArchiMate 3.0. An organisation would continue to model using ArchiMate 2.0 if they wish to make use of any of the new features in ArchiMate 3.0.
My own personal opinion is that an organisation should consider moving to Enterprise Architect version 13 (mainly due its new feature of “Time Aware Modelling”) and ArchiMate 3.0. One of the main reasons, is due to inherent ambiguity (due to the lack of direction indication) in the assigns relationship in ArchiMate 2.0, which has been eliminated in ArchiMate 3.0 by making the assigns relationship directional.
Migrating an ArchiMate 2.0 model to ArchiMate 3.0
Enterprise Architect version 13 provides a migration script for this purpose. The following steps are used to perform the migration:
- Take a backup copy of the existing model repository.
- Using the Configure | Manage Technology ribbon, ensure that both ArchiMate 2.0 and ArchiMate 3.0 MDG technologies are enabled.
- Using the Code | Scripting ribbon, make the scripting window visible:
- Select the topmost package (or view) that contains the model to migrate:
- Select the script Migrate ArchiMate 2 to ArchiMate 3 in the scripting window.
- Right-click and select Run Script from the menu.
- The progress of the migration, together with any errors / warnings will be displayed in the system output window.
- Review the diagrams (you may have to tidy some of the relationships).
- Turn off the MDG ArchiMate 2.0 using the Configure | Manage Technology ribbon.
NOTE: It appears that composition relationships are NOT HIDDEN, when using nested structures in ArchiMate 3.0. I suspect this is an Enterprise Architect version 13 issue. This is likely to be fixed and should not deter migration, as these relationships can always be hidden using the Visible Relations function in Enterprise Architect. (Layout | Manage ribbon and select Show and Hide Relationships… from the menu).
Dunstan Thomas Consulting
You'll find lots of useful Enterprise Architect videos on our YouTube Channel.