• Proceedings of the Korea Database Society Conference
• /
• 1998.09a
• /
• pp.525-543
• /
• 1998

This paper proposes a conceptual taxonomy of architectures far workflow management systems. The systematic classification work is based on a framework for workflow architectures. The framework, consisting of generic-level, conceptual-level and implementation-level architectures, provides common architectural principles for designing a workflow management system. We define the taxonomy by considering the possibilities for centralization or distribution of data, control, and execution. That is, we take into account three criteria. How are the major components of a workflow model and system, like activities, roles, actors, and workcases, concretized in workflow architecture？ Which of the components is represented as software modules of the workflow architecture？ And how are they configured and operating in the architecture？ The workflow components might be embodied, as active (processes or threads) modules or as passive (data) modules, in the software architecture of a workflow management system. One or combinations of the components might become software modules in the software architecture. Finally, they might be centralized or distributed. The distribution of the components should be broken into three: Vertically, Horizontally and Fully distributed. Through the combination of these aspects, we can conceptually generate about 64 software Architectures for a workflow management system. That is, it should be possible to comprehend and characterize all kinds of software architectures for workflow management systems including the current existing systems as well as future systems. We believe that this taxonomy is a significant contribution because it adds clarity, completeness, and "global perspective" to workflow architectural discussions. The vocabulary suggested here includes workflow levels and aspects, allowing very different architectures to be discussed, compared, and contrasted. Added clarity is obtained because similar architectures from different vendors that used different terminology and techniques can now be seen to be identical at the higher level. Much of the complexity can be removed by thinking of workflow systems. Therefore, it is used to categorize existing workflow architectures and suggest a plethora of new workflow architectures. Finally, the taxonomy can be used for sorting out gems and stones amongst the architectures possibly generated. Thus, it might be a guideline not only for characterizing the existing workflow management systems, but also for solving the long-term and short-term architectural research issues, such as dynamic changes in workflow, transactional workflow, dynamically evolving workflow, large-scale workflow, etc., that have been proposed in the literature.

• Asia pacific journal of information systems
• /
• v.11 no.1
• /
• pp.117-137
• /
• 2001

B2B(business-to-business) commerce has become the prime driver of contemporary electronic commerce. Under B2B commerce, corporations often must operate across organizational boundaries to share their business processes. Workflow management was proposed by Aalst(4, 5) to support several business partners that are involved in shared workflow processes in B2B commerce. We designed a messaging system for B2B workflow, where heterogeneous workflow management systems on each organization for trade were integrated. Based on Aalst's example in(4, 5), we analyzed B2B workflow by using class diagram, use case diagram, activity diagram, and statechart diagram of UML, and designed the messaging system, We also demonstrated a prototype system which was implemented by using Java API and XML. To compare with a holistic system such as EDI systems, the messaging system allows the business partners in B2B commerce to communicate with each other by dedicated messages and integrate each B2B interoperable workflow without any restrictions.

• Korean Management Science Review
• /
• v.16 no.1
• /
• pp.187-201
• /
• 1999

In this paper, we propose a multi-layered architecture of workflow management systems based on CORBA (Common Object Request Broker Architecture). The system aims to support product development processes in distributed environment. Many companies have started to adopt workflow management systems to manage and support their business processes. However, there are many problems in direct application of those systems to product development environments. These mainly resulted from the dynamic features of product development processes. It is strongly required to support dynamic processes as well as static and procedural ones in an integrated and consistent manner. To meet these requirements, a basic workflow management system has been developed as the core component of the integrated architecture. This performs the basic functions of workflow management system. Second, a dynamic workflow management system based on a bidding mechanism has been developed to manage processes that cannot be easily defined or are likely to be modified, Finally, an SGML workflow management system, which is the third layer in the architecture, has been developed to manage documents processing workflows by integration SGML documents contents and process information into the structured SGML document.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.6 no.8
• /
• pp.1325-1335
• /
• 2002

Workflow systems, automated business processing, have been generalized. In this paper, we propose a method to mine workflow specification on workflow logs. The method detects workflow specification considering cycle, AND and OR control flow between tasks. Also, we provide dynamic mining method to detect workflow specification in which log is generated.

• Journal of KIISE:Computer Systems and Theory
• /
• v.34 no.9
• /
• pp.385-394
• /
• 2007

In this paper, we present a workflow system which manages efficiently operations in workflow form. The workflow of this system is made up of concepts of meta-services for increasing reusability. Thus users can execute the workflow by calling their services. Also, GUI workflow editor is developed with the workflow system which provides users with convenience. Furthermore the workflow model is divided into 3-layers such as service, flow, and task layer for reusability and scalability of workflow. Therefore, this middleware can use grid resources effectively and offer convenience to users.

