Compendium

Business-Process / Workflow / Enterprise-Architecture Modelling DSLs Family Index

12 min read

Business-Process / Workflow / Enterprise-Architecture Modelling DSLs Family Index

type: language-family-index family: process-modelling languages_catalogued: 25 tags: [language-reference, family-index, process-modelling, bpmn, dmn, cmmn, archimate, uml-xmi, sysml, kerml, workflow-json]

Business-Process / Workflow / Enterprise-Architecture Modelling — Family Index

Family overview

Business-process modelling DSLs are the textual (almost exclusively XML or JSON) serialisations of the diagrammatic languages that enterprises use to describe what work happens, in what order, by whom, and under which decision rules. The dominant stack is the OMG triad: BPMN 2.0 (Business Process Model and Notation, formal Recommendation since January 2011 with maintenance release 2.0.2 published January 2014, ISO/IEC 19510:2013) for end-to-end process flows; DMN (Decision Model and Notation, first 1.0 in September 2015) for decision tables and decision logic; and CMMN 1.1 (Case Management Model and Notation, December 2016) for the ad-hoc, knowledge-worker-driven cases that BPMN’s structured-flow assumption cannot capture. All three share the OMG meta-meta-model lineage (MOF/UML) and are interchanged via XML, with the diagram layer (BPMN-DI, DMN-DI, CMMN-DI) factored separately from the semantic model.

The UML/XMI lineage runs in parallel. UML 2.5.1 / XMI 2.5.1 (2017) remains the current OMG specification and the default interchange format for modelling tools, with OCL 2.4 (2014) as the embedded constraint DSL. In July 2025 the OMG approved final adoption of SysML v2 (published September 2025), which is a clean break from UML: it is no longer a UML profile but sits on its own foundation, KerML 1.0 (Kernel Modeling Language) — a textual-first modelling notation rather than a diagram-first one. This is the most significant 2020s shift in the OMG modelling-language family and signals that the UML-profile extension mechanism, which had carried SysML 1.x for two decades, is finally being retired.

The enterprise-architecture (EA) layer sits above all of this. ArchiMate (The Open Group) provides a strategy-application-technology three-layer modelling language; ArchiMate 3.2 (October 2022) was the long-stable refinement, and ArchiMate 4 was announced and released April 27, 2026 — a major cleanup focused on simplicity and integration with TOGAF. TOGAF itself is a framework rather than a language but defines the artifact conventions that ArchiMate models populate. EPC (Event-driven Process Chain) is the SAP/Scheer/ARIS lineage, still used in SAP-heavy organisations though largely displaced by BPMN elsewhere.

The modern wave is JSON-based low-code workflow DSLs that have effectively displaced BPMN for cloud-native and citizen-developer use cases: AWS Step Functions ASL (Amazon States Language), Microsoft Power Automate flow JSON, Azure Logic Apps workflow JSON, Argo Workflows YAML (Kubernetes-native; v4.0 GA February 2026), n8n and Zapier for low-code automation, and Temporal for code-as-workflow durable execution. These are a parallel modelling universe — most never reference BPMN at all — and they collectively now process more workflow executions per day than the entire BPMN engine ecosystem combined. Inside DMN, FEEL (Friendly Enough Expression Language) is the embedded expression DSL; OCL plays the same role for UML; VTL (Velocity) appears as a templating sub-DSL in some workflow stacks. Finally, SBVR 1.5 (December 2019) is OMG’s controlled-natural-language business-rule DSL — niche but theoretically interesting for its first-order-logic / deontic-modal-logic semantics.

In our deep library

None of these formats have standalone deep-library notes; they are catalogued only at Tier 3 because they are interchange/specification languages rather than general-purpose programming languages.

Cross-reference:

  • notation-spec — UML, Z-notation, BNF and other formal-specification languages. UML 2.5.1 / OCL / SysML v2 / KerML are dual-classified: the modelling-language-as-formal-spec aspect lives there; the XMI-as-process-modelling-interchange aspect lives here.
  • build-devops — CI/CD pipeline DSLs (GitHub Actions YAML, GitLab CI YAML, Jenkinsfile, Tekton). The boundary: build-devops is build/release pipeline; this family is business-process / decision / case modelling. Argo Workflows is borderline (Kubernetes-native and used for both CI and business workflows).
  • stream-processing — data-pipeline DSLs (Flink SQL, Beam, Kafka Streams). The boundary: stream-processing is unbounded-data flow; this family is discrete process / case / decision flow.
  • api-description — OpenAPI / AsyncAPI / GraphQL SDL. Most workflow-JSON DSLs reference HTTP APIs described by OpenAPI; the workflow itself is the orchestrator on top.
  • config-management — Argo Workflows YAML and Azure Logic Apps JSON sit on the boundary; YAML/JSON config tooling is shared.
  • visual-dataflow — Apache NiFi and other visual flow editors. Visually similar but generally targets data movement rather than business-process semantics.

