Linked.Archi ArchiMate ontology based on the ArchiMate 3.2 specification. Represents ArchiMate elements, relationship types (using the three-declaration qualified relationship pattern), and composite/connector concepts as RDF/OWL. Version 3.2 modernizes the ontology to current Linked.Archi conventions and RDF 1.2 rdf:reifies.
Linked.Archi ArchiMate ontology aligned to the ArchiMate 3.2 specification, modernized to conform to Linked.Archi core ontology conventions, the qualified relationship pattern, and RDF 1.2. This is not an official Open Group document.
Linked.Archi
Linked.Archi ArchiMate 3.2 Ontology
3.2.0: Modernized to current Linked.Archi conventions. Replaced legacy relationship declarations with three-declaration qualified relationship pattern. Added qualified relationship classes (: namespace) and qualified properties. Replaced rdfs:label with skos:prefLabel, arch:specURL with dcterms:source. Added RDF 1.2 rdf:reifies bridge in relationship examples. Updated license to CC-BY 4.0. Aligned all elements with archimate-tax ontology (:).
This namespace (archimate/onto#) covers ArchiMate 3.x (versions 3.0, 3.1, 3.2). ArchiMate 2.x used a substantially different metamodel (different element names, relationship rules, and layer structure) and is not represented here. A future ArchiMate 4.x major revision may introduce a separate namespace if the metamodel changes are breaking.
Indicates that a behavior element may access a business or data object.
Accesses
Indicates that an element combines one or more other elements.
Aggregates
3.0: Directional notation introduced (arrow replaces black circle at 'to' end).
Indicates the allocation of responsibility, performance of behavior, storage, or execution.
Assigned To
Indicates an unspecified relationship, or one that is not represented by another ArchiMate relationship.
Associated With
Indicates that an element consists of one or more other elements.
Composed Of
Indicates transfer from one element to another.
Flows To
3.0: Notation changed for consistency with other dependency relationships (access and serving).
Indicates that an element affects the implementation or achievement of some motivation element.
Influences
Navigates from a source element to an Access qualified relationship resource. The Access resource carries the accessType (Read, Write, ReadWrite).
ex:OrderProcess am:qualifiedAccesses ex:qr-006 . ex:qr-006 a am:Access ; arch:source ex:OrderProcess ; arch:target ex:CustomerData ; am:accessType "ReadWrite" .
qualified Accesses
Navigates from a source element to an Aggregation qualified relationship resource.
ex:Department1 am:qualifiedAggregates ex:qr-002 . ex:qr-002 a am:Aggregation ; arch:source ex:Department1 ; arch:target ex:Team1 .
qualified Aggregates
Navigates from a source element to an Assignment qualified relationship resource. Assignment links active structure elements with behavior they perform, or actors with roles they fulfill.
ex:DevTeam am:qualifiedAssignedTo ex:qr-003 . ex:qr-003 a am:Assignment ; arch:source ex:DevTeam ; arch:target ex:DeploymentProcess .
qualified Assigned To
Navigates from a source element to an Association qualified relationship resource. Association is the most generic relationship — used when no more specific type applies.
ex:Stakeholder1 am:qualifiedAssociatedWith ex:qr-011 . ex:qr-011 a am:Association ; arch:source ex:Stakeholder1 ; arch:target ex:Driver1 .
qualified Associated With
Navigates from a source element to a Composition qualified relationship resource. Use this to reach the full relationship object with metadata, provenance, and lifecycle state.
ex:System1 am:qualifiedComposedOf ex:qr-001 . ex:qr-001 a am:Composition ; arch:source ex:System1 ; arch:target ex:Module1 .
qualified Composed Of
Navigates from a source element to a Flow qualified relationship resource. Flow indicates transfer of information, goods, or money.
ex:Invoicing am:qualifiedFlowsTo ex:qr-009 . ex:qr-009 a am:Flow ; arch:source ex:Invoicing ; arch:target ex:Payment ; skos:prefLabel "Invoice data flow"@en .
qualified Flows To
Navigates from a source element to an Influence qualified relationship resource. The Influence resource carries the influenceStrength (+, ++, -, --).
ex:CostReduction am:qualifiedInfluences ex:qr-007 . ex:qr-007 a am:Influence ; arch:source ex:CostReduction ; arch:target ex:Profitability ; am:influenceStrength "++" .
qualified Influences
Navigates from a source element to a Realization qualified relationship resource. Realization links a concrete element with a more abstract element it realizes.
ex:PaymentSvc am:qualifiedRealizes ex:qr-004 . ex:qr-004 a am:Realization ; arch:source ex:PaymentSvc ; arch:target ex:PaymentCapability .
qualified Realizes
Navigates from a source element to a Serving qualified relationship resource. Serving indicates that an element provides its functionality to another.
ex:AppSvc1 am:qualifiedServes ex:qr-005 . ex:qr-005 a am:Serving ; arch:source ex:AppSvc1 ; arch:target ex:BizProc1 ; rdf:reifies <<( ex:AppSvc1 am:serves ex:BizProc1 )>> ; prov:wasDerivedFrom ex:diagramEdge-81 .
qualified Serves
Navigates from a source element to a Specialization qualified relationship resource. Specialization indicates that an element is a particular kind of another.
ex:OnlineBanking am:qualifiedSpecializes ex:qr-010 . ex:qr-010 a am:Specialization ; arch:source ex:OnlineBanking ; arch:target ex:BankingService .
qualified Specializes
Navigates from a source element to a Triggering qualified relationship resource. Triggering indicates a temporal or causal dependency.
ex:OrderReceived am:qualifiedTriggers ex:qr-008 . ex:qr-008 a am:Triggering ; arch:source ex:OrderReceived ; arch:target ex:FulfillmentProcess .
qualified Triggers
Indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity.
Realizes
3.0: Renamed from 'Used By' to 'Serves', in line with the other active names of relationships.
Indicates that an element provides its functionality to another element.
Serves
Indicates that an element is a particular kind of another element.
Specializes
Indicates a temporal or causal relationship between elements.
Triggers
Specifies the type of access: read, write, read-write, or unspecified.
Access Type
Specifies the strength or sign of an influence (e.g., +, ++, -, --).
Influence Strength
An access relationship indicates that a behavior element may access a business or data object. The accessType property specifies read, write, read-write, or unspecified.
Access
Active structure elements are the subjects that can perform behavior.
ActiveStructureElement
Superclass for all performers: internal active structure (actors, components, nodes) and external active structure (interfaces). Also includes paths and communication networks. SHACL shapes use this class to enforce that assignment originates from active structure.
An aggregation relationship indicates that an element combines one or more other elements. Unlike composition, the aggregated element can exist independently.
Aggregation
An application collaboration represents an aggregate of two or more application components that work together to perform collective application behavior.
Application Collaboration
Application
Software Component
An application component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.
Application Component
An application event is an application behavior element that denotes a state change.
Application Event
App Function
An application function represents automated behavior that can be performed by an application component.
Application Function
An application interaction represents a unit of collective application behavior performed by (a collaboration of) two or more application components.
Application Interaction
API
App Interface
An application interface represents a point of access where application services are made available to a user, another application component, or a node.
Application Interface
ApplicationLayerElement
Layer marker for application domain elements. Serves Business layer, realized by Technology layer.
App Process
3.0: Introduced to increase regularity across layers.
An application process represents a sequence of application behaviors that achieves a specific outcome.
Application Process
Software Service
An application service represents an explicitly defined exposed application behavior.
Application Service
Binary
Deployment Unit
Package
An artifact represents a piece of data that is used or produced in a software development process, or by deployment and operation of an IT system.
Artifact
An assessment represents the result of an analysis of the state of affairs of the enterprise with respect to some driver.
Assessment
An assessment may reveal strengths, weaknesses, opportunities, or threats for some area of interest. These need to be addressed by adjusting existing goals or setting new ones, which may trigger changes to the Enterprise Architecture.
An assignment relationship indicates the allocation of responsibility, performance of behavior, storage, or execution.
Assignment
An association relationship indicates an unspecified relationship, or one that is not represented by another ArchiMate relationship.
Association
Behavior elements represent the dynamic aspects of the enterprise.
BehaviorElement
Superclass for all behavior: internal behavior (processes, functions, interactions), external behavior (services), and events. SHACL shapes use this class to enforce that triggering and flow relationships connect behavior elements only.
Department
Organization
Person
A business actor is a business entity that is capable of performing behavior.
Business Actor
A business collaboration is an aggregate of two or more business internal active structure elements that work together to perform collective behavior.
Business Collaboration
A business event is a business behavior element that denotes an organizational state change.
Business Event
Function
A business function is a collection of business behavior based on a chosen set of criteria, closely aligned to an organization, but not necessarily explicitly governed by the organization.
Business Function
A business interaction is a unit of collective business behavior performed by (a collaboration of) two or more business roles.
Business Interaction
A business interface is a point of access where a business service is made available to the environment.
Business Interface
BusinessLayerElement
Layer marker for business domain elements. Served by Application layer elements.
Information Object
A business object represents a concept used within a particular business domain.
Business Object
Process
Workflow
A business process represents a sequence of business behaviors that achieves a specific outcome such as a defined set of products or business services.
Business Process
Role
A business role represents the responsibility for performing specific behavior, to which an actor can be assigned, or the part an actor plays in a particular action or event.
Business Role
Service
A business service represents an explicitly defined exposed business behavior.
Business Service
Business Capability
3.0: Introduced as part of the new Strategy layer.
A capability represents an ability that an active structure element, such as an organization, person, or system, possesses.
Capability
Capabilities help reduce the gap between strategic goals and implementable architecture by focusing on business outcomes. They are typically realized by a combination of organization, people, processes, information, and technology.
An aggregate of two or more internal active structure elements working together.
Collaboration
Collaborations aggregate roles or actors that perform collective behavior (interactions). They are temporary or permanent groupings aimed at specific interactions.
LAN
Network
WAN
3.2: Icon notation changed.
A communication network represents a set of structures that connects computer systems or other electronic devices for transmission, routing, and reception of data.
Communication Network
Composite elements consist of other concepts, possibly from multiple aspects or layers.
CompositeElement
Elements that cross aspect boundaries: products (bundle services and objects), groupings (generic containers), locations (physical or logical places), and plateaus (stable architecture states).
A composition relationship indicates that an element consists of one or more other elements. The contained element exists only within the context of the container.
Composition
3.2: Definition improved.
A constraint represents a factor that prevents or obstructs the realization of goals.
Constraint
A constraint does not prescribe intended functionality but imposes a restriction on the way the system operates or may be realized.
A contract represents a formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product.
Contract
Core layers are Business, Application, and Technology (including Physical).
CoreLayerElement
Superclass for the three core layers. SHACL shapes use this to enforce cross-layer relationship direction rules (e.g., serving flows from lower to higher layers).
A course of action is an approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal.
Course of Action
Courses of action can be categorized as strategies and tactics. Strategies tend to be long-term and broad in scope, while tactics tend to be shorter-term and narrower.
Data Asset
Data Entity
A data object represents data structured for automated processing.
Data Object
A deliverable represents a precisely-defined outcome of a work package.
Deliverable
Hardware
Physical Server
3.2: No longer a subtype of Node; now a subtype of technology internal active structure element, with composition and aggregation relationships to Node.
A device is a physical IT resource upon which system software and artifacts may be stored or deployed for execution.
Device
3.0: Introduced as part of the new Physical layer.
A distribution network represents a physical network used to transport materials or energy.
Distribution Network
A driver represents an external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them.
Driver
Drivers may be internal, in which case they are usually associated with a stakeholder, and are often called "concerns". Examples of internal drivers are Customer satisfaction and Profitability. Drivers of change may also be external; e.g., economic changes or changing legislation.
Machine
Physical Device
3.0: Introduced as part of the new Physical layer. 3.2: No longer a subtype of Node; now a subtype of technology internal active structure element, with composition and aggregation relationships to Node.
Equipment represents one or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.
Equipment
An event represents a state change.
Event
Events are instantaneous — they trigger or are triggered by other behavior via triggering relationships. They can be external (received from outside) or internal (produced by a process).
An external active structure element (interface) represents a point of access.
ExternalActiveStructureElement
Interfaces expose services to the environment and hide internal complexity. Typically composed by the internal active structure element they belong to. Assigned to the services they expose.
An external behavior element (service) represents explicitly defined exposed behavior.
ExternalBehaviorElement
Services are the externally visible behavior offered to consumers. Realized by internal behavior and exposed through interfaces. Connected to consumers via serving relationships.
Building
Data Center
Site
A facility represents a physical structure or environment.
Facility
A flow relationship indicates transfer from one element to another.
Flow
A gap represents a statement of difference between two plateaus.
Gap
A goal represents a high-level statement of intent, direction, or desired end state for an organization and its stakeholders.
Goal
Goals are generally expressed using qualitative words; e.g., "increase", "improve", or "easier". Goals can also be decomposed. Goals are typically used to measure success of an organization.
The grouping element aggregates or composes concepts that belong together based on some common characteristic.
Grouping
ImplementationAndMigrationLayerElement
Layer marker for implementation and migration planning elements — work packages, deliverables, events, plateaus, and gaps.
An implementation event is a behavior element that denotes a state change related to implementation or migration.
Implementation Event
An influence relationship indicates that an element affects the implementation or achievement of some motivation element. The influenceStrength property specifies the degree.
Influence
A unit of collective behavior performed by two or more active structure elements.
Interaction
Interactions are assigned to collaborations. They represent behavior that requires multiple participants and cannot be attributed to a single actor or component.
An internal active structure element represents an entity capable of performing behavior.
InternalActiveStructureElement
The performers — actors, roles, collaborations, components, nodes, devices, system software. Connected to behavior via assignment. Can be composed of or aggregated with other internal active structure elements.
An internal behavior element represents a unit of activity.
InternalBehaviorElement
Internal behavior is what active structure elements actually do — processes, functions, and interactions. Assigned to internal active structure via assignment relationships. Realizes external behavior (services).
An and junction is used to connect relationships of the same type where all must be satisfied.
And Junction
An or junction is used to connect relationships of the same type where one or more must be satisfied.
Or Junction
3.0: Moved from Business Layer to generic metamodel.
A location is a place or position where structure elements can be located or behavior can be performed.
Location
3.0: Introduced as part of the new Physical layer. 3.2: Realization from Material to Equipment added.
Material represents tangible physical matter or physical elements.
Material
3.0: Moved from Business Layer to Motivation elements. 3.2: Icon notation changed.
Meaning represents the knowledge or expertise present in, or the interpretation given to, a core element in a particular context.
Meaning
A motivation element represents the context of or reason behind the architecture.
MotivationElement
The 'why' behind the architecture: stakeholders, drivers, assessments, goals, outcomes, principles, requirements, constraints, meanings, and values. Connected to other elements via influence relationships.
Compute Node
Host
Server
A node represents a computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources.
Node
3.0: Introduced.
An outcome represents an end result that has been achieved.
Outcome
Outcomes are high-level, business-oriented results produced by capabilities of an organization. Outcomes are tangible, possibly quantitative, and time-related, and can be associated with assessments.
Passive structure elements can be accessed by behavior elements.
PassiveStructureElement
Objects acted upon by behavior — business objects, data objects, artifacts, materials, contracts, representations. Connected to behavior via access relationships (read, write, read-write).
Connection
Link
3.0: Renamed from CommunicationPath; meaning extended to integrate with physical elements.
A path represents a link between two or more nodes, through which these nodes can exchange data or material.
Path
PhysicalLayerElement
Layer marker for physical assets — equipment, facilities, distribution networks, and materials.
Architecture State
Baseline
Target State
A plateau represents a relatively stable state of the architecture that exists during a limited period of time.
Plateau
A principle represents a qualitative statement of intent that should be met by the architecture.
Principle
Principles are strongly related to goals and requirements. A principle defines a general property that applies to any system in a certain context. Principles are intended to be more stable than requirements.
A product represents a coherent collection of services and/or passive structure elements, accompanied by a contract/set of agreements, which is offered as a whole to customers.
Product
A realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity.
Realization
A representation represents a perceptible form of the information carried by a business object.
Representation
A requirement represents a statement of need that must be met by the architecture.
Requirement
Requirements model the properties of elements that are needed to achieve the "ends" modeled by goals. Requirements represent the "means" to realize goals.
A resource represents an asset owned or controlled by an individual or organization.
Resource
Resources are a central concept in strategic management. They are often considered, together with capabilities, to be sources of competitive advantage. Resources can be classified into tangible assets, intangible assets, and human assets.
3.0: Renamed from 'Used By'. Cross-layer relationship constraints relaxed.
A serving relationship indicates that an element provides its functionality to another element.
Serving
A specialization relationship indicates that an element is a particular kind of another element.
Specialization
A stakeholder is the role of an individual, team, or organization (or classes thereof) that represents their interests in the outcome of the architecture.
Stakeholder
This definition is based on the definition in the TOGAF framework. A stakeholder has one or more interests in, or concerns about, the organization and its Enterprise Architecture. In order to direct efforts to these interests and concerns, stakeholders change, set, and emphasize goals. Stakeholders may also influence each other. Examples of stakeholders are the CEO, the board of directors, shareholders, customers, business and application architects, but also legislative authorities.
StrategyLayerElement
Layer marker for strategy elements. Strategy elements are realized by combinations of Business, Application, and Technology layer elements.
Abstract superclass for all structure elements.
StructureElement
Parent of both active structure (performers) and passive structure (objects acted upon). Not used directly in models.
Middleware
Operating System
Platform Software
System software represents software that provides or contributes to an environment for storing, executing, and using software or data deployed within it.
System Software
A technology collaboration represents an aggregate of two or more nodes that work together to perform collective technology behavior.
Technology Collaboration
A technology event is a technology behavior element that denotes a state change.
Technology Event
A technology function represents a collection of technology behavior that can be performed by a node.
Technology Function
A technology interaction represents a unit of collective technology behavior performed by (a collaboration of) two or more nodes.
Technology Interaction
A technology interface represents a point of access where technology services offered by a node can be accessed.
Technology Interface
TechnologyLayerElement
Layer marker for technology and infrastructure elements. Realizes Application layer elements.
A technology process represents a sequence of technology behaviors that achieves a specific outcome.
Technology Process
Infrastructure Service
A technology service represents an explicitly defined exposed technology behavior.
Technology Service
A triggering relationship indicates a temporal or causal relationship between elements.
Triggering
3.0: Moved from Business Layer to Motivation elements.
Value represents the relative worth, utility, or importance of a core element or an outcome.
Value
3.1: Introduced.
A value stream represents a sequence of activities that create an overall result for a customer, stakeholder, or end user.
Value Stream
A value stream describes how an enterprise organizes its activities to create value. Value is always defined from the perspective of the stakeholder. Value streams may be defined at different levels of the organization and can be a composition or aggregation of value-adding stages.
Initiative
Project
A work package represents a series of actions identified and designed to achieve specific results within specified time and resource constraints.
Work Package