Data-Flow Anti-patterns: Discovering Data-Flow Errors in Workflows

Trčka, N.; Aalst, Wil M. P. van der; Sidorova, Natalia

doi:10.1007/978-3-642-02144-2_34

Cited by 148 publications

(136 citation statements)

References 13 publications

Supporting

Mentioning

135

Contrasting

Unclassified

Order By: Relevance

“…For instance, [23] represents the associations between services in a WFD-net (WorkFlow nets annotated with Data). The tasks are annotated with the data that is created, read or written by the task.…”

Section: Process-centric Approachesmentioning

confidence: 99%

Specifying Artifact-Centric Business Process Models in UML

Estañol

Queralt

Sancho

et al. 2015

Lecture Notes in Business Information Processing

View full text Add to dashboard 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.

show abstract

Section: Process-centric Approachesmentioning

confidence: 99%

Specifying Artifact-Centric Business Process Models in UML

Estañol

Queralt

Sancho

et al. 2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…Process model smells are closely related to anti-patterns [29,82], since both describe indicators for low process model quality. However, most of the described patterns constitute real modeling errors (potentiallly leading to deadlocks) and cannot be resolved through behavior-preserving refactorings.…”

Section: Related Workmentioning

confidence: 99%

Refactoring large process model repositories

Weber

Reichert

Mendling

et al. 2011

Computers in Industry

187

120

View full text Add to dashboard Cite

With the increasing adoption of process-aware information systems, large process model repositories have emerged. Typically, the models in such repositories are re-aligned to real-world events and demands through adaptation on a day-to-day basis. This bears the risk of introducing model redundancies and of unnecessarily increasing model complexity. If no continuous investment is made in keeping process models simple, changes will become more difficult and error-prone over time. Although refactoring techniques are widely used in software engineering to address similar problems, so far, no comparable state-of-the-art has evolved in the business process management domain. Process designers either have to refactor process models by hand or are simply unable to apply respective techniques at all. This paper proposes a catalogue of process model "smells" for identifying refactoring opportunities. In addition, it introduces a set of behavior-preserving techniques for refactoring large process repositories. The proposed refactorings enable process designers to effectively deal with model complexity by making process models better understandable and easier to maintain. The refactorings have been evaluated using large process repositories from the healthcare and automotive domain. To demonstrate the feasibility of the refactoring techniques, a proof-of-concept prototype has been implemented.

show abstract

“…Data dependencies can be formalized using workflow nets with data (WFDnets) as shown in [34]. WFD-nets extend WF-nets with data elements while identifying four relationships between activities (i. e., transitions) and data elements: read (activity a requires a data element d as input), write (activity a creates or updates data element d), destroy (activity a deletes data element d, and guard (data element d is used for routing).…”

Section: Dealing With Domain Knowledge and Data Dependenciesmentioning

confidence: 99%

“…The elements of a CRUD matrix can be translated into data dependencies in a WFD-net. In [34], nine data-flow anti-patterns are defined. For instance, the anti-pattern DAP 1 (Missing Data) describes the situation where some data element d needs to be accessed, i. e., read or destroyed, but either it has never been created or it has been deleted without having been created again.…”

Section: Dealing With Domain Knowledge and Data Dependenciesmentioning

confidence: 99%

See 1 more Smart Citation

Ensuring correctness during process configuration via partner synthesis

Aalst

Lohmann

Rosa

2012

Information Systems

View full text Add to dashboard Cite

Variants of the same process can be encountered within one organization or across different organizations. For example, different municipalities, courts, and rental agencies all need to support highly similar processes. In fact, procurement and sales processes can be found in almost any organization. However, despite these similarities, there is also the need to allow for local variations in a controlled manner. Therefore, many academics and practitioners have advocated the use of configurable process models (sometimes referred to as reference models). A configurable process model describes a family of similar process models in a given domain. Such a model can be configured to obtain a specific process model that is subsequently used to handle individual cases, for instance, to process customer orders. Process configuration is notoriously difficult as there may be all kinds of interdependencies between configuration decisions. In fact, an incorrect configuration may lead to behavioral issues such as deadlocks and livelocks. To address this problem, we present a novel verification approach inspired by the "operating guidelines" used for partner synthesis. We view the configuration process as an external service, and compute a characterization of all such services which meet particular requirements via the notion of configuration guideline. As a result, we can characterize all feasible configurations (i. e., configurations without behavioral problems) at design time, instead of repeatedly checking each individual configuration while configuring a process model.

show abstract

Data-Flow Anti-patterns: Discovering Data-Flow Errors in Workflows

Cited by 148 publications

References 13 publications

Specifying Artifact-Centric Business Process Models in UML

Specifying Artifact-Centric Business Process Models in UML

Refactoring large process model repositories

Ensuring correctness during process configuration via partner synthesis

Contact Info

Product

Resources

About