|
Comparison |
WIDE |
WWWorkflow |
Liaison |
Micro workflow |
MOVE-FLOW |
1 |
Targeted User |
End user |
Web Developer |
All |
Application Developers |
All |
2 |
Application integration |
C++ over Unix |
Web applications |
Java Applications |
Smalltalk |
All |
3 |
Interoperability through standard Webservice |
No |
No |
No |
No |
Yes |
4 |
Can use Process modeled in standard format |
No |
No |
No |
No |
Yes |
5 |
Process modeled using |
Database |
WFL |
Valmont |
Smalltalk inheritance |
Standard XPDL |
6 |
Support Distributed environment |
Yes |
No |
Yes |
No |
Yes |
7 |
Interfacing with other WfMS |
No |
No |
Limited |
No |
Yes |
8 |
Expandability |
No |
No |
Yes |
Yes |
Yes |
9 |
Interface to render user task |
Yes |
Yes |
Yes |
No |
Yes |
10 |
Adopt SaaS deployment model |
No |
No |
No |
No |
Yes |
WfMSs comparison
As shown in the comparison, all mentioned system doesn’t support standard process modeling language. They don't use webservice as standard interface to integrate with other applications. And they are not built to support SaaS deployment model.
This thesis proposes Software as a Service workflow management system (MOVE-FLOW) engine architecture. MOVE-FLOW engine is a workflow engine that Supports SaaS concept and in turn capable of controlling the flow of applications; built on different working environments, and remotely over the web. Also MOVE-FLOW tires to address drawbacks of Current WfMS.
For the proposed WfMS examples:
The architecture of WIDE is focused on database technology. The workflow processes are managed through extended transaction processing techniques and active rules management. The persistence is implemented by the relational database technology. Its design is based on client/server architecture on top of Oracle. WIDE is tightly coupled to the DBMS technology used. This technique makes WIDE less flexible and hard to extend. MOVE-FLOW is component based which makes all elements of the system loosely coupled and the system can be extended easily.
WWWorkflow focuses on providing engine functionality through the web but not how to extent system functionality. Also it doesn’t focus on developers to benefit from its components.
Micro-workflow targets software developers and provides the type of workflow functionality they need in object-oriented applications. Executing a process over heterogeneous systems is not the focus of this work.
Liaison targets solving the distribution nature of the workflow system. But it didn’t provide a clear methodology to control the process execution over the web. Interoperability and communication over the web is not defined in the structure of Liaison engine.
MOVE-FLOW WFMS tries to handle all those drawbacks. It supports workflow execution over the web. It also targets developers and provide extendable interface to give the developer the chance to extend the system and to fully integrate their application with the engine.
The structure is component based to be extendable. Also it uses Service Oriented Architecture SOA to enable exposing engine functionality to external systems, in Local Network or over the web. MOVE-FLOW supports querying system services without the need to query engine itself. Also developers can subscribe to engine services to monitor execution and build their own traceability mechanism.
MOVE-FLOW architecture is based on a Component Based Architecture mixed with Service Oriented Architecture technologies to enable engine to host other organization process, those processes control the flow of application built on different environment over the web. | 
News
Events
