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

Access
type: Class
source: sec-Access-Relationship
subclass of: QualifiedRelationship
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
unqualified form: Accesses

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.
is abstract class: true

Aggregation
type: Class
source: sec-Aggregation-Relationship
subclass of: QualifiedRelationship
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
unqualified form: Aggregates

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

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

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

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

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

Application Interface
type: Class
source: sec-Application-Interface
subclass of: ApplicationLayerElement
subclass of: ExternalActiveStructureElement
alternative label: API
alternative label: App 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.

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

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

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

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

Assessment
type: Class
source: sec-Assessment
subclass of: MotivationElement
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.

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

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

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.
is abstract class: true

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

Business Collaboration
type: Class
source: sec-Business-Collaboration
subclass of: BusinessLayerElement
subclass of: 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 Event
type: Class
source: sec-Business-Event
subclass of: BusinessLayerElement
subclass of: Event
definition: A business event is a business behavior element that denotes an organizational state change.

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

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

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

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

Business Process
type: Class
source: sec-Business-Process
subclass of: BusinessLayerElement
subclass of: InternalBehaviorElement
alternative label: Process
alternative label: Workflow
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 Role
type: Class
source: sec-Business-Role
subclass of: BusinessLayerElement
subclass of: InternalActiveStructureElement
alternative label: 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 Service
type: Class
source: sec-Business-Service
subclass of: BusinessLayerElement
subclass of: ExternalBehaviorElement
alternative label: Service
definition: A business service represents an explicitly defined exposed business behavior.

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

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.
is abstract class: true

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

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).
is abstract class: true

Composition
type: Class
source: sec-Composition-Relationship
subclass of: QualifiedRelationship
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
unqualified form: Composed Of

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

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

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).
is abstract class: true

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

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

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

Device
type: Class
source: sec-Device
subclass of: Node
alternative label: Hardware
alternative label: Physical Server
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.
definition: A device is a physical IT resource upon which system software and artifacts may be stored or deployed for execution.

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

Driver
type: Class
source: sec-Driver
subclass of: MotivationElement
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.

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

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).
is abstract class: true

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.
is abstract class: true

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.
is abstract class: true

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

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

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

Goal
type: Class
source: sec-Goal
subclass of: MotivationElement
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.

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

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

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

Influence
type: Class
source: sec-Influence-Relationship
subclass of: QualifiedRelationship
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
unqualified form: Influences

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.
is abstract class: true

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.
is abstract class: true

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).
is abstract class: true

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

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

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

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

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

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.
is abstract class: true

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

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

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).
is abstract class: true

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

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

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

Principle
type: Class
source: sec-Principle
subclass of: MotivationElement
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.

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

Realization
type: Class
source: sec-Realization-Relationship
subclass of: QualifiedRelationship
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
unqualified form: Realizes

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

Requirement
type: Class
source: sec-Requirement
subclass of: MotivationElement
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.

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

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

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

Stakeholder
type: Class
source: sec-Stakeholder
subclass of: MotivationElement
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.

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.
is abstract class: true

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.
is abstract class: true

System Software
type: Class
source: sec-System-Software
subclass of: Node
alternative label: Middleware
alternative label: Operating System
alternative label: Platform Software
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.
definition: System software represents software that provides or contributes to an environment for storing, executing, and using software or data deployed within it.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

qualified Accesses
type: ObjectProperty
range: Access
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" .
domain includes: Element
unqualified form: Accesses

qualified Aggregates
type: ObjectProperty
range: Aggregation
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 .
domain includes: Element
unqualified form: Aggregates

qualified Assigned To
type: ObjectProperty
range: Assignment
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 .
domain includes: Element
unqualified form: Assigned To

qualified Associated With
type: ObjectProperty
range: Association
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 .
domain includes: Element
unqualified form: Associated With

qualified Composed Of
type: ObjectProperty
range: Composition
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 .
domain includes: Element
unqualified form: Composed Of

qualified Flows To
type: ObjectProperty
range: Flow
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 .
domain includes: Element
unqualified form: Flows To

qualified Influences
type: ObjectProperty
range: Influence
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 "++" .
domain includes: Element
unqualified form: Influences

qualified Realizes
type: ObjectProperty
range: Realization
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 .
domain includes: Element
unqualified form: Realizes

qualified Serves
type: ObjectProperty
range: Serving
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 .
domain includes: Element
unqualified form: Serves

qualified Specializes
type: ObjectProperty
range: Specialization
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 .
domain includes: Element
unqualified form: Specializes

qualified Triggers
type: ObjectProperty
range: Triggering
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 .
domain includes: Element
unqualified form: Triggers

Realizes
type: ObjectProperty
source: sec-Realization-Relationship
definition: 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

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

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

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