A Light Workflow Management System Using Simple Process Models

Agostini, Alessandra; Michelis, Giorgio De

doi:10.1023/a:1008703327801

Cited by 67 publications

(42 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is recommended, for approaches using the a priori flexibility, to allow adapting a process instance when the system can not deal with a not anticipated event using its a priori flexibility capacities [1], [7], [14], [18], [21], [27], [38].…”

Section: Run Timementioning

confidence: 99%

“…Global: The transformation concerns the process definition [1], [8], [8], [11], [23], [28], [38], [47], [57], [60], [62]. The classical problem concerns the current instances of this type.…”

Section: Run Timementioning

confidence: 99%

“…Ad hoc: a non pre-defined action on instances or definition is created during the execution to modify the behavior of the BP [1], [8], [11], [14], [27], [28], [47]. The target process definition is not known.…”

Section: Run Timementioning

confidence: 99%

“…instances are executed according to the old model until they reach a safe state. This strategy is used in Milano [1] and Wasa2 [62].…”

Section: Run Timementioning

confidence: 99%

See 3 more Smart Citations

A Survey on the Flexibility Requirements Related to Business Processes and Modeling Artifacts

Nurcan

2008

Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008)

View full text Add to dashboard Cite

show abstract

Section: Run Timementioning

confidence: 99%

Section: Run Timementioning

confidence: 99%

Section: Run Timementioning

confidence: 99%

“…instances are executed according to the old model until they reach a safe state. This strategy is used in Milano [1] and Wasa2 [62].…”

Section: Run Timementioning

confidence: 99%

See 2 more Smart Citations

A Survey on the Flexibility Requirements Related to Business Processes and Modeling Artifacts

Nurcan

2008

Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008)

View full text Add to dashboard Cite

show abstract

“…Solutions to the related problem of dynamic change i.e., how to transform the process without suspending all its instances or waiting for all instances to have come to conclusion, of the possibility of creating inconsistent states of process instances have been studied in formal frameworks, typically defined by Petri nets. Examples of them are: WF-nets [13,15], Flow Nets [16,17], and MILANO nets [18,19] (that is, marked, acyclic Free-Choice Petri Nets).…”

Section: Related Workmentioning

confidence: 99%

Resource Disconnection Management in MANET Driven by Process Time Plan

Leoni¹,

Rosa²,

Dustdar³

et al. 2007

Proceedings of the 1st International ICST Conference on Autonomic Computing and Communication Systems

View full text Add to dashboard Cite

The use of mobile ad hoc networks (manets) and of adaptive process management systems, able (i) to enact cooperative processes among the on-the-field operators and (ii) to cope with disconnection anomalies, is an effective tool in emergency management. In this paper, we present the architecture of MOBIDIS, a novel manet-based process management system for emergencies, and we describe the novel techniques proposed for adaptiveness of the process enactment. A prototype implementation and experiments are presented.

show abstract

Software Tools

Grundy

Hosking

2002

Encyclopedia of Software Engineering

View full text Add to dashboard Cite

The demand for computer software applications steadily increases as numbers of users, problem domains, and application areas grow the need for good tools to support the myriad of activities that occur during software development is thus greater than ever. This article provides an overview of current practice in software tool features and usage. It also surveys research work in the area of software tools, indicating recent and likely near‐future trends in tools development. A section outlines recent directions in software process evolution, product domains and people management. As different software tools are used throughout the software process for different activities, changes in processes, products and project organization have introduced a variety of new demands on tools and tool developers. A categorization of software tools aligned with software process activities is then presented, including examples of tools in the various categories, along with a brief explanation of common terms used to describe software tools. We describe key elements of the structure of software tools, ranging from repository and data management to multiple‐view presentation and editing. We then focus on the key issue of tool integration, outlining current approaches to integration, current research trends, and likely near‐future integration support in software tools. We describe various strategies for supporting collaborative work with different software tools, facilitating improved teamwork with tools. We review and discuss current research, practice, and likely trends in automated support in software tools, alleviating developers of tedious tasks and helping manage ever‐growing software complexity. We conclude with a summary of some important factors in successful tool development and deployment.

show abstract

A Light Workflow Management System Using Simple Process Models

Cited by 67 publications

References 19 publications

A Survey on the Flexibility Requirements Related to Business Processes and Modeling Artifacts

A Survey on the Flexibility Requirements Related to Business Processes and Modeling Artifacts

Resource Disconnection Management in MANET Driven by Process Time Plan

Software Tools

Contact Info

Product

Resources

About