EA Toolsets project : MetaExamples

This is an old revision of MetaExamples from 2009-05-24 19:47:43.

[ OsEATools | MetaModel | Metamodel - real-world examples | Categories ]

Metamodel - real-world examples

Rows - layers of abstraction

Each of the seven rows represents a layer of abstraction (see rows).

The following ArchiMate relations are allowed between rows:

realization - each abstraction needs to be 'realized' by entities in the layers below (i.e. realizations always occur 'downward' between the layers)
specialization - some specializations are also realizations, in that they 'realize' an abstract class (such specializations also move 'downward' between layers - though note that unlike realizations, specializations may also occur within a layer)
association - association is the general 'none of the above' relation in ArchiMate, with a semantic meaning that must be explicitly assigned - in some cases these may traverse between layers

Other ArchiMate relations (triggering, flow, aggregation, composition, assignment, used by, access) are allowed only within a row.

Columns and segments - primitives and base-composites

All of the columns (see columns) are abstractions. True primitives within a column may exist in the higher layers (row-0 to row-2 and sometimes row-3), but as we move towards the real world even entities which exist within a single column must be linked with one or more appropriate category-segments (see type or skill) as base-composites.

A primitive cannot be split any further; a composite may be split and recombined in other ways (in theory, at least, if not always in practice). Recombination enables redesign.

The Archimate relations may be used within and between columns as per the Archimate specification.

Assets

An asset is an entity (or Concept, in the Archimate base-ontology) for which the organisation is responsible and which it may access or use in functions. (A liability is an asset which has, for the moment, been assigned a negative value, and/or is required to be available to transfer to others at some future time.)

Some examples:

device (computer, vehicle, machine-tool etc) - asset>physical, with implied capability of at least the same category
data - asset>virtual, also in narrative form as information held by person, as asset>virtual+relational
paper form - asset>physical+asset>virtual
person - implied via asset>relational, usually also assigned to some role (note: it is the relationship with the person that is the asset, not the actual person - by intent, real persons do not fit direct directly into this categorisation schema, and should never be described directly as 'assets')
customer record - data about relation, hence asset>virtual <- asset>relational