I’ve created a PDF that you can print two sided (and laminate if you like) to have easy access to the ArchiMate 3 metamodel.
On the front it contains the Core meta-model. It is depicted in the Mastering ArchiMate colour scheme (this link gets you to a depiction of the ArchiMate 1 metamodel, which also illustrates how much ArchiMate has grown over the years), which shows both differences between the layers and the aspects (active structure, behaviour, passive structure). I use that colour scheme because it tends to be easier to grasp diagrams if the different aspects are shown in different colours. It also helps in explaining the language. There is a layered-colour version as well, see below.
I have expanded any non-usable element (Technology Object, which is an abstraction in the meta-model that cannot be used directly, only its subtypes Artifact and Material can) and replicated the relations that come from it so the sheet only shows real meta-model elements that you can use in models (and their direct relations, except the always allowed Composition/Aggregation from an element type to itself). I’ve used a bit of colour coding and labeling of the relations. It also shows all the cross-layer direct relations.
I’ve also left out all Collaborations and Interactions. Most can now be expressed by using Junction on relations and using just the above set. I still need to add that remark to the diagram.
Note, the blue relation on the left is mentioned in the text of the standard but not shown in the figure that accompanies the text and also not in the table at the end. Technically that means it is not a direct relation in ArchiMate, but I think this is an omission. It is debatable, though, so this may change in the future.
On the second page (back), the other domains of ArchiMate are shown. First Motivation:
Again, except for refering to the rest of the meta-model, I only show real element types. I’ve left out all the possible Influence relations (though they are mentioned) and again the always allowed Composition/Aggregation from an element type to itself. “Any Structural of Behavioural Element” is a reference to the meta-meta-model. It is assumed the reader knows what this means (in Core, Strategy and Implementation & Migration domains).
I’ve used my Core colour coding to signal which parts of the Core meta-model can Realise which element of the Strategy domain (which the standard calls a ‘layer’).
And Implementation and Migration:
Here, I used a grey diamond on relations to signal they may either be a Composition or an Aggregation. Again, self-referenced Composition and Aggregation are not shown.
Finally, the Composite Elements are shown:
The PDF is fully vector, so it can scale to unlimited size without becoming pixelated. Print it on a banner the size of a house and drape it in your conference venue 🙂
And for those that like the layered colour view that doesn’t differentiate between the core aspects. Here is a link to a PDF that shows the same in that colour scheme. The front side looks like this:
A view elements are also displayed differently (Service, Application Component, Device). This is (except Contract which came up in green) the default visualisation of BiZZdesign Enterprise Studio 2.1.0.
[Updated on Sep 10 2016. A few labels were fixed.]
[Updated on Sep 25 2016 – Main changes: Left-to-Right orientation, several relations fixed, changed colouring on relations, better explanation of Specialisation]