Linked.Archi ArchiMate 3.2 Ontology
type: Ontology
imports: core#
license: http://creativecommons.org/licenses/by/4.0/
preferred namespace prefix: am
creator: Kalin Maldzhanski
description: 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.
abstract: 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.
created: 2019-03-17
issued: 2019-03-17
modified: 2025-12-01
publisher: Linked.Archi
publisher: linked.archi
status: draft
source: archimate3-doc
source: archimate3 Model.xsd
version IRI: 3.2#
version info: 3.2
prior version: 3.1#
citation: Linked.Archi ArchiMate Ontology
history note: 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 dc: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 (:).
scope note: 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.

BehaviorElement
type: Class
subclass of: Element
definition: Behavior elements represent the dynamic aspects of the enterprise.
scope note: 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.

InternalBehaviorElement
type: Class
subclass of: BehaviorElement
definition: An internal behavior element represents a unit of activity.
scope note: 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).

ExternalBehaviorElement
type: Class
subclass of: BehaviorElement
definition: An external behavior element (service) represents explicitly defined exposed behavior.
scope note: Services are the externally visible behavior offered to consumers. Realized by internal behavior and exposed through interfaces. Connected to consumers via serving relationships.

Event
type: Class
subclass of: BehaviorElement
definition: An event represents a state change.
scope note: 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).

Interaction
type: Class
subclass of: InternalBehaviorElement
definition: A unit of collective behavior performed by two or more active structure elements.
scope note: Interactions are assigned to collaborations. They represent behavior that requires multiple participants and cannot be attributed to a single actor or component.

StructureElement
type: Class
subclass of: Element
definition: Abstract superclass for all structure elements.
scope note: Parent of both active structure (performers) and passive structure (objects acted upon). Not used directly in models.

ActiveStructureElement
type: Class
subclass of: StructureElement
definition: Active structure elements are the subjects that can perform behavior.
scope note: 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.

InternalActiveStructureElement
type: Class
subclass of: ActiveStructureElement
definition: An internal active structure element represents an entity capable of performing behavior.
scope note: 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.

ExternalActiveStructureElement
type: Class
subclass of: ActiveStructureElement
definition: An external active structure element (interface) represents a point of access.
scope note: 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.

Collaboration
type: Class
subclass of: InternalActiveStructureElement
definition: An aggregate of two or more internal active structure elements working together.
scope note: Collaborations aggregate roles or actors that perform collective behavior (interactions). They are temporary or permanent groupings aimed at specific interactions.

PassiveStructureElement
type: Class
subclass of: StructureElement
definition: Passive structure elements can be accessed by behavior elements.
scope note: Objects acted upon by behavior — business objects, data objects, artifacts, materials, contracts, representations. Connected to behavior via access relationships (read, write, read-write).

MotivationElement
type: Class
subclass of: Element
definition: A motivation element represents the context of or reason behind the architecture.
scope note: The 'why' behind the architecture: stakeholders, drivers, assessments, goals, outcomes, principles, requirements, constraints, meanings, and values. Connected to other elements via influence relationships.

CompositeElement
type: Class
subclass of: Element
definition: Composite elements consist of other concepts, possibly from multiple aspects or layers.
scope note: Elements that cross aspect boundaries: products (bundle services and objects), groupings (generic containers), locations (physical or logical places), and plateaus (stable architecture states).

CoreLayerElement
type: Class
subclass of: Element
definition: Core layers are Business, Application, and Technology (including Physical).
scope note: 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).

BusinessLayerElement
type: Class
subclass of: CoreLayerElement
scope note: Layer marker for business domain elements. Served by Application layer elements.

ApplicationLayerElement
type: Class
subclass of: CoreLayerElement
scope note: Layer marker for application domain elements. Serves Business layer, realized by Technology layer.

TechnologyLayerElement
type: Class
subclass of: CoreLayerElement
scope note: Layer marker for technology and infrastructure elements. Realizes Application layer elements.

