Universal Artifacts

Abstract

In most BPM systems (a.k.a. workflow systems), the data for process execution is scattered across databases for enterprise, auxiliary local data stores within the BPM systems, and even file systems (e.g., specification of process models). The interleaving nature of data management and BP execution and the lack of a coherent conceptual data model for all data needed for execution make it hard for (1) providing Business-Process-as-a-Service (BPaaS) and (2) effective support for collaboration between business processes. The primary reason is that an enormous effort is required for maintaining both the engines and the data for the client applications. In particular, different modeling languages and different BPM systems make process interoperation one of the toughest challenges. In this article, we formulate a concept of a “universal artifact,” which extends artifact-centric models by capturing all needed data for a process instance throughout its execution. A framework called SeGA based on universal artifacts is developed to support separation of data and BP execution, a key principle for BPM systems. We demonstrate in this article that SeGA is versatile enough to fully facilitate not only executions of individual processes (to support BPaaS) but also various collaboration models. Moreover, SeGA reduces the complexity in runtime management including runtime querying, constraints enforcement, and dynamic modification upon collaboration across possibly different BPM systems.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 29 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.