|
ArchiMate Concept
|
HOPEX Concept
|
Alias
|
Comment
|
|
Business Actor
|
Org-Unit
|
Business Actor
|
|
|
Business Role &
Business Collaboration
|
Business Function
|
Business Role
|
The same HOPEX metaclass is used for both concepts, so relations are the same for a role and a collaboration. For example, you can connect a collaboration to an actor.
|
|
Business Interface
Application Interface
Infrastructure Interface
|
Service Point
Request Point
|
Provided Interface
Required Interface
|
|
|
Business Service
Application Service
Infrastructure Service
|
Exchange
|
Service
|
The same HOPEX metaclass is used for the three concepts. A specific typing attribute is used to differentiate the instances.
|
|
|
Exchange Contract
|
Interface Protocol
|
Interactions between usage of communicating objects or between interfaces rely on interface protocols; interface protocols are supported by interfaces.
|
|
Application Component
System Software
|
Application
|
Application component
|
The same HOPEXmetaclass is used for the two concepts.
The connexion with an interface is managed by a specific path.
|
|
Application Collaboration
|
Application Collaboration
|
Application system
|
The connexion with an interface is managed by a specific path.
|
|
Business Process
Business Function
Business Interaction
|
Functional Process
|
Business Process
|
In HOPEX, this covers the functional aspects of processes.
|
|
|
Functional Activity
|
Business Activity
|
Step in a Business process. Corresponds to a BPMN activity
|
|
Business Process
|
Organizational Process
|
Org Process
|
In HOPEX, this defines the implementation of a business process in a given context.
|
|
|
Operation
|
Org activity
|
Step in a Business process. Corresponds to a BPMN activity
|
|
Business Event Interface
|
Event
|
Business Event
|
|
|
Business Object
|
Concept
|
|
Note: in process diagrams (business process and org process viewpoints), business objects can be encapsulated within "objects" and linked to the carried products. A specific wizard enables the link creation
|
|
Product
|
Content
|
Product
|
Note: contents can be linked to flows for instance to detail the carried information content; products are therefore used in a broader sense of "work product" here
|
|
Contract
|
Not implemented
|
|
|
|
Meaning
|
Not implemented
|
|
|
|
Representation
|
Not implemented
|
|
|
|
Application Function
Application Interaction
Infrastructure function
|
System Process
|
IT Function
|
Note: the alias is kept generic for this can be used for infrastructure as well
|
|
|
Task
|
IT Activity
|
Step in a IT function process; corresponds to a BPMN Activity
|
|
Data Object
|
Entity(DM)
|
Data Object
|
In process diagrams (application behavior viewpoint), data objects can be encapsulated within "objects" and linked to the carried products. A specific wizard enables the link creation
|
|
|
Data Store
|
Information Store
|
Information Store can be used within an Application Component to host data objects (via information model)
|
|
|
Application Data Store
|
Application Component Information Store
|
Information Store can be used within an Application Component to host data objects (via information model)
|
|
|
Data Model
|
Information Model
|
An information model is described by the Information Structure viewpoint and contains data objects. It is linked to a Information Store.
|
|
Value
|
Not implemented
|
|
|
|
Artifact
|
Artifact (UML)
|
Artifact
|
|