PhysicalLayerElement
type: Class
subclass of: CoreLayerElement
scope note: Layer marker for physical assets — equipment, facilities, distribution networks, and materials.

StrategyLayerElement
type: Class
subclass of: Element
scope note: Layer marker for strategy elements. Strategy elements are realized by combinations of Business, Application, and Technology layer elements.

ImplementationAndMigrationLayerElement
type: Class
subclass of: Element
scope note: Layer marker for implementation and migration planning elements — work packages, deliverables, events, plateaus, and gaps.

Stakeholder
type: Class
subclass of: MotivationElement
source: sec-Stakeholder
definition: A stakeholder is the role of an individual, team, or organization (or classes thereof) that represents their interests in the outcome of the architecture.
scope note: 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.

Driver
type: Class
subclass of: MotivationElement
source: sec-Driver
definition: A driver represents an external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them.
scope note: 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.

Assessment
type: Class
subclass of: MotivationElement
source: sec-Assessment
definition: An assessment represents the result of an analysis of the state of affairs of the enterprise with respect to some driver.
scope note: 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.

Goal
type: Class
subclass of: MotivationElement
source: sec-Goal
definition: A goal represents a high-level statement of intent, direction, or desired end state for an organization and its stakeholders.
scope note: 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.

Outcome
type: Class
subclass of: MotivationElement
source: sec-Outcome
definition: An outcome represents an end result that has been achieved.
change note: 3.0: Introduced.
scope note: 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.

Principle
type: Class
subclass of: MotivationElement
source: sec-Principle
definition: A principle represents a qualitative statement of intent that should be met by the architecture.
scope note: 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.

Requirement
type: Class
subclass of: MotivationElement
source: sec-Requirement
definition: A requirement represents a statement of need that must be met by the architecture.
scope note: Requirements model the properties of elements that are needed to achieve the "ends" modeled by goals. Requirements represent the "means" to realize goals.

Constraint
type: Class
subclass of: Requirement
source: sec-Constraint
definition: A constraint represents a factor that prevents or obstructs the realization of goals.
change note: 3.2: Definition improved.
scope note: A constraint does not prescribe intended functionality but imposes a restriction on the way the system operates or may be realized.

Meaning
type: Class
subclass of: MotivationElement
source: sec-Meaning
definition: Meaning represents the knowledge or expertise present in, or the interpretation given to, a core element in a particular context.
change note: 3.0: Moved from Business Layer to Motivation elements. 3.2: Icon notation changed.

Value
type: Class
subclass of: MotivationElement
source: sec-Value
definition: Value represents the relative worth, utility, or importance of a core element or an outcome.
change note: 3.0: Moved from Business Layer to Motivation elements.

Resource
type: Class
subclass of: StructureElement
subclass of: StrategyLayerElement
source: sec-Resource
definition: A resource represents an asset owned or controlled by an individual or organization.
change note: 3.0: Introduced as part of the new Strategy layer.
scope note: 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.

Capability
type: Class
subclass of: BehaviorElement
subclass of: StrategyLayerElement
alternative label: Business Capability
source: sec-Capability
definition: A capability represents an ability that an active structure element, such as an organization, person, or system, possesses.
change note: 3.0: Introduced as part of the new Strategy layer.
scope note: 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.

Value Stream
type: Class
subclass of: BehaviorElement
subclass of: StrategyLayerElement
source: sec-Value-Stream
definition: A value stream represents a sequence of activities that create an overall result for a customer, stakeholder, or end user.
change note: 3.1: Introduced.
scope note: 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.

Course of Action
type: Class
subclass of: BehaviorElement
subclass of: StrategyLayerElement
source: sec-Course-of-Action
definition: A course of action is an approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal.
change note: 3.0: Introduced as part of the new Strategy layer.
scope note: 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.

Business Actor
type: Class
subclass of: InternalActiveStructureElement
subclass of: BusinessLayerElement
alternative label: Organization
alternative label: Department
alternative label: Person
source: sec-Business-Actor
definition: A business actor is a business entity that is capable of performing behavior.

