A design pattern for integration of business process management systems
Ma, Chaoying, Bacon, Liz, Petridis, Miltos and Windall, Gill (2007) A design pattern for integration of business process management systems. In: Chang, Weide and Joshi, James B.D., (eds.) IRI 2007: Proceedings of the 2007 IEEE International Conference on Information Reuse and Integration. Institute of Electrical and Electronics Engineers, Inc., Piscataway, NJ, pp. 239-244. ISBN 9781424414994 (doi:10.1109/IRI.2007.4296627)Full text not available from this repository.
A cross-domain workflow application may be constructed using a standard reference model such as the one by the Workflow Management Coalition (WfMC)  but the requirements for this type of application are inherently different from one organization to another. The existing models and systems built around them meet some but not all the requirements from all the organizations involved in a collaborative process. Furthermore the requirements change over time. This makes the applications difficult to develop and distribute. Service Oriented Architecture (SOA) based approaches such as the BPET (Business Process Execution Language) intend to provide a solution but fail to address the problems sufficiently, especially in the situations where the expectations and level of skills of the users (e.g. the participants of the processes) in different organisations are likely to be different. In this paper, we discuss a design pattern that provides a novel approach towards a solution. In the solution, business users can design the applications at a high level of abstraction: the use cases and user interactions; the designs are documented and used, together with the data and events captured later that represents the user interactions with the systems, to feed an intermediate component local to the users -the IFM (InterFace Mapper) -which bridges the gaps between the users and the systems. We discuss the main issues faced in the design and prototyping. The approach alleviates the need for re-programming with the APIs to any back-end service thus easing the development and distribution of the applications
Actions (login required)