• The Journal of Information Technology and Database
• /
• v.5 no.1
• /
• pp.97-108
• /
• 1998

This paper proposes a conceptual taxonomy of architectures for workflow management systems. The systematic classification work is based on a framework for workflow architectures. The framework, consisting of generic-level, conceptual-level and implementation-level architectures, provides common architectural principles for designing a workflow management system. We define the taxonomy by considering the possibilities for centralization or distribution of data, control, and execution. That is, we take into account three criteria. How are the major components of a workflow model and system, like activities, roles, actors, and workcases, concretized in workflow architecture. Which of the components is represented as software modules of the workflow architecture\ulcorner And how are they configured and operating in the architecture\ulcorner The workflow components might be embodied, as active (processes or threads) modules or as passive (data) modules, in the software architecture of a workflow management system. One or combinations of the components might become software modules in the software architecture. Finally, they might be centralized or distributed. The distribution of the components should be broken into three: Vertically, Horizontally and Fully distributed. Through the combination of these aspects, we can conceptually generate about 64 software Architectures for a workflow management system. That is, it should be possible to comprehend and characterize all kinds of software architectures for workflow management systems including the current existing systems as well as future systems. We believe that this taxonomy is a significant contribution because it adds clarity, completeness, and global perspective to workflow architectural discussions. The vocabulary suggested here includes workflow levels and aspects, allowing very different architectures to be discussed, compared, and contrasted. Added clarity is obtained because similar architectures from different vendors that used different terminology and techniques can now be seen to be identical at the higher level. Much of the complexity can be removed by thinking of workflow systems. Therefore, it is used to categorize existing workflow architectures and suggest a plethora of new workflow architectures. Finally, the taxonomy can be used for sorting out gems and stones amongst the architectures possibly generated. Thus, it might be a guideline not only for characterizing the existing workflow management systems, but also for solving the long-term and short-term architectural research issues, such as dynamic changes in workflow, transactional workflow, dynamically evolving workflow, large-scale workflow, etc., that have been proposed in the literature.

• 연구논문집
• /
• s.30
• /
• pp.169-176
• /
• 2000

The Evolution of Workflow Managment consists of rhe automation of business procedures or "workflows" during which documents, information or tasks are passed from one participant to another in a way that is governed by rules or procedures. Workflow technologies have evolved from image management system, document management system, relational or object database systems, and electronic mail system. Workflow Management system has the benefits to improve better efficiency, process control,flexibility, business process. Automation of many business processes results in the elimination standdardizing working methods. Consistency in the processes leads to greater predictability in levels of response to customers and software control over processes enables their re-design in line with changing business needs, In this present study, we implement Electronic Approval System which is a kind of Workflow Management system using static and dynamic flow control information on the web environment.

• Journal of Internet Computing and Services
• /
• v.10 no.6
• /
• pp.205-217
• /
• 2009

Recently, many organizations such as companies or institutions have demanded induction of very large-scale workflow management system in order to process a large number of business-instances. Workflow vendors have focused on physical extension of workflow engines based on device-level clustering, so as to provide very large-scale workflow services. Performance improvement of workflow engine by simple physical-connection among computer systems which don't consider logical-level software architecture leads to wastes of time or cost for construction of very large-scale workflow service environment. In this paper, we propose workcase-based workflow architecture and implement a very large-scale workflow management system based on the architecture. We prove that software architectures to be applied on a workflow engine have an effect on scalability and performance through workcase response-time evaluation of our proposed system.

• The KIPS Transactions:PartA
• /
• v.17A no.2
• /
• pp.93-102
• /
• 2010

There are many complicated situations which could be occurred in users' surroundings, so it is required to develop automation services to provide users with appropriate services in ubiquitous computing environments. However, most of the current context-aware workflow systems express context-aware services only with a single workflow. Therefore, they have difficulties in providing users with various and composite services by combining different workflows. In this paper we propose a CAWL-based context-aware workflow system, where CAWL is a context-aware workflow language to express a composite workflow model by describing individual service workflows. The proposed system can provide users with various composite workflow services based on a service scenario, which is described with CAWL. And by reusing a number of single workflows to construct composite workflow services, it is possible to save time and effort to develop context-aware workflows.

• Proceedings of the CALSEC Conference
• /
• 2005.03a
• /
• pp.195-200
• /
• 2005

As the workflow systems are becoming complex and obscure, there are discrepancies between actual workflow process and designed process. Therefore, we have developed techniques for discovering workflow models. The starting point for such techniques is a so-called 'workflow log' containing information about the workflow process as it is actually being executed. This paper presents an algorithm of workflow process mining based on heuristic approach from the workflow log, which can be happen to business process system.