Business Role
type: Class
subclass of: InternalActiveStructureElement
subclass of: BusinessLayerElement
alternative label: Role
source: sec-Business-Role
definition: 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 Collaboration
type: Class
subclass of: Collaboration
subclass of: BusinessLayerElement
source: sec-Business-Collaboration
definition: A business collaboration is an aggregate of two or more business internal active structure elements that work together to perform collective behavior.

Business Interface
type: Class
subclass of: ExternalActiveStructureElement
subclass of: BusinessLayerElement
source: sec-Business-Interface
definition: A business interface is a point of access where a business service is made available to the environment.

Business Process
type: Class
subclass of: InternalBehaviorElement
subclass of: BusinessLayerElement
alternative label: Process
alternative label: Workflow
source: sec-Business-Process
definition: 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 Function
type: Class
subclass of: InternalBehaviorElement
subclass of: BusinessLayerElement
alternative label: Function
source: sec-Business-Function
definition: 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 Interaction
type: Class
subclass of: Interaction
subclass of: BusinessLayerElement
source: sec-Business-Interaction
definition: A business interaction is a unit of collective business behavior performed by (a collaboration of) two or more business roles.

Business Event
type: Class
subclass of: Event
subclass of: BusinessLayerElement
source: sec-Business-Event
definition: A business event is a business behavior element that denotes an organizational state change.

Business Service
type: Class
subclass of: ExternalBehaviorElement
subclass of: BusinessLayerElement
alternative label: Service
source: sec-Business-Service
definition: A business service represents an explicitly defined exposed business behavior.

Business Object
type: Class
subclass of: PassiveStructureElement
subclass of: BusinessLayerElement
alternative label: Information Object
source: sec-Business-Object
definition: A business object represents a concept used within a particular business domain.

Contract
type: Class
subclass of: Business Object
source: sec-Contract
definition: 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.

Representation
type: Class
subclass of: PassiveStructureElement
subclass of: BusinessLayerElement
source: sec-Representation
definition: A representation represents a perceptible form of the information carried by a business object.

Product
type: Class
subclass of: CompositeElement
subclass of: BusinessLayerElement
source: sec-Product
definition: 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.

Application Component
type: Class
subclass of: InternalActiveStructureElement
subclass of: ApplicationLayerElement
alternative label: Software Component
alternative label: Application
source: sec-Application-Component
definition: An application component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.

Application Collaboration
type: Class
subclass of: Collaboration
subclass of: ApplicationLayerElement
source: sec-Application-Collaboration
definition: An application collaboration represents an aggregate of two or more application components that work together to perform collective application behavior.

Application Interface
type: Class
subclass of: ExternalActiveStructureElement
subclass of: ApplicationLayerElement
alternative label: API
alternative label: App Interface
source: sec-Application-Interface
definition: An application interface represents a point of access where application services are made available to a user, another application component, or a node.

Application Function
type: Class
subclass of: InternalBehaviorElement
subclass of: ApplicationLayerElement
alternative label: App Function
source: sec-Application-Function
definition: An application function represents automated behavior that can be performed by an application component.

Application Interaction
type: Class
subclass of: Interaction
subclass of: ApplicationLayerElement
source: sec-Application-Interaction
definition: An application interaction represents a unit of collective application behavior performed by (a collaboration of) two or more application components.

Application Process
type: Class
subclass of: InternalBehaviorElement
subclass of: ApplicationLayerElement
alternative label: App Process
source: sec-Application-Process
definition: An application process represents a sequence of application behaviors that achieves a specific outcome.
change note: 3.0: Introduced to increase regularity across layers.

Application Event
type: Class
subclass of: Event
subclass of: ApplicationLayerElement
source: sec-Application-Event
definition: An application event is an application behavior element that denotes a state change.

Application Service
type: Class
subclass of: ExternalBehaviorElement
subclass of: ApplicationLayerElement
alternative label: Software Service
source: sec-Application-Service
definition: An application service represents an explicitly defined exposed application behavior.