Tier 3 family table — OMG core (BPMN/DMN/CMMN/UML/SysML)

FormatFirst appearedOriginTypeStatus (2026)URL
BPMN 2.0 XML2011 (formal Rec.); 2.0.2 in January 2014OMGXML serialisation of Business Process Model and Notation diagrams; ISO/IEC 19510:2013Active and dominant; 2.0.2 still current; BPMN 2.1 in development at OMGhttps://www.omg.org/spec/BPMN/
DMN 1.6 (beta)2015 (DMN 1.0); 1.6 beta 2025OMGDecision Model and Notation; XML for decision tables and decision-requirements diagrams; embeds FEELActive; 1.6 beta is current; DMN 1.5 was the last formal release; widely implemented (Camunda, Drools, Trisotech)https://www.omg.org/dmn/
FEEL (DMN expression language)2015OMG (inside DMN)Embedded functional/expression DSL inside DMN; “Friendly Enough Expression Language”Active alongside DMN; the de facto expression layer for Camunda 8 across BPMN/DMN/Formshttps://docs.camunda.io/docs/components/concepts/feel/
CMMN 1.12014 (1.0); December 2016 (1.1)OMGCase Management Model and Notation; XML for ad-hoc, knowledge-worker-driven casesStable / niche; no 1.2 in development; Camunda dropped CMMN from Camunda 8; Pega and IBM Case Manager are main commercial vendorshttps://www.omg.org/cmmn/
UML 2.5.1 / XMI 2.5.12.5.1 published December 2017OMGXML Metadata Interchange; the canonical interchange format for UML 2.5.1 modelsCurrent OMG standard; no 2.6 in development; supported by Enterprise Architect, MagicDraw, Eclipse EMF, Altova UModelhttps://www.omg.org/spec/XMI/
OCL 2.4February 2014OMGObject Constraint Language; companion textual constraint DSL for UML/MOFStable / dormant; aligned with UML 2.4.1; no major OMG update since 2014https://www.omg.org/spec/OCL/
SysML 1.61.6 published December 2019OMGUML profile for systems engineering; XMI interchangeLegacy maintenance; superseded by SysML v2; still widely deployed in defence/aerospace MBSEhttps://www.omg.org/spec/SysML/1.6/
SysML v2Final adoption July 21, 2025; published September 3, 2025OMGSystems Modeling Language v2; textual-first via KerML; clean break from UML profile mechanismActive (just released); adoption ramping; Cameo Systems Modeler 2026 and others adding supporthttps://www.omg.org/spec/SYSML/2.0/
KerML 1.0September 2025OMGKernel Modeling Language; textual-syntax foundation under SysML v2Active (just released); the base layer SysML v2 is built onhttps://www.omg.org/spec/KERML/1.0/
BPEL (WS-BPEL 2.0)April 2007OASISWeb-Services Business Process Execution Language; XML; SOAP-era service orchestrationMostly legacy; superseded by BPMN 2.0 and modern workflow engines; still found in legacy SOA estateshttps://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html
XPDL 2.2XPDL 2.2 in 2012WfMC (Workflow Management Coalition)XML Process Definition Language; pre-BPMN process interchange format; later aligned with BPMNLegacy; mostly read for migration purposeshttps://www.wfmc.org/xpdl
SBVR 1.51.0 January 2008; 1.5 December 2019OMGSemantics of Business Vocabulary and Business Rules; controlled natural language with FOL + deontic/alethic modal logic semanticsStable / niche; academically interesting; adoption is thin outside specific business-rule shopshttps://www.omg.org/spec/SBVR/

Tier 3 family table — Enterprise architecture

