• 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 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.

• 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.

• 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 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.

• 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.

• Korean Management Science Review
• /
• v.20 no.2
• /
• pp.17-31
• /
• 2003

A workflow management system is a software system to support accurate execution, control and management of business processes. It has been known that the system automatically executes complex processes and effectively manages them to improve the productivities. However though existing systems assure the automatic execution of an individual process, there is a room for enhancement from the view of efficient execution of all the processes. In this paper, we propose a method of executing business processes efficiently by introducing the PERT/CPM techniques in the workflow management systems. We first consider the differences between workflow process models and PERT/CPM models, and then develop a method of calculating the critical path and slack time in workflow processes. This leads us to develop a dispatching rule that can guide task performers to prioritize their tasks to increase the efficiency of ail the processes. We have carried out a set of simulation experiments and analyzed the results to demonstrate the effectiveness of the proposed method.

• 연구논문집
• /
• 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.

• 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에 맞게 변환하였다.

• 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.