Data Object
type: Class
subclass of: PassiveStructureElement
subclass of: ApplicationLayerElement
alternative label: Data Entity
alternative label: Data Asset
source: sec-Data-Object
definition: A data object represents data structured for automated processing.

Node
type: Class
subclass of: InternalActiveStructureElement
subclass of: TechnologyLayerElement
alternative label: Server
alternative label: Host
alternative label: Compute Node
source: sec-Node
definition: A node represents a computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources.

Device
type: Class
subclass of: Node
alternative label: Hardware
alternative label: Physical Server
source: sec-Device
definition: A device is a physical IT resource upon which system software and artifacts may be stored or deployed for execution.
change note: 3.2: No longer a subtype of Node; now a subtype of technology internal active structure element, with composition and aggregation relationships to Node.

System Software
type: Class
subclass of: Node
alternative label: Platform Software
alternative label: Middleware
alternative label: Operating System
source: sec-System-Software
definition: System software represents software that provides or contributes to an environment for storing, executing, and using software or data deployed within it.
change note: 3.2: No longer a subtype of Node; now a subtype of technology internal active structure element, with composition and aggregation relationships to Node.

Technology Collaboration
type: Class
subclass of: Collaboration
subclass of: TechnologyLayerElement
source: sec-Technology-Collaboration
definition: A technology collaboration represents an aggregate of two or more nodes that work together to perform collective technology behavior.
change note: 3.0: Introduced to increase regularity across layers.

Technology Interface
type: Class
subclass of: ExternalActiveStructureElement
subclass of: TechnologyLayerElement
source: sec-Technology-Interface
definition: A technology interface represents a point of access where technology services offered by a node can be accessed.

Path
type: Class
subclass of: ActiveStructureElement
subclass of: TechnologyLayerElement
alternative label: Link
alternative label: Connection
source: sec-Path
definition: A path represents a link between two or more nodes, through which these nodes can exchange data or material.
change note: 3.0: Renamed from CommunicationPath; meaning extended to integrate with physical elements.

Communication Network
type: Class
subclass of: ActiveStructureElement
subclass of: TechnologyLayerElement
alternative label: Network
alternative label: LAN
alternative label: WAN
source: sec-Communication-Network
definition: A communication network represents a set of structures that connects computer systems or other electronic devices for transmission, routing, and reception of data.
change note: 3.2: Icon notation changed.

Technology Function
type: Class
subclass of: InternalBehaviorElement
subclass of: TechnologyLayerElement
source: sec-Technology-Function
definition: A technology function represents a collection of technology behavior that can be performed by a node.

Technology Process
type: Class
subclass of: InternalBehaviorElement
subclass of: TechnologyLayerElement
source: sec-Technology-Process
definition: A technology process represents a sequence of technology behaviors that achieves a specific outcome.
change note: 3.0: Introduced to increase regularity across layers.

Technology Interaction
type: Class
subclass of: Interaction
subclass of: TechnologyLayerElement
source: sec-Technology-Interaction
definition: A technology interaction represents a unit of collective technology behavior performed by (a collaboration of) two or more nodes.
change note: 3.0: Introduced to increase regularity across layers.

Technology Event
type: Class
subclass of: Event
subclass of: TechnologyLayerElement
source: sec-Technology-Event
definition: A technology event is a technology behavior element that denotes a state change.

Technology Service
type: Class
subclass of: ExternalBehaviorElement
subclass of: TechnologyLayerElement
alternative label: Infrastructure Service
source: sec-Technology-Service
definition: A technology service represents an explicitly defined exposed technology behavior.

Artifact
type: Class
subclass of: PassiveStructureElement
subclass of: TechnologyLayerElement
alternative label: Deployment Unit
alternative label: Binary
alternative label: Package
source: sec-Artifact
definition: 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.

