Reasoning on UML Data-Centric Business Process Models

Lecture Notes in Computer Science

Sancho

Teniente

2015

Self Cite

Abstract. This paper presents a way of checking the correctness of artifact-centric business process models defined using the BAUML framework. To ensure that these models are free of errors, we propose an approach to verify (i.e. there are no internal mistakes) and to validate them (i.e. the model complies with the business requirements). This approach is based on translating these models into logic and then encoding the desirable properties as satisfiability problems of derived predicates. In this way, we can then use a tool to check if these properties are fulfilled.

Section: Introductionmentioning

confidence: 99%

Verification and Validation of UML Artifact-Centric Business Process Models

Lecture Notes in Computer Science

Sancho

Teniente

2015

Self Cite

“…These languages can be understood by domain experts and they provide a high level of abstraction. Another advantage of using these combination of models is that, as we have shown in previous work [9], it is possible to perform semantic reasoning on the models to ensure that they fulfill the user requirements.…”

Section: Discussionmentioning

confidence: 99%

“…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.…”

Section: Introductionmentioning

confidence: 99%

Specifying Artifact-Centric Business Process Models in UML

Lecture Notes in Business Information Processing

Queralt

Sancho

et al. 2015

Self Cite

Abstract. In recent years, the artifact-centric approach to process modeling has attracted a lot of attention. One of the research lines in this area is finding a suitable way to represent the dimensions in this approach. Bearing this in mind, this paper proposes a way to specify artifact-centric business process models by means of well-known UML diagrams, from a high-level of abstraction and with a technology-independent perspective. UML is a graphical language, widely used and with a precise semantics.

“…In this paper, we adopt the instantiation of BALSA in [8,9], representing the aforementioned dimensions using UML [15] and OCL [19]. Both UML and OCL are standard languages generally used for, but not limited to, conceptual modeling.…”

Section: The Bauml Frameworkmentioning

confidence: 99%

“…Since k is a pre-defined string, each decrement is different from the others, and this is why each specific decrement is mapped to a separate operation in P bu run . Considering the case of instruction 7 : CDEC (1,2,9), the right part of Figure 6 represents the new data configuration after the execution of this step by the connection that is currently at the end of the right chain.…”

Section: Proofmentioning

confidence: 99%

Verifiable UML Artifact-Centric Business Process Models

Calvanese

Montali

Proceedings of the 23rd ACM International Conference on Conference on Information and Knowledge Management

et al. 2014

Self Cite

Artifact-centric business process models have gained increasing momentum recently due to their ability to combine structural (i.e., data related) with dynamical (i.e., process related) aspects. In particular, two main lines of research have been pursued so far: one tailored to business artifact modeling languages and methodologies, the other focused on the foundations for their formal verification. In this paper, we merge these two lines of research, by showing how recent theoretical decidability results for verification can be fruitfully transferred to a concrete UML-based modeling methodology. In particular, we identify additional steps in the methodology that, in significant cases, guarantee the possibility of verifying the resulting models against rich first-order temporal properties. Notably, our results can be seamlessly transferred to different languages for the specification of the artifact lifecycles.