Model Integration Guide for ArchiMate®
ArchiMate® to SpecIF mapping
Resources
| ArchiMate® Open Exchange (XML) | SpecIF |
|---|---|
| BusinessActor, BusinessRole, BusinessCollaboration, BusinessInterface, BusinessProcess, BusinessFunction, BusinessInteraction, BusinessService, ApplicationComponent, ApplicationCollaboration, ApplicationInterface, ApplicationFunction, ApplicationInteraction, ApplicationProcess, ApplicationService, Node, Equipment, Facility, DistributionNetwork, Device, SystemSoftware, TechnologyCollaboration, TechnologyInterface, Path, CommunicationNetwork, TechnologyFunction, TechnologyProcess, TechnologyInteraction, TechnologyService, OrJunction, AndJunction | FMC:Actor |
| Goal, Capability, Contract, Representation, Artefact, Product, BusinessObject, DataObject | FMC:State |
| BusinessEvent, ApplicationEvent, TechnologyEvent, ImplementationEvent | FMC:Event |
| Requirement, Constraint | IREB:Requirement |
| Location, Grouping | SpecIF:Collection |
Where:
- The listed elements are described in the ArchiMate® 3.1 Specification.
- All SpecIF resource class terms are defined in the Vocabulary.
- For all entities in the left column the namespace ‘archimate:’ is used; the XML header defines
xsi:schemaLocation="http://www.opengroup.org/xsd/archimate/3.0/ http://www.opengroup.org/xsd/archimate/3.1/archimate3_Diagram.xsd". - The original model element type is stored in a property named dcterms:type.
Statements
At present, the following statements are derived from ArchiMate® diagrams, where the statement terms (predicates) are highlighted in italics:
| ArchiMate® Open Exchange (XML) | SpecIF | Comment | |
|---|---|---|---|
| view | SpecIF:shows | ||
| Composition, Aggregation, Realization, Assignment | SpecIF:contains | ArchiMate® Structural (or ‘unifying’) Relationship | |
| Access (accessType:Write) | SpecIF:writes | ArchiMate® Dependency Relationship | |
| Access (accessType:Read) | SpecIF:reads | ArchiMate® Dependency Relationship | |
| Association | SpecIF:isAssociatedWith | ArchiMate® Dependency Relationship | |
| Influence | SpecIF:influences | ArchiMate® Dependency Relationship | |
| Serving | SpecIF:serves | ArchiMate® Dependency Relationship | |
| Flow, Triggering | SpecIF:precedes | ArchiMate® Dynamic Relationship | |
| Specialization | SpecIF:isSpecializationOf |
Where:
- The listed elements are described in the ArchiMate® 3.1 Specification.
- All SpecIF statement class terms are defined in the Vocabulary.
- For all entities in the left column the namespace ‘archimate:’ is used; the XML header defines
xsi:schemaLocation="http://www.opengroup.org/xsd/archimate/3.0/ http://www.opengroup.org/xsd/archimate/3.1/archimate3_Diagram.xsd". - The original model element type is stored in a property named dcterms:type.
Example
ArchiMate® 3.1 defines numerous viewpoints, 25 in total. Two typical ones are chosen to demonstrate an ArchiMate® to SpecIF transformation.
Layered Viewpoint
The following clipping from ArchiMate® Layered Viewpoint represents two data objects, one system service, two application components and a node:
The following SpecIF graph expresses the same:
Information Structure Viewpoint
The following clipping from ArchiMate® Information Structure Viewpoint represents five data objects similar to a UML Class Diagram:
The following SpecIF graph expresses the same:
Full Example
The full example can be inspected, here:
- Telephone Connection Request (Open-Exchange XML)
- Telephone Connection Request (SpecIF)
- Telephone Connection Request (SpecIF-Viewer)
Transformation Code
Here you may look at the current code of the ArchiMate® to SpecIF transformation.