Equipment
type: Class
subclass of: Node
subclass of: PhysicalLayerElement
alternative label: Machine
alternative label: Physical Device
source: sec-Equipment
definition: Equipment represents one or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.
change note: 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.

Facility
type: Class
subclass of: Node
subclass of: PhysicalLayerElement
alternative label: Building
alternative label: Data Center
alternative label: Site
source: sec-Facility
definition: A facility represents a physical structure or environment.
change note: 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.

Distribution Network
type: Class
subclass of: ActiveStructureElement
subclass of: PhysicalLayerElement
source: sec-Distribution-Network
definition: A distribution network represents a physical network used to transport materials or energy.
change note: 3.0: Introduced as part of the new Physical layer.

Material
type: Class
subclass of: PassiveStructureElement
subclass of: PhysicalLayerElement
source: sec-Material
definition: Material represents tangible physical matter or physical elements.
change note: 3.0: Introduced as part of the new Physical layer. 3.2: Realization from Material to Equipment added.

Work Package
type: Class
subclass of: InternalBehaviorElement
subclass of: ImplementationAndMigrationLayerElement
alternative label: Project
alternative label: Initiative
source: sec-Work-Package
definition: A work package represents a series of actions identified and designed to achieve specific results within specified time and resource constraints.

Deliverable
type: Class
subclass of: PassiveStructureElement
subclass of: ImplementationAndMigrationLayerElement
source: sec-Deliverable
definition: A deliverable represents a precisely-defined outcome of a work package.

Implementation Event
type: Class
subclass of: Event
subclass of: ImplementationAndMigrationLayerElement
source: sec-Implementation-Event
definition: An implementation event is a behavior element that denotes a state change related to implementation or migration.

Plateau
type: Class
subclass of: CompositeElement
subclass of: ImplementationAndMigrationLayerElement
alternative label: Architecture State
alternative label: Baseline
alternative label: Target State
source: sec-Plateau
definition: A plateau represents a relatively stable state of the architecture that exists during a limited period of time.

Gap
type: Class
subclass of: PassiveStructureElement
subclass of: ImplementationAndMigrationLayerElement
source: sec-Gap
definition: A gap represents a statement of difference between two plateaus.

Grouping
type: Class
subclass of: CompositeElement
source: sec-Grouping
definition: The grouping element aggregates or composes concepts that belong together based on some common characteristic.

Location
type: Class
subclass of: CompositeElement
source: sec-Location
definition: A location is a place or position where structure elements can be located or behavior can be performed.
change note: 3.0: Moved from Business Layer to generic metamodel.

And Junction
type: Class
subclass of: Element
source: sec-Junction
definition: An and junction is used to connect relationships of the same type where all must be satisfied.

Or Junction
type: Class
subclass of: Element
source: sec-Junction
definition: An or junction is used to connect relationships of the same type where one or more must be satisfied.

Composed Of
type: ObjectProperty
definition: Indicates that an element consists of one or more other elements.
source: sec-Composition-Relationship
domain includes: Element
range includes: Element

Composition
type: Class
subclass of: QualifiedRelationship
unqualified form: Composed Of
source: sec-Composition-Relationship
definition: 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.
domain includes: Element
range includes: Element

qualified Composed Of
type: ObjectProperty
range: Composition
unqualified form: Composed Of
domain includes: Element
definition: 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.
example: ex:System1 am:qualifiedComposedOf ex:qr-001 . ex:qr-001 a am:Composition ; arch:source ex:System1 ; arch:target ex:Module1 .

Aggregates
type: ObjectProperty
definition: Indicates that an element combines one or more other elements.
source: sec-Aggregation-Relationship
domain includes: Element
range includes: Element

Aggregation
type: Class
subclass of: QualifiedRelationship
unqualified form: Aggregates
source: sec-Aggregation-Relationship
definition: An aggregation relationship indicates that an element combines one or more other elements. Unlike composition, the aggregated element can exist independently.
domain includes: Element
range includes: Element

