Skip to end of metadata
Go to start of metadata

The metamodels in Enterprise Studio have different object and relation types. All types have a type name and many of them (not all) also have a translation. The type name is a concept name, mostly hidden to the user. The type names are used in the Metamodeler and the Metamodel Browser, but also when scripting or when working with the BiZZdesign Open API. The translation is the name that is visible to the user when working with models. A few examples:

  • ArchiMate® object business actor: Type name is BusinessActor, translation is Business actor.
  • ArchiMate total view extended: Type name is AllExtendedView, translation is Total view extended.
  • ArchiMate application layer: Type name is ApplicationScheme, translation is Application layer.
  • BPMN object call activity: Type name is BPMN_CallActivity, translation is Call activity.
  • BPMN process diagram: Type name is BPMN_ProcessScheme, translation is Process diagram.

Concrete types and abstract types

The object and relation types can be categorized in abstract types and concrete types. Concrete types are single-object types and are listed by the Metamodel Browser. They can also be found in the Metamodeler. Concrete types, apart from folders, are derived (directly or indirectly) of one of the abstract base types. Abstract types can be divided in abstract types that can be instantiated but are not listed by the Metamodel Browser, and abstract types that cannot themselves be instantiated but serve as base type for other concepts that can.

Type names of the concrete object and relation types can be found in the Metamodel Browser and the Metamodeler. The abstract base types can only be found in a metamodel package of the Metamodeler.


Example of type names of concrete ArchiMate object types


Below is an overview of the abstract base types, they can serve as a starting point for finding name types of an object or relation in a metamodel, or be used themselves.

Abstract base types

Types that can be instantiated, but are not listed by the Metamodel Browser
AbstractFolderThe type of a folder inside a model.
CommandDefinitionA stored viewpoint (e.g. a color view filter, or a script).
CommandFolderA folder that stores viewpoints (displayed as a folder when the Viewpoints panel is in edit mode, and as a section when in normal mode).
MM_FolderThe type of a folder outside all models (i.e. a folder under the model package, that contains models).
MM_ModelPackageThe type of the model package root object (of which there is exactly one in a model package).
ViewChartA chart. The actual type of the chart is determined by its properties.
ViewEdgeA graphical line, as drawn using the Edge graphic shape in the "Graphic shapes" section of the Create pane.
ViewGraphicA graphical shape, as drawn using one of the shapes in the "Graphic shapes" section of the Create pane. Its appearance is determined by its properties.
ViewHyperlinkA hyperlink object, as drawn using the "Hyperlink" graphic shape in the "Graphic shapes" section of the Create pane.


Abstract types that cannot themselves be instantiated, but serve as base type for other concepts that can
AbstractCompoundBase type of concepts that can be placed on a view, and can be nested semantically (i.e. in the model browser).
AbstractConnectorBase type of Junction and Or Junction (in ArchiMate). These objects are always located directly below the model package.
AbstractDependencyRelationBase type of cross-model relationships.
AbstractElementBase type of concepts that can be placed on a view, and cannot be nested semantically (e.g. an Action in Amber).
AbstractMemberBase type of concepts that cannot exist unless part of another concept (e.g. a UML Attribute).
AbstractRelationBase type of relationships inside a metamodel (i.e. all except cross-model relationships).
AbstractSchemeBase type of all layers, mostly interchangeable with its direct subtype SemanticScheme.
AbstractViewBase type of all views.
MM_ModelBase type of all models. Each metamodel defines its own dedicated subtype by prepending the metamodel name, e.g. ArchiMateMM_Model.
MM_ObjectBase type of all objects, including relationships.
MM_RefObjectBase type of all object references (on a view). The script language accepts "Reference" as an alias for this type.
MM_RelationBase type of all relationships (including cross-model relations). The script language accepts "Relation" as an alias for this type.
SemanticSchemeBase type of all layers, mostly interchangeable with its direct supertype SemanticScheme.
SemanticViewBase type of views that are associated with one (and exactly one) layer, e.g. a process diagram in Amber or BPMN.


ArchiMate® is a registered trademark of The Open Group.