Figure 1 - uploaded by Dongsoo Han
Content may be subject to copyright.
Source publication
Patterns in the domain of workflow management systems(WFMS) have been written. Meszaros and Brown wrote a pattern language for workflow systems[11]. They considered the workflow facility a component of a system and described the process for creating that system. Thus their pattern language falls short of describing workflow facilities managed by an...
Contexts in source publication
Context 1
... Finally, this process will end after the order department sends the delivery confirmation message to the customer. Figure 1 shows this process in the form of an activity diagram. ...
Citations
With each passing day of enterprise business, work flow needs to be improved frequently, which proposes high requirements to the process definition tool. Through briefly introducing the concept of workflow and workflow management system, the foundational and importance of process definition has been pointed out in the workflow management system. Finally, giving the Design and Implementation of Process Definition Tool.
In this paper, we propose a framework supporting dynamic interoperation between heterogeneous workflow systems and workflow-based dynamic Enterprise Application Integration (EAI). To this end, based on Subflow Task Model and Multi-Tiered Dynamic State Transition Model, four major components are defined: The workflow engine, Adapter, Service Interface Repositories (SIRs), and XML messages. Workflow engine provides user for location transparency of sub-processes by encapsulating and dynamically binding both internal and external sub-processes. As a middleware, the adapter achieves location and system transparency with the help of the workflow engine by encapsulating and dynamically binding external sub-processes to its super-process. SIRs contains the service information of other systems. The Local SIR (LSIR) within an organization is an important component for dynamic EAI. The adapter looks up the LSIR at run time when it tries to find external services. Several XML messages enable the communications between heterogeneous workflow systems and enterprise applications.
An error-comprising workflow definition of mission critical business process might incur serious problems to an enterprise. Although workflow designer is responsible for the error-comprising workflow definitions, workflow system has to be equipped with an intelligent workflow modeling tool preventing workflow designers from specifying error-comprising workflow definitions. Faults and mistakes of process designers have to be detected and reported to them by the tool at workflow build time. Access conflicts and improper specification of exceptions are two typical examples of such an error-comprising workflow definition. In this paper, we develop an access conflict detection and an uncaught exception detection techniques. A simple workflow definition language, named SWDL, is developed and the techniques are successfully developed on SWDL using Set Constraint System. With slight modifications and scope restrictions, the proposed techniques can be used in any workflow definition language either by translating it into SWDL or by referring to the techniques for the developing its own techniques. This indicates that general conventional programming language analysis techniques can be used in the analysis of workflow definitions by introducing an intermediate workflow definition language and developing analysis techniques on it.
When a workflow process is related to many organizations and a
diverse set of applications at run time, many approaches usually use
subprocess tasks to represent other systems' services: the subprocess
task represents a single service. However, if a subprocess task needs to
represent multiple subprocesses and moreover the number and execution
flow of them are not known until run-time, conventional approaches
cannot handle the situation because they must pre-define all the
potentially reachable paths. In this paper we propose a framework for
dynamic workflow interoperation using the multi-subprocess task. In the
framework, the multi-subprocess task is designed to handle preliminarily
unknown multiple subprocesses. Based on the multi-subprocess task, four
major components are defined and implemented to support the dynamic
workflow interoperation. We analyzed our framework using an example
scenario and found that the framework brings many advantages in terms of
automaticity, adaptability, business efficiency, and physical resources