qualified Aggregates
type: ObjectProperty
range: Aggregation
unqualified form: Aggregates
domain includes: Element
definition: Navigates from a source element to an Aggregation qualified relationship resource.
example: ex:Department1 am:qualifiedAggregates ex:qr-002 . ex:qr-002 a am:Aggregation ; arch:source ex:Department1 ; arch:target ex:Team1 .

Assigned To
type: ObjectProperty
definition: Indicates the allocation of responsibility, performance of behavior, storage, or execution.
change note: 3.0: Directional notation introduced (arrow replaces black circle at 'to' end).
source: sec-Assignment-Relationship
domain includes: Element
range includes: Element

Assignment
type: Class
subclass of: QualifiedRelationship
unqualified form: Assigned To
source: sec-Assignment-Relationship
definition: An assignment relationship indicates the allocation of responsibility, performance of behavior, storage, or execution.
domain includes: Element
range includes: Element

qualified Assigned To
type: ObjectProperty
range: Assignment
unqualified form: Assigned To
domain includes: Element
definition: 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.
example: ex:DevTeam am:qualifiedAssignedTo ex:qr-003 . ex:qr-003 a am:Assignment ; arch:source ex:DevTeam ; arch:target ex:DeploymentProcess .

Realizes
type: ObjectProperty
definition: Indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity.
source: sec-Realization-Relationship
domain includes: Element
range includes: Element

Realization
type: Class
subclass of: QualifiedRelationship
unqualified form: Realizes
source: sec-Realization-Relationship
definition: A realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity.
domain includes: Element
range includes: Element

qualified Realizes
type: ObjectProperty
range: Realization
unqualified form: Realizes
domain includes: Element
definition: Navigates from a source element to a Realization qualified relationship resource. Realization links a concrete element with a more abstract element it realizes.
example: ex:PaymentSvc am:qualifiedRealizes ex:qr-004 . ex:qr-004 a am:Realization ; arch:source ex:PaymentSvc ; arch:target ex:PaymentCapability .

Serves
type: ObjectProperty
definition: Indicates that an element provides its functionality to another element.
change note: 3.0: Renamed from 'Used By' to 'Serves', in line with the other active names of relationships.
source: sec-Serving-Relationship
domain includes: Element
range includes: Element

Serving
type: Class
subclass of: QualifiedRelationship
unqualified form: Serves
source: sec-Serving-Relationship
definition: A serving relationship indicates that an element provides its functionality to another element.
change note: 3.0: Renamed from 'Used By'. Cross-layer relationship constraints relaxed.
domain includes: Element
range includes: Element

qualified Serves
type: ObjectProperty
range: Serving
unqualified form: Serves
domain includes: Element
definition: Navigates from a source element to a Serving qualified relationship resource. Serving indicates that an element provides its functionality to another.
example: 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 .

Accesses
type: ObjectProperty
definition: Indicates that a behavior element may access a business or data object.
source: sec-Access-Relationship
domain includes: Element
range includes: Element

Access
type: Class
subclass of: QualifiedRelationship
unqualified form: Accesses
source: sec-Access-Relationship
definition: 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.
domain includes: Element
range includes: Element

qualified Accesses
type: ObjectProperty
range: Access
unqualified form: Accesses
domain includes: Element
definition: Navigates from a source element to an Access qualified relationship resource. The Access resource carries the accessType (Read, Write, ReadWrite).
example: ex:OrderProcess am:qualifiedAccesses ex:qr-006 . ex:qr-006 a am:Access ; arch:source ex:OrderProcess ; arch:target ex:CustomerData ; am:accessType "ReadWrite" .

Influences
type: ObjectProperty
definition: Indicates that an element affects the implementation or achievement of some motivation element.
change note: 3.0: Notation changed for consistency with other dependency relationships (access and serving).
source: sec-Influence-Relationship
domain includes: Element
range includes: Element

Influence
type: Class
subclass of: QualifiedRelationship
unqualified form: Influences
source: sec-Influence-Relationship
definition: An influence relationship indicates that an element affects the implementation or achievement of some motivation element. The influenceStrength property specifies the degree.
domain includes: Element
range includes: Element

