• Journal of KIISE:Information Networking
• /
• v.27 no.2
• /
• pp.226-236
• /
• 2000

The best-fit workflow management system architecture for the workflows in the internet is dependent on the workflow types that should be processed in the workflow system. Since a workflow management system should accommodate various kinds of workflows requiring different workflow system architectures respectively as their best-fit workflow system architectures, it is ideal that a workflow system covers various workflow system architectures and changes its architecture according to the input workflow types. In this paper we propose a workflow system architecture that covers various workflow architectures within a single workflow system. The system changes its architecture by creating an execution object for a task in the form of an object instance and placing the created object instance to anywhere the system wants to. Performance test has been performed on the early versions of the system changing its architectures, and the results are illustrated. The results show that the distributed multiple workflow servers in the internet can contribute to not only reliable control of the distributed tasks but also enhancing total throughput of a workflow system.

• IE interfaces
• /
• v.17 no.2
• /
• pp.190-199
• /
• 2004

Recently, many enterprises are introducing a workflow management system for the successful implementation of BPR(Business Process Reengineering). Proposed in this study is the workflow management system which has a light-weight component structure and an XPDL(XML Process Definition Language) file interpretation facility. The XPDL is the standard process definition exchange format developed by WfMC(Workflow Management Coalition). The major causes of inefficiency at current implementations of workflow management systems are the centralized workflow engine structure and the use of proprietary workflow definition format among most solutions. The proposed light-weight component structure in this study is the intermediate structure that takes the strength of both centralized and distributed workflow engines. And a prototype workflow system which uses an XPDL process definition file as input is developed through the thorough analysis of functional requirements.

• Proceedings of the Safety Management and Science Conference
• /
• 2006.11a
• /
• pp.415-426
• /
• 2006

Many technical and nontechnical issues hinder enterprise wide workflow management. The most significant technical issue is the inability to deal with the heterogeneity among users, workflow types, and WFMSs. Not all users demand the same workflow functionality, so user interfaces of different levels of sophistication are required. Because workflow types cannot always be fully predefined, they often need to be adjusted or extended during execution. Unlike relational database management systems, however, each WFMS often has differing workflow metamodels. This leads to incompatibility between WFMSs, making integration into an environment comprising many heterogeneous WFMSs a troublesome and sometimes impossible task. Current Workflow system consists mainly of Database system. It contains some problems like that the integration relationship among system processes cant be expressed properly. This research has been focused on two phases that should be considered in the Workflow system. First of all, the first phase is the analysis phase; one of its role is to figure out independent execution task unit(Workflow component). The second phase is design phase that provides with the framework to execute these task units actively. The Workflow component extraction method in the analysis phase uses a analysis method called C-C Net and, in the design phase, the architecture that makes the these Workflow component executed actively is provided. Through this research, each process is divided into a task unit and more effective Workflow system could be formed by executing these units actively. Current system layer calls task units, on the other hand, the Workflow system this research implemented provides with the architecture that places a layer between them that controls task units actively.

• Journal of Internet Computing and Services
• /
• v.20 no.3
• /
• pp.77-84
• /
• 2019

Workflow management system is a system that manages the workflow model which defines the process of work in reality. We can define the workflow process by sequencing jobs which is performed by the performers. Using the workflow management system, we can also analyze the flow of the process and revise it more efficiently. Many researches are focused on how to make the workflow process model more efficiently and manage it more easily. Recently, many researches use the workflow log files which are the execution history of the workflow process model performed by the workflow management system. Ourresearch group has many interests in making useful knowledge from the workflow event logs. In this paper we use XES log files because there are many data using this format. This papersuggests what are the cardinalities of the temporal workcases and how to get them from the workflow event logs. Cardinalities of the temporal workcases are the occurrence pattern of critical elements in the workflow process. We discover instance cardinalities, activity cardinalities and organizational resource cardinalities from several XES-based workflow event logs and visualize them. The instance cardinality defines the occurrence of the workflow process instances, the activity cardinality defines the occurrence of the activities and the organizational cardinality defines the occurrence of the organizational resources. From them, we expect to get many useful knowledge such as a patterns of the control flow of the process, frequently executed events, frequently working performer and etc. In further, we even expect to predict the original process model by only using the workflow event logs.

