Linked.Archi ArchiMate 4.0 Taxonomy
Pure SKOS taxonomy classifying ArchiMate 4.0 elements by domain and by aspect. ArchiMate 4.0 replaces the layer-based structure of 3.x with a domain-based organization (Common, Business, Application, Technology, Strategy, Motivation, Implementation & Migration). For OWL abstract classes used in SHACL constraint checking, see archimate4-onto.ttl.
This taxonomy and the OWL abstract classes in archimate4-onto.ttl serve complementary purposes and are NOT duplicates: SKOS concepts (this file) OWL classes (onto file) ───────────────────────── ────────────────────────── am4tax:ActiveStructureAspect am4:ActiveStructureElement am4tax:CommonDomain am4:CommonDomainElement 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 am4:BehaviorElement to enforce domain 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.
Linked.Archi
ArchiMate 4.0 Concept Scheme
Classification of ArchiMate 4.0 elements by domain and by aspect.
Element by Domain
Classification of ArchiMate 4.0 elements by their architectural domain — the primary organizational grouping in the ArchiMate 4.0 framework (replacing layers from 3.x).
Common Domain
Generic, cross-domain elements shared across Business, Application, and Technology. New in ArchiMate 4.0, the Common Domain contains behavior elements (Process, Function, Event, Service) that were previously duplicated per layer, plus generic active structure elements (Role, Collaboration, Path) and composite elements (Grouping, Location).
Business Domain
Elements specific to the business domain: actors, interfaces, objects, and products. In ArchiMate 4.0, behavior elements previously in the Business layer (BusinessProcess, BusinessFunction, etc.) have been merged into the Common Domain.
Application Domain
Elements specific to the application domain: components, interfaces, and data objects. In ArchiMate 4.0, behavior elements previously in the Application layer have been merged into the Common Domain.
Technology Domain
Elements specific to the technology and physical domain: nodes, devices, system software, networks, equipment, facilities, artifacts, and materials. In ArchiMate 4.0, the Technology and Physical layers from 3.x are merged into a single Technology Domain.
Strategy Domain
Elements representing strategic concepts: resources, capabilities, value streams, and courses of action.
Motivation Domain
Elements representing the context and reasons behind the architecture: stakeholders, drivers, goals, requirements, principles, and values.
Implementation and Migration Domain
Elements supporting planning and execution of architecture changes: work packages, deliverables, and plateaus.
Element by Aspect
Classification of ArchiMate 4.0 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, roles, collaborations, and their interfaces.
Behavior
Elements representing dynamic behavior — processes, functions, events, services, capabilities, value streams, courses of action, and work packages.
Passive Structure
Elements on which behavior is performed — objects, artifacts, materials, deliverables, and resources.
Composite
Composite elements that may combine multiple aspects or domains — products, groupings, locations, and plateaus.
Motivation
Motivation elements — the context and reasons behind the architecture: stakeholders, drivers, goals, requirements, principles, and values.