ArchiMate support
Support of the ArchiMate standard
by Modelio BA - Enterprise Architect
The table below presents Modelio BA - Enterprise Architect's support of the ArchiMate standard.
Please note that wherever there is a discrepancy between names, TOGAF terms have been chosen over ArchiMate terms.
Notations are primarily based on the UML and BPMN standards.
| ArchiMate notion | Enterprise Architect notion |
Comments | Notation |
| Business Layer | |||
| Business actor | Actor | Internal actor and external actor | |
| Business role | Role | ||
| Business collaboration | Business collaboration | ||
| Business interface | No real usage identified | ||
| Location | Location | Headquarters and sites | |
| Business object | Business entity | ||
| Business process | Business process | ||
| Business function | Function | ||
| Business interaction | Business interaction | ||
| Business event | Event | ||
| Business service | Business service | ||
| Representation | No real usage identified | ||
| Meaning | Term | This notion is little developed in ArchiMate, but extensively developed in the Modelio "dictionary" | |
| Value | Value factor on Function | ||
| Product | Product | TOGAF semantics supported | |
| Contract | Service contract | Pre-conditions, post-conditions, invariant | |
| Architecture Layer | |||
| Application component | Application component | Modelio BA - Enterprise Architect breaks components down using component typology to facilitate sound SOA structuring | |
| Application collaboration | Application collaboration | ||
| Application interface | Required or provided services | ||
| Data object | Entity | ||
| Application function | No real usage identified. Antinomic TOGAF and SOA. | ||
| Application interaction | UML interaction on collaboration | ||
| Application service | Information service | ||
| Technical Layer | |||
| Node | Node | Generic element | |
| Device | Server, workstation, ... | More detailed list on Modelio BA - Enterprise Architect | |
| Network | Bus | ||
| Communication path | Network link | ||
| Infrastructure interface | Port | ||
| System software | Utility component | ||
| Infrastructure function | No real usage identified. Antinomic TOGAF and SOA. | ||
| Infrastructure service | IS service | ||
| Artifact | Technology artifact | ||
| Relationships | |||
| Association | Association | ||
| Access | Flow | ||
| Use by | Consumes | "Consumes" is reserved for actors. For other elements, backwards "supports" links. | |
| Realization | Component realization | Specialized in Modelio BA - Enterprise Architect on components | |
| Assignment | Initiator of; participates in; owner of | Modelio BA - Enterprise Architect provides more specialized links | |
| Aggregation | Aggregation | ||
| Composition | Composition | ||
| Flow | Flow | ||
| Triggering | Flow | ||
| Grouping | Packages and embedding | ||
| Junction | BPMN junction | ||
| Specialization | Generalization | ||
| Extensions (motivation) | |||
| Language extension mechanisms | Profiles, MDA | ||
| Driver, Goal | Goals | Detailed by specific properties and diagrams in Modelio. The distinction between Driver and Goal can be made through different "containers" or by using specific properties. | |
| Requirement | Requirements | Detailed by specific properties and diagrams in Modelio | |
| Aggregation | Part | ||
| Realization | Satisfies | OMG SysML norm | |
| Influence | +influence; -influence | ||
| Aggregation | Aggregation | ||
| Deployment | Modelio BA - Enterprise Architect enables application components to be directly deployed on nodes. | ||