Upper ArchiMate Ontology
The upper level ArchiMate abstract MetaModel provides a framework for the implementation of ArchiMate® formalism in Hopex.
ArchiMate Upper Ontology abstract MetaModel
ArchiMate Model (on the left side of the figure) is the container which owns the concepts. The main concepts are: ArchiMate Concept and ArchiMate Elements.
ArchiMate Concept is the root abstract MetaClass of the MetaModel.
ArchiMate Concept has two sub MetaClasses:
• ArchiMate Elements, see "ArchiMate Elements", page 61,
• ArchiMate Concept Relationships, see "ArchiMate Concept Relationships", page 61.
ArchiMate Elements
ArchiMate Elements MetaClass gathering all the ArchiMate® elements implemented to get Hopex for the ArchiMate® Framework. To manage the bridge with Hopex for the ArchiMate® Framework and other Hopex products and concepts, ArchiMate Elements MetaClass is divided into sub-MetaClasses:
• ArchiMate Standalone Elements for the concepts which are ArchiMate® specific. For more details, see "Creating ArchiMate Standalone Elements", page 31.
• ArchiMate EA Elements for the concepts which can refer to existing Hopex Building Blocks used in other Hopex solutions. For example:
• Application Component refers to an Hopex Application (available in Hopex Business Process Analysis or Hopex IT Architecture)
• ArchiMate Work Package refers to an Hopex Enterprise Project (available in HOPEX Project Portfolio Management)
These EA Elements have a specific behavior for creation and deletion. For more details, see "Creating an ArchiMate EA Element", page 32.
ArchiMate Concept Relationships
ArchiMate Concept Relationships MetaClass is divided into sub-MetaClasses:
• ArchiMate Association: a specific Relationship which can associate any concepts (including other Relationships),
• ArchiMate Element Relationship: gathering all ArchiMate Relationships, sorted by subtypes, for example: ArchiMate Composition or ArchiMate Aggregation.
