DECLARE: Full Support for Loosely-Structured Processes

By Maja Pesic, Helen Schonenberg, Wil M.P. van der Aalst. IEEE International Enterprise Distributed Object Computing Conference, 2007

636 citations recorded by the source corpus.

Traditional workflow management systems (WFMSs) are not flexible enough to support loosely-structured processes. Furthermore, flexibility in contemporary WFMSs usually comes at a certain cost, such as lack of support for users, lack of methods for model analysis, lack of methods for analysis of past executions, etc. DECLARE is a proto-type of a WFMS that uses a constraint-based process modeling language for the development of declarative models describing loosely-structured processes. In this paper we show how DECLARE can support loosely-structured processes without sacrificing important WFMSs features like user support, model verification, analysis of past executions, changing models at run-time, etc.

Subfields: Artificial Intelligence, Information Systems, Management Information Systems

View Paper: https://www.semanticscholar.org/paper/dc66448f90c5aea3a8444c9fc44681a45ddfcbad

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Information Systems

In Management Information Systems

Citations in the corpus

Automated Discovery of Process Models from Event Logs: Review and Benchmark (2017, neutral): “pressed using Declare constraints [106], [107].”
Declarative workflows: Balancing between flexibility and support (2009, methodology): “In order to enforce this, Declare constructs an automaton for each constraint [6, 34 ].”
Time prediction based on process mining (2011, methodology): “This demonstrates that the technique presented in this chapter can be used to actively provide predictions to users interacting with a PAIS (e.g., a workflow system like YAWL or Declare).”
Predictive Monitoring of Business Processes (2013, methodology): “In our proposed approach, a business constraint can be formulated in terms of LTL rules, as LTL (and its variations) is classically used in the literature for expressing business constraints on procedural knowledge [21].”
Artifact-Centric Business Process Models: Brief Survey of Research Results and Challenges (2008, neutral): “It would also be useful to adapt the relatively simple temporal-logic inspired declarative language of [ 38 ] to the artifact-centric setting.”