Correctness issues in workflow management

Kamath, M.; Ramamritham, Krithi

doi:10.1088/0967-1846/3/4/002

Cited by 40 publications

(25 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…They are also used in office automation for assignment of tasks and execution monitoring (triggering alarms when deadlines are missed, exemption handling etc.) [32]. In the database community there has been extensive work on extending transactions for workflow applications [13,39,9,5,21,7,3].…”

Section: Related Workmentioning

confidence: 99%

Extending the data warehouse for service provisioning data

Kotidis

2006

Data & Knowledge Engineering

View full text Add to dashboard Cite

The last few years, there has been an extensive body of literature in data warehousing applications that primarily focuses on basket-type (transactional) data, common in retail industries. In this paper we focus on service provisioning data, that is data that is recorded internally in an organization for provisioning certain business related tasks. Coupling the recorded data with the underlying process and business-practice(s) that generate them is crucial for end-to-end analysis. Our framework is based on a graph description of the process (called a sketch) that is generating this data. Using this sketch, we formalize a new class of aggregate queries that consolidate data from a part of the process, based on a user defined path expression. We then show how to build a compact, non-redundant collection of summary (aggregate) tables and indices for this new type of queries. We first explore how to select a minimum set of views to answer queries with path-expressions over the given sketch. For queries that also include aggregation, we define two partial orders among the views. The first is used to pick the minimum set of aggregate views to answer any query with no false dismissals, while the second describes an augmented set that allows fewer false positives. Computing a non-materialized aggregate is done through appropriate rewriting of the user query. We describe two indexing schemes that use phantom (non-materialized) aggregate values to expedite query processing. Experimental results show these schemes to perform well on synthetic and real datasets.

show abstract

Section: Related Workmentioning

confidence: 99%

Extending the data warehouse for service provisioning data

Kotidis

2006

Data & Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…A tracking agent specification consists of a state model with qualitative abstractions based on the state model of the corresponding scheduler agent. Choosing the right abstractions is critical to the approach for formal correctness analysis [10]. The above steps are elaborated below using examples.…”

Section: Design Of Tracking Agentmentioning

confidence: 99%

Dynamic Change in Workflow-Based Coordination of Distributed Services

Bose

Matthews

2003

Self-Adaptive Software: Applications

View full text Add to dashboard Cite

Abstract. The rapid advances in distributed computing and network-based technologies have paved the path for a networked economy. In such a networked economy, software technologies for coordination of distributed services according to specific business policies or workflows will play an everincreasing role. A critical success factor in such automation is the handling of dynamic changes in the workflow in a dependable manner. This paper introduces an integrated architecture, called SWAP, for dynamic adaptation of workflow policies. It develops systematic methods for the design of agents that perform workflow policy change coordination and uses model-checking methods to analyze safety properties. We use the domain of E-commerce for the ordering of products to demonstrate the concepts and methods of our approach.

show abstract

“…A data model defines the structure of the product as a tree where each node is a component and the edges are composition links. Database community proposed a solution to collaborative updating of data : transaction concept has been extended to support long-duration activities and to solve the problem of constraint enforcement in software engineering and workflow applications (see [14], [1], [16], [9], [4], [11], [21], [22]). The main idea is to relax the ACID properties which would make data unavailable for a long time (since transactions may run for days or weeks).…”

Section: Related Workmentioning

confidence: 99%

ProjectLeader: A Constraint-Based Process Support for the Distributed Design of Component-Based Products

Blin

Fabret

Kapitskaia

et al. 2002

Software Product-Family Engineering

View full text Add to dashboard Cite

RésuméNous présentons, dans ce papier, un support d'aide à la conception collaborative de produits appartenant à une famille de produits. Le produit est modélisé par un arbre de composants et les contraintes de développement, utilisées pour guider le processus de conception, sont exprimées à l'aide d'un langage spécifique basé sur des expressions logiques. L'objectif principal de ProjectLeader est d'économiser le temps de conception en favorisant le travail simultané et en prévenant les retours en arrière. Ainsi, pour chaque intention de décision émise par un concepteur, ProjectLeader vérifie que la décision ne remettra pas en cause la possibilité d'atteindre un état correct du produit final, c'est-à-dire un état dans lequel toutes les contraintes sont vérifiées. Mots-clefs : conception collaborative, système à base de composants, modélisation et traitement de contraintes de conception, modélisation et traitement de la variabilité AbstractIn this paper we present a support that helps organizing distributed design of products belonging to a product family. We model the product to be developed as a component-based tree of object templates, develop a logic-based language that allows expressing diverse development constraints and use these constraints to guide the design process. The main objective of our support is to save time and development effort in increasing parallel work and avoiding roll-backs. For that, it reasons in terms of correctness of the future, final state of the product, and verifies that the product state after each operation allows the reacheability of such a state.

show abstract

Correctness issues in workflow management

Cited by 40 publications

References 13 publications

Extending the data warehouse for service provisioning data

Extending the data warehouse for service provisioning data

Dynamic Change in Workflow-Based Coordination of Distributed Services

ProjectLeader: A Constraint-Based Process Support for the Distributed Design of Component-Based Products

Contact Info

Product

Resources

About