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.