• 한국데이타베이스학회:학술대회논문집
• /
• 한국데이타베이스학회 1998년도 국제 컨퍼런스: 국가경쟁력 향상을 위한 디지틀도서관 구축방안
• /
• 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.

• Journal of Information Processing Systems
• /
• 제4권3호
• /
• pp.103-112
• /
• 2008

This paper proposes a policy adjuster-driven Grid workflow management system for collaborative healthcare platform, which supports collaborative heart disease diagnosis applications. To select policies according to service level agreement of users and dynamic resource status, we devised a policy adjuster to handle workflow management polices and resource management policies using policy decision scheme. We implemented this new architecture with workflow management functions based on policy quorum based resource management system for providing poincare geometrycharacterized ECG analysis and virtual heart simulation service. To evaluate our proposed system, we executed a heart disease identification application in our system and compared the performance to that of the general workflow system and PQRM system under different types of SLA.

• 정보기술과데이타베이스저널
• /
• 제5권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.

• 한국CDE학회지
• /
• 제8권1호
• /
• pp.58-65
• /
• 2002

Collaborative product commerce(CPC) involves many people working together with heterogeneous and distributed software applications. For such an environment, Workflow Management System(WFMS) can be useful for coordination of people, software agents and processes. It provides diverse services including automatic work muting, project management continuous process improvement and application integration. However, there are some limitations to apply WFMS to CPC environment due to inflexibility and lack of design support facilities. This paper identifies the problems and addresses possible approaches to overcome the difficulties.

• 인터넷정보학회논문지
• /
• 제20권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.

• 한국정보과학회논문지:정보통신
• /
• 제27권2호
• /
• pp.226-236
• /
• 2000

인터넷상의 워크플로우를 위한 최적의 워크플로우 시스템은 해당 워크플로우 시스템에 입력되는 워크플로우 종류에 의존적이다. 워크플로우 시스템이 처리해야 하는 워크플로우 종류가 다양하고 이들에 가장 적합한 워크플로우 시스템의 구조가 각각 서로 다르다고 볼 때, 하나의 워크플로우 시스템이 다양한 종류의 워크플로우 시스템 구조를 포용하고 입력되는 워크플로우 종류에 따라서 적절히 그것의 구조를 변경하는 것이 이상적이라고 할 수 있다. 본 논문에서는 다양한 워크플로우 시스템 구조를 포용하는 워크플로우 시스템 구조를 제안한다. 제안된 시스템에서는 태스크들을 위한 수행 객체를 객체 인스턴스 형태로 생성하고 이들을 시스템이 원하는 임의의 위치에 배치함으로써 그것의 구조를 변경할 수 있다. 초기의 시스템에 대해서 그 구조를 변경하면서 성능 평가를 수행하였으며 그 결과가 제시되었다. 제시된 결과에 의하면 인터넷상에 분산된 복수의 워크플로우 서버는 분산된 태스크에 대한 안정적인 운영 외에도 전체 시스템의 성능을 향상시키는 데에도 도움이 되는 것으로 확인되었다.

• 한국정보처리학회논문지
• /
• 제7권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.

• 한국CDE학회논문집
• /
• 제5권1호
• /
• pp.61-70
• /
• 2000

The design and development of a Web-based Workflow Management System (WfMS) is described in this paper. WfMSs are employed by many organizations to manage their business processes efficiently. The goal of this research is to provide an effective management of design processes in a distributed and heterogeneous environment-an environment in which workflow participants are geographically dispersed and use different computing platforms. We identify the requirements of WfMSs for the distributed and heterogeneous environment. We present an approach to applying the Web technology to was. The developed system is composed of three main modules: Worflow Engine, Web-based clients, and Process Designer. The workflow engine is implemented in pure Java for portability to heterogeneous platforms. furthermore, the client interfaces are all programmed using applets, and thus they can be readily accessed through the Internet/intranet. The Process Designer provides a build-time function of generating process specifications. Some important functions of the developed system are explained in this paper. A prototype system has been developed and applied to design processes. The system allows effective cooperation among designers who may be geographically separated.

• 인터넷정보학회논문지
• /
• 제10권6호
• /
• pp.205-217
• /
• 2009

최근 기업들은 조직 내외의 협업 또는 협력에 의해 발생되는 거대량의 업무들을 안정적으로 처리해줄 수 있는 초대형 워크플로우 관리 시스템의 등장을 요구하고 있다. 워크플로우 벤더들은 초대형 워크플로우 서비스를 지원하는 워크플로우 관리시스템을 구현하기 위해, 하드웨어들의 추가적 확장을 통한 워크플로우 관리 시스템의 성능 향상을 모색하고 있다. 그러나 워크플로우 관리 시스템의 소프트웨어적인 아키텍처를 고려하지 않은 단순한 물리적 확장은 시스템 구축에 소요되는 시간적 또는 비용적 낭비를 야기할 수 있다. 이러한 한계를 개선하기 위하여, 본 논문에서는 워크케이스 기반 워크플로우 아키텍처를 제안하고, 해당 아키텍처를 토대로 하는 초대형 워크플로우 관리 시스템을 구현한다. 또한 워크케이스 기반 초대형 워크플로우 관리 시스템에 관한 생성 반응 시간 관련 실험을 통해서, 논리적인 소프트웨어 아키텍처의 개선이 워크플로우 관리 시스템의 초대형성에 매우 큰 영향을 미칠 수 있음을 증명하고자 한다.

• 산업공학
• /
• 제10권3호
• /
• pp.63-73
• /
• 1997

This paper presents requirements for workflow management systems supporting CITIS. We propose an architecture of global workflow management system which aims at supporting external workflow among different organizations rather than internal one. The architecture consists of five key elements, that is process definition language, process graphic design tool, control engine, status monitoring tool, and interface models. For each of these elements, implementation requirements are presented and its major functions are described. A key concept to the CITIS standard is the integration of disparate systems in distributed environment. This leads us to place a special emphasis on the interface models that can enhance the interoperability between externally participating workflow systems. Two interface models for the global workflow management system are explained. CORBA, the most widely accepted standard for distributed object management, can be adopted to facilitate the integration. World Wide Web can be used for the underlying platform on which information is exchanged and the status of processes instances is monitored. The workflow management system can provide a ready and easy access to and management of the data for CALS environments.