• Journal of Internet Computing and Services
• /
• v.17 no.5
• /
• pp.131-139
• /
• 2016

This paper presents a workflow validation method for data-intensive graphical workflow models using real-time workflow tracing mode on data-intensive workflow designer. In order to model and validate workflows, we try to divide as modes have editable mode and tracing mode on data-intensive workflow designer. We could design data-intensive workflow using drag and drop in editable-mode, otherwise we could not design but view and trace workflow model in tracing mode. We would like to focus on tracing-mode for workflow validation, and describe how to use workflow tracing on data-intensive workflow model designer. Especially, it is support data centered operation about control logics and exchange variables on workflow runtime for workflow tracing.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.139-146
• /
• 2006

This paper describes the design and implementation details of a distributed transactional workflow monitoring system. There have been prevalent research and development trends in the workflow literature - workflow systems tend to be completely distributed architectures to support very large-scale workflow applications on object-oriented and internet-based infrastructures. That is, the active (object), distributed (architecture), system-oriented (transaction), and large-scale (application) workflow systems are the key targets in terms of the research and development aspects. While the passive, centralized, human-oriented, and small/medium scale workflow systems are the typical instances of the traditional workflow systems. Unlike in the traditional (the client-server architecture) workflow systems, the workflow monitoring features should not be easily supported in the recent (the fully distributed architecture) workflow systems. At the same time, they need a set of additional monitoring features, such as gathering and displaying statistical (or overload status) information of the workflow architectural components dispersed on the internet. We, in this paper, introduce the additional workflow monitoring features that are necessarily required for the recent workflow systems, and show how to embed those features into a web-based distributed workflow system.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2002.05a
• /
• pp.280-284
• /
• 2002

최근 Workflow System의 컴퍼넌트화는 필수적인 것으로 인식되고 잇다. 컴퍼넌트화의 장점으로는 유지, 보수의 용이성과 다른 어플리케이션과의 원활한 통합을 들 수 있고, 컴퍼넌트 기반의 Workflow System은 e-business infra를 형성하는데 필수적이다. 따라서 본 연구에서는 기업 내부의 포로세스를 관리해 주는 Workflow System을 컴퍼넌트형태로 설계하여 가장 진보된 형태의 Workflow System의 기반을 마련한다. 본 논문에서는 RUP방법론에 다라 use case분석, class diagram분석을 통해서 DISFlow(Daewoo Information Workflow)를 EJB Architecture에 맞게 변환하였다.

• Journal of KIISE:Databases
• /
• v.28 no.3
• /
• pp.395-405
• /
• 2001

In this paper, we analyze workflow management system in programming language aspects. Many workflow characteristics such as workflow relevant data, workflow control structures, and workflow application invocations are studied and compared with those of distributed parallel programs. Although there exist minor differences between them, we found that there exist surprisingly many analogies between them. Based on this observation, we suggest to view workflow management system as distributed parallel program development platform. This new view on workflow management system provides users consistent view on workflow and workflow management system and with this view workflow management system designer can cope with arbitrary requests from the users keeping design consistency. Moreover the analogy between workflow and program provides a basis to apply program analysis techniques to the analysis of workflow.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.5S
• /
• pp.1609-1619
• /
• 2000

Workflow means the automation of a business process, in which documents, information or tasks are transferred among participants for business action according to a set of procedural rules, and workflow management system is a system which defines, creates and manages the execution of workflow running one or more workflow engines. In this research, necessity of standardizing current workflow systems is recognized, and problems such as interoperability of current systems, dynamic adaptation to changing business environment and lacking of assessment, management and auditing of business processes are analyzed so that the design and implementation of a workflow system is focused on to offer a solution to the problems. The system is designed and implemented to change dynamically on Run-Time the processes definition defined on Build-Time, and interoperability is enabled by developing workflow engine and related modules based on the WfMC specifications and APIs.

• Proceedings of the CALSEC Conference
• /
• 2003.09a
• /
• pp.230-235
• /
• 2003

A Workflow Management System is one which provides procedural automation of a business process by management of the sequence of work activities. The existing workflow management systems have limitation of interaction among application systems. In this paper, we propose a new workflow management system that can be adapted in dynamically changed paradigm of distributed computing by using Web Service. System Architecture and prototyping execution model of the system is described in BPEL4WS.