Flexible exception handling in the OPERA process support system

Hagen, Claus; Alonso, Gustavo

doi:10.1109/icdcs.1998.679803

Cited by 56 publications

(30 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Such 'healing' actions are difficult to implement and in some cases such 'ad hoc' modifications to the workflow instance may not be possible. There is already a substantial amount of academic and industrial research on facilitating such 'ad hoc' modifications (for example, [14][15][16]) and it is important to see what can be leveraged when using BPEL.…”

Section: Very Long Running Grid Workflowsmentioning

confidence: 99%

On using BPEL extensibility to implement OGSI and WSRF Grid workflows

Slomiski

2005

Concurrency and Computation

View full text Add to dashboard Cite

show abstract

Section: Very Long Running Grid Workflowsmentioning

confidence: 99%

On using BPEL extensibility to implement OGSI and WSRF Grid workflows

Slomiski

2005

Concurrency and Computation

View full text Add to dashboard Cite

show abstract

“…Hence, as observed by many authors (e.g., [29,30]), it is difficult to model the handling of exceptional situations by means of activities and flows. In particular, the critical aspect in process design lies in modelling the occurrence of the exceptional situation.…”

Section: Wires: a Methodology For Developing Workflow Applicationsmentioning

confidence: 99%

WIRES: A Methodology for Developing Workflow Applications

et al. 2002

View full text Add to dashboard Cite

Workflow management systems are becoming a relevant support for a large class of business applications, and many workflow models as well as commercial products are currently available. While the large availability of tools facilitates the development and the fulfilment of customer requirements, workflow application development still requires methodological guidelines that drive the developers in the complex task of rapidly producing effective applications. In fact, it is necessary to identify and model the business processes, to design the interfaces towards existing cooperating systems, and to manage implementation aspects in an integrated way. This paper presents the WIRES methodology for developing workflow applications under a uniform modelling paradigm -UML modelling tools with some extensions -that covers all the life cycle of these applications: from conceptual analysis to implementation. High-level analysis is performed under different perspectives, including a business and an organisational perspective. Distribution, interoperability and cooperation with external information systems are considered in this early stage. A set of 'workflowability' criteria is provided in order to identify which candidate processes are suited to be implemented as workflows. Nonfunctional requirements receive particular emphasis in that they are among the most important criteria for deciding whether workflow technology can be actually useful for implementing the business process at hand. The design phase tackles aspects of concurrency and cooperation, distributed transactions and exception handling. Reuse of component workflows, available in a repository as workflow fragments, is a distinguishing feature of the method. Implementation aspects are presented in terms of rules that guide in the selection of a commercial workflow management system suitable for supporting the designed processes, coupled with guidelines for mapping the designed workflows onto the model offered by the selected system.

show abstract

“…-A process modeller can describe the standard activities and actions for a workflow process, and any deviations, using the same methodology; -It allows re-use of existing process components and aids in the development of fault tolerant workflows using pre-existing building blocks [37]; -Its modularity simplifies the logic and verification of the standard model, since individual worklets are less complex to build and therefore easier to verify than monolithic models; -It provides for a variety of workflow views of differing granularity, which offers ease of comprehensibility for all stakeholders; -It allows for gradual and ongoing evolution of the model, so that global modification each time a business practice changes or a deviation occurs is unnecessary; and -In the occurrence of an unexpected event, the process modeller needs simply to choose an existing worklet or build a new one for that event, which can be automatically added to the repertoire for current and future use as necessary, thus avoiding manifold complexities including downtime, model restructuring, versioning problems and so on.…”

Section: Discussionmentioning

confidence: 99%

Worklets: A Service-Oriented Implementation of Dynamic Flexibility in Workflows

Adams

Hofstede

Edmond

et al. 2006

On the Move to Meaningful Internet Systems 2006: CoopIS, DOA, GADA, and ODBASE

196

159

View full text Add to dashboard Cite

Abstract. This paper presents the realisation, using a Service Oriented Architecture, of an approach for dynamic flexibility and evolution in workflows through the support of flexible work practices, based not on proprietary frameworks, but on accepted ideas of how people actually work. A set of principles have been derived from a sound theoretical base and applied to the development of worklets, an extensible repertoire of self-contained sub-processes aligned to each task, from which a dynamic runtime selection is made depending on the context of the particular work instance.

show abstract

Flexible exception handling in the OPERA process support system

Cited by 56 publications

References 11 publications

On using BPEL extensibility to implement OGSI and WSRF Grid workflows

On using BPEL extensibility to implement OGSI and WSRF Grid workflows

WIRES: A Methodology for Developing Workflow Applications

Worklets: A Service-Oriented Implementation of Dynamic Flexibility in Workflows

Contact Info

Product

Resources

About