FormatFirst appearedOriginTypeStatus (2026)URL
ArchiMate 3.23.2 October 2022 (3.0 in 2012)The Open GroupEnterprise-architecture modelling language; XML interchange via Open Group ArchiMate Model Exchange File Format (.archimate)Stable (long-lived predecessor); superseded April 27, 2026 by ArchiMate 4 but still widely deployedhttps://pubs.opengroup.org/architecture/archimate3-doc/
ArchiMate 4April 27, 2026The Open GroupMajor release focused on simplicity, clarity, and TOGAF integrationActive (just released); tooling support landing in Archi, Visual Paradigm, Sparx EAhttps://www.opengroup.org/archimate-4-member-license
TOGAF Architecture Description (10th ed.)TOGAF 10 in April 2022The Open GroupFramework rather than a language, but defines artifact conventions ArchiMate populatesActivehttps://www.opengroup.org/togaf
EPC (Event-driven Process Chain)early 1990sAugust-Wilhelm Scheer / ARIS / SAPEvent-/function-alternating process diagram; AML XML interchange via ARISLegacy in non-SAP world; still mainstream inside SAP-centric enterpriseshttps://en.wikipedia.org/wiki/Event-driven_process_chain

Tier 3 family table — Process engines (BPMN-based)

FormatFirst appearedOriginTypeStatus (2026)URL
Camunda 8 BPMN+DMN+FEEL2013 (Camunda BPM); 2022 (Camunda 8 / Zeebe)CamundaBPMN 2.0 + DMN 1.3 + FEEL on top of the cloud-native Zeebe engine; Camunda 8 dropped CMMNVery active; the dominant open-core BPMN engine in 2026https://docs.camunda.io/
Bonita BPM model2009BonitasoftBPMN 2.0 superset with proprietary connectors and form/case extensionsActive but lower velocity than Camundahttps://documentation.bonitasoft.com/
jBPM process language2003Red Hat / JBossBPMN 2.0-based process engine; tightly coupled to Drools (DMN/rules)Active but niche outside Red Hat shopshttps://www.jbpm.org/
Activiti2010Alfresco (BPMN-fork from jBPM lineage by Tom Baeyens)BPMN 2.0 engine; Flowable was a 2016 fork that has overtaken Activiti in activityMaintenance; Flowable is the de facto continuationhttps://www.activiti.org/
Flowable2016 (fork of Activiti)FlowableBPMN 2.0 + DMN + CMMN engine; one of the few engines still implementing CMMNActive; broader OMG-triad coverage than Camunda 8https://www.flowable.com/open-source

Tier 3 family table — Modern low-code / cloud workflow

FormatFirst appearedOriginTypeStatus (2026)URL
AWS Step Functions ASL (Amazon States Language)December 2016AWSJSON-based state-machine DSL; Standard and Express workflow modes; Workflow Studio visual editor generates ASLVery active; the dominant cloud-workflow DSL in the AWS ecosystemhttps://docs.aws.amazon.com/step-functions/latest/dg/concepts-amazon-states-language.html
Azure Logic Apps workflow JSON2016Microsoft AzureJSON workflow definition language; Standard and Consumption tiersActivehttps://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-definition-language
Microsoft Power Automate flow JSON2016 (as Microsoft Flow)MicrosoftLow-code workflow JSON; tightly coupled to Microsoft 365 / Dataverse / Copilot StudioVery active; the dominant citizen-developer workflow DSL inside Microsoft estateshttps://learn.microsoft.com/en-us/power-automate/
Argo Workflows YAML2017Argo project (Intuit / CNCF)Kubernetes-native workflow CRD; DAG and step semantics; v4.0 GA February 4, 2026Very active; CNCF graduated; v4.0.5 latest stable as of April 2026https://argoproj.github.io/workflows/
Temporal workflow code2019 (Temporal Inc.; lineage from Uber Cadence 2017)Temporal Technologies”Code-as-workflow” durable execution; Workflows in Go/Java/Python/TypeScript/PHP rather than YAML/JSON DSL; configuration is the only DSL surfaceVery active; substantial 2024-2026 traction at Netflix, HashiCorp, Stripe, etc.https://docs.temporal.io/
n8n workflow JSON2019n8n.ioOpen-source low-code automation; visual editor with JSON workflow exportActive; open-source alternative to Zapier and Power Automatehttps://docs.n8n.io/
Zapier Workflow JSON2011ZapierClosed/SaaS low-code automation; JSON workflow representationActive; the original mass-market low-code workflow toolhttps://zapier.com/
CAP (Common Alerting Protocol)OASIS 1.2 in 2010OASISXML emergency-management alerting / workflow message formatStable; mandated for many public-warning systemshttps://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html