qualified Influences
type: ObjectProperty
range: Influence
unqualified form: Influences
domain includes: Element
definition: Navigates from a source element to an Influence qualified relationship resource. The Influence resource carries the influenceStrength (+, ++, -, --).
example: ex:CostReduction am:qualifiedInfluences ex:qr-007 . ex:qr-007 a am:Influence ; arch:source ex:CostReduction ; arch:target ex:Profitability ; am:influenceStrength "++" .

Triggers
type: ObjectProperty
definition: Indicates a temporal or causal relationship between elements.
source: sec-Triggering-Relationship
domain includes: Element
range includes: Element

Triggering
type: Class
subclass of: QualifiedRelationship
unqualified form: Triggers
source: sec-Triggering-Relationship
definition: A triggering relationship indicates a temporal or causal relationship between elements.
domain includes: Element
range includes: Element

qualified Triggers
type: ObjectProperty
range: Triggering
unqualified form: Triggers
domain includes: Element
definition: Navigates from a source element to a Triggering qualified relationship resource. Triggering indicates a temporal or causal dependency.
example: ex:OrderReceived am:qualifiedTriggers ex:qr-008 . ex:qr-008 a am:Triggering ; arch:source ex:OrderReceived ; arch:target ex:FulfillmentProcess .

Flows To
type: ObjectProperty
definition: Indicates transfer from one element to another.
source: sec-Flow-Relationship
domain includes: Element
range includes: Element

Flow
type: Class
subclass of: QualifiedRelationship
unqualified form: Flows To
source: sec-Flow-Relationship
definition: A flow relationship indicates transfer from one element to another.
domain includes: Element
range includes: Element

qualified Flows To
type: ObjectProperty
range: Flow
unqualified form: Flows To
domain includes: Element
definition: Navigates from a source element to a Flow qualified relationship resource. Flow indicates transfer of information, goods, or money.
example: 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 .

Specializes
type: ObjectProperty
definition: Indicates that an element is a particular kind of another element.
source: sec-Specialization-Relationship
domain includes: Element
range includes: Element

Specialization
type: Class
subclass of: QualifiedRelationship
unqualified form: Specializes
source: sec-Specialization-Relationship
definition: A specialization relationship indicates that an element is a particular kind of another element.
domain includes: Element
range includes: Element

qualified Specializes
type: ObjectProperty
range: Specialization
unqualified form: Specializes
domain includes: Element
definition: Navigates from a source element to a Specialization qualified relationship resource. Specialization indicates that an element is a particular kind of another.
example: ex:OnlineBanking am:qualifiedSpecializes ex:qr-010 . ex:qr-010 a am:Specialization ; arch:source ex:OnlineBanking ; arch:target ex:BankingService .

Associated With
type: ObjectProperty
definition: Indicates an unspecified relationship, or one that is not represented by another ArchiMate relationship.
source: sec-Association-Relationship
domain includes: Element
range includes: Element

Association
type: Class
subclass of: QualifiedRelationship
unqualified form: Associated With
source: sec-Association-Relationship
definition: An association relationship indicates an unspecified relationship, or one that is not represented by another ArchiMate relationship.
domain includes: Element
range includes: Element

qualified Associated With
type: ObjectProperty
range: Association
unqualified form: Associated With
domain includes: Element
definition: Navigates from a source element to an Association qualified relationship resource. Association is the most generic relationship — used when no more specific type applies.
example: ex:Stakeholder1 am:qualifiedAssociatedWith ex:qr-011 . ex:qr-011 a am:Association ; arch:source ex:Stakeholder1 ; arch:target ex:Driver1 .

Access Type
type: DatatypeProperty
definition: Specifies the type of access: read, write, read-write, or unspecified.
domain: Access
range: string

Influence Strength
type: DatatypeProperty
definition: Specifies the strength or sign of an influence (e.g., +, ++, -, --).
domain: Influence
range: string