Verification of relational data-centric dynamic systems with external services

Abstract

Data-centric dynamic systems are systems where both the process controlling the dynamics and the manipulation of data are equally central. We study verification of (first-order) µ-calculus variants over relational data-centric dynamic systems, where data are maintained in a relational database, and the process is described in terms of atomic actions that evolve the database. Action execution may involve calls to external services, thus inserting fresh data into the system. As a result such systems are infinite-state. We show that verification is undecidable in general, and we isolate notable cases where decidability is achieved. Specifically we start by considering service calls that return values deterministically (depending only on passed parameters). We show that in a µ-calculus variant that preserves knowledge of objects appeared along a run we get decidability under the assumption that the fresh data introduced along a run are bounded, though they might not be bounded in the overall system. In fact we tie such a result to a notion related to weak acyclicity studied in data exchange. Then, we move to nondeterministic services and we investigate decidability under the assumption that knowledge of objects is preserved only if they are continuously present. We show that if infinitely many values occur in a run but do not accumulate in the same state, then we get again decidability. We give syntactic conditions to avoid this accumulation through the novel notion of "generate-recall acyclicity", which ensures that every service call activation generates new values that cannot be accumulated indefinitely.

Specifying Artifact-Centric Business Process Models in UML

“…Many authors opt for a database schema [26,11,27,28,7], while others consider artifacts as a set of attributes or variables [29,12,30,3]. Another alternative is to add an ontology represented by means of description logics on top of a relational database [31].…”

“…Lifecycles The lifecycle of a business artifact may be implicitly represented by using dynamic constraints in logic [26] or the tasks (or actions in the terminology of the papers) that make changes to the artifacts [27,28,11,31]. [7] derives the artifact's lifecycle from a BPMN model annotated with data.…”

“…For instance, [26,11,28,31] use a set of condition-action rules defined in logic. In [12], preconditions determine the execution of the actions; as such, they act as associations.…”

“…In general,they are described by using pre and postconditions (also called effects). Different variants of logic are used in [26,11,12,29,30,27,31] for this purpose. [28,5] omit the preconditions.…”

“…Our approach allows also automated reasoning from the business process models (as shown on [9,10]), while most of the existing proposals that handle reasoning are based on models which use languages grounded on complex mathematical notations [11,12,13] which are not practical at the business level.…”