Notable threads

  • BPMN 2.0 as the surprisingly-stable standard. Formally adopted in 2011, with its only maintenance release (2.0.2) published January 2014 and ratified as ISO/IEC 19510:2013, BPMN 2.0 is still the dominant enterprise process-modelling language in 2026. The core diagram types (process, collaboration, choreography) and the XML schema have been stable for 12+ years; BPMN 2.1 is in development at OMG but not yet a formal release as of mid-2026. This longevity reflects both genuine quality and the high cost of churn — every BPMN 2.0 model in deployment, every engine implementation, every certification is anchored to 2.0.2.

  • DMN as the decision-table breakthrough. DMN (first 1.0 in September 2015) cracked open decision modelling for business analysts by separating decision requirements (DRD diagrams) from decision logic (decision tables) from decision expressions (FEEL). The genius is that decision tables are something domain experts can read directly, while FEEL underneath gives the engine a precise functional semantics. DMN 1.6 beta is current; DMN 1.5 was the last formal release. Camunda, Drools, Trisotech, and Red Hat KIE all implement substantial subsets, and DMN has displaced ad-hoc business-rules engines in many organisations.

  • SysML 2.0 / KerML’s clean break from UML. Approved for final adoption July 21, 2025 and published September 3, 2025, SysML v2 is the largest OMG modelling-language event of the 2020s. Key shift: SysML 1.x was a UML profile (extension via stereotypes), which constrained semantics to whatever UML’s metamodel allowed; SysML v2 is built on its own foundation, KerML 1.0, with a textual-first concrete syntax that compiles to / from diagrams rather than the other way around. Adoption will be slow — defence and aerospace MBSE estates have a decade of SysML 1.x investment — but the direction of travel is set.

  • ArchiMate 4 just landed. The Open Group announced ArchiMate 4 on April 27, 2026, the first major release since ArchiMate 3.0 (2012) and ArchiMate 3.2 (October 2022). Headline goals: simplicity, clarity, and tighter TOGAF integration. ArchiMate 3.2 will remain in production for years given the deployed base, but new EA programmes started in 2026+ should evaluate ArchiMate 4 directly. Tooling support is landing in Archi (open source), Visual Paradigm, and Sparx Enterprise Architect.

  • The low-code displacement of BPMN. AWS Step Functions ASL, Azure Logic Apps JSON, Power Automate flow JSON, n8n, and Zapier collectively process billions of workflow executions per day in 2026 — most without ever referencing BPMN. The cultural break is significant: BPMN assumed “business analyst draws diagram in modeller, hands XML to engine”; ASL/Power Automate assume “developer or citizen-developer composes JSON in cloud console, runs in cloud immediately.” These are effectively a parallel modelling universe with different vocabularies (states, transitions, triggers, connectors) and almost no interchange between them and the OMG triad.

  • BPEL’s slow death. WS-BPEL 2.0 (OASIS, April 2007) was the standard for SOA-era service orchestration: XML, SOAP-flavoured, with deep WSDL coupling. As REST/JSON displaced SOAP and as BPMN 2.0 grew executable extensions, BPEL evaporated from new builds. Modern equivalents — Camunda 8, Flowable, AWS Step Functions, Temporal — are all either BPMN-based or code-based. BPEL is now read only when migrating legacy estates.

  • Temporal as the “code is the workflow” rejection. Temporal (2019, lineage from Uber Cadence 2017) explicitly rejects declarative workflow DSLs. Workflows are written in Go / Java / Python / TypeScript / PHP as ordinary functions; the runtime guarantees deterministic replay and durable execution across crashes. The substantial 2024-2026 traction (Netflix, HashiCorp, Stripe, Coinbase, DoorDash) is a cultural signal that the developer-experience cost of YAML/JSON workflow DSLs is real. The trade-off: code-as-workflow loses the business-analyst-readable diagram and requires the workflow author to be a programmer.

  • The CMMN niche. Case Management Model and Notation 1.1 (December 2016) is the OMG triad’s least-adopted member. The premise — adaptive, knowledge-worker-driven cases — is real (insurance claims, legal matters, healthcare patient journeys), but most teams either fall back to BPMN with ad-hoc extensions or to vendor-specific case managers (Pega, IBM Case Manager, Appian). Camunda dropped CMMN entirely in Camunda 8; Flowable is one of the few open-source engines still implementing it. No CMMN 1.2 is in development.

Citations

Graph View