Process monitoring using sensors in YAWL

This article describes the architecture of a monitoring component for the YAWL system. The architecture proposed is based on sensors and it is realized as a YAWL service to have perfect integration with the YAWL systems. The architecture proposed is generic and applicable in different contexts of business process monitoring. Finally, it was tested and evaluated in the context of risk monitoring for business processes.

YAWL4Industry : reflections on using YAWL for industry projects

The Yet Another Workflow Language (YAWL) language and environment has been used to prototype, verify, execute and analyse business processes in a wide variety of industrial domains, such as telephony, construction, supply chain, insurance services, medical environments, personnel management and the creative arts. These engagements offer the YAWL researcher community a great opportunity to validate our research findings within an industry setting, as well as discovery of possible enhancements from the end user perspective. This paper describes three such industry projects, discusses why YAWL was chosen and how it was used in each, and reacts on the insights gained along the way.

Usability extensions for the worklet service

The YAWL Worklet Service is an effective approach to facilitating dynamic flexibility and exception handling in workflow processes. Recent additions to the Service extend its capabilities through a programming interface that provides easier access to rules storage and evaluation, and an event server that notifies listening servers and applications when exceptions are detected, which together serve enhance the functionality and accessibility of the Service's features and expand its usability to new potential domains.

Editor 3.0: Redesigining the YAWL user interface

It has long been a concern that the wider uptake of the YAWL environment may have been hindered by the usability issues identified in the current Process Editor. As a consequence, it was decided that the Editor be completely rewritten to address those usability limitations. The result has been the implementation of a new YAWL Process Editor architecture that creates a clear separation between the User Interface component layer and the core processing back end, facilitating the redesign of the default user interface. This new architecture also supports the development of multiple User Interface front ends for specific contexts that take advantage of the core capabilities the new Editor architecture has to offer.