Linked.Archi ArchiMate 3.2 Taxonomy
Pure SKOS taxonomy classifying ArchiMate elements by layer and by aspect, and relationship types by category. For OWL abstract classes used in SHACL constraint checking, see archimate3.2-onto.ttl.
This taxonomy and the OWL abstract classes in archimate3.2-onto.ttl serve complementary purposes and are NOT duplicates: SKOS concepts (this file) OWL classes (onto file) ───────────────────────── ────────────────────────── amtax:ActiveStructureAspect am:ActiveStructureElement amtax:BusinessLayer am:BusinessLayerElement Purpose: navigation, palette Purpose: formal semantics, generation, UI filtering, SHACL constraint checking, SKOS visualization tools SPARQL reasoning Example: a modeling tool reads Example: a SHACL shape checks skos:narrower to populate the rdf:type/rdfs:subClassOf* element palette grouped by am:BehaviorElement to enforce layer and aspect. "triggering can only connect behavior elements". The two are linked via rdfs:seeAlso on each SKOS concept pointing to its corresponding OWL class. See AM-DD-1 in doc/archimate/design-decisions.md.
Linked.Archi
ArchiMate 3.2 Concept Scheme
Classification of ArchiMate elements by layer and aspect, and relationship types by category.
ArchiMate Concept
Top-level concept encompassing all ArchiMate elements, relationships, and connectors.
ArchiMate Element
An ArchiMate element — a node in the modeling palette. Elements are the basic building blocks used to define and describe enterprise architectures.
ArchiMate Relationship
An ArchiMate relationship type — an edge in the modeling palette. Relationships connect elements to express dependencies, flows, and structural links.
ArchiMate Connector
Relationship connectors (junctions) used to combine relationships of the same type using AND or OR logic.
Element by Layer
Classification of ArchiMate elements by their architectural layer — the primary horizontal grouping in the ArchiMate framework.
Strategy Layer
Elements representing strategic concepts: resources, capabilities, value streams, and courses of action. The Strategy layer provides the bridge between business goals and the architecture that supports them.
Business Layer
Elements representing business concepts: actors, roles, processes, functions, services, objects, and products. The Business layer describes the organization's operations and how it creates value.
Application Layer
Elements representing application concepts: components, interfaces, functions, services, and data objects. The Application layer describes the software systems that support business processes.
Technology Layer
Elements representing technology concepts: nodes, devices, system software, networks, paths, and artifacts. The Technology layer describes the infrastructure that hosts and runs applications.
Physical Layer
Elements representing physical concepts: equipment, facilities, distribution networks, and materials. The Physical layer describes tangible assets and physical infrastructure.
Implementation and Migration Layer
Elements representing implementation and migration concepts: work packages, deliverables, events, plateaus, and gaps. This layer supports planning and managing architecture transitions.
Element by Aspect
Classification of ArchiMate elements by their structural aspect — the vertical dimension in the ArchiMate framework (active structure, behavior, passive structure, motivation, composite).
Active Structure
Elements that can perform behavior — the subjects of activity. Includes actors, components, nodes, and their interfaces. Active structure elements are assigned to behavior elements.
Internal Active Structure
Internal active structure elements — entities capable of performing behavior: actors, roles, collaborations, components, and nodes.
External Active Structure
External active structure elements (interfaces) — points of access where services are exposed to the environment.
Passive Structure
Elements on which behavior is performed — objects, artifacts, and materials. Passive structure elements are accessed by behavior elements.
Behavior
Elements representing dynamic behavior — processes, functions, interactions, events, and services. Behavior elements describe what active structure elements do.
Internal Behavior
Internal behavior elements — units of activity performed by active structure elements: processes, functions, and interactions.
External Behavior
External behavior elements (services) — explicitly defined exposed behavior accessible through interfaces.
Event
Event elements — instantaneous state changes that trigger or are triggered by other behavior.
Motivation
Motivation elements — the context and reasons behind the architecture: stakeholders, drivers, goals, requirements, principles, and values.
Composite
Composite elements that may combine multiple aspects or layers — products, groupings, locations, and plateaus.
Strategy
Strategy elements viewed as an aspect — resources, capabilities, value streams, and courses of action that bridge business goals to architecture.
Relationship by Category
Classification of ArchiMate relationship types by their semantic category.
Structural Relationship
Relationships modeling structural dependencies between elements: composition (part-of), aggregation (groups), assignment (performs), and realization (implements).
Dependency Relationship
Relationships modeling dependencies between elements: serving (provides functionality), access (reads/writes data), and influence (affects motivation).
Dynamic Relationship
Relationships modeling dynamic behavior between elements: triggering (temporal/causal) and flow (transfer of information, goods, or money).
Other Relationship
Other relationship types: specialization (is-a-kind-of) and association (unspecified or generic relationship).