• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.13 no.8
• /
• pp.4108-4122
• /
• 2019

Workflow process mining is becoming a more and more valuable activity in workflow-supported enterprises, and through which it is possible to achieve the high levels of qualitative business goals in terms of improving the effectiveness and efficiency of the workflow-supported information systems, increasing their operational performances, reducing their completion times with minimizing redundancy times, and saving their managerial costs. One of the critical challenges in the workflow process mining activity is to devise a reasonable approach to discover and recognize the bottleneck points of workflow process models from their enactment event histories. We have intuitively realized the fact that the iterative process pattern of redo-activities ought to have the high possibility of becoming a bottleneck point of a workflow process model. Hence, we, in this paper, propose an algorithmic approach and its implementation to discover the redo-activities and their performers' involvements patterns from workflow process enactment event logs. Additionally, we carry out a series of experimental analyses by applying the implemented algorithm to four datasets of workflow process enactment event logs released from the BPI Challenges. Finally, those discovered redo-activities and their performers' involvements patterns are visualized in a graphical form of information control nets as well as a tabular form of the involvement percentages, respectively.

• Journal of the Korea Society for Simulation
• /
• v.16 no.4
• /
• pp.77-86
• /
• 2007

Web services are considered as the critical component in the business plans of corporations as they offers the potential for creating highly dynamic and versatile distributed applications that span across business boundaries. Web Service Orchestration studies composition of already-existing web services to create new value-added services. The composite web services could be executed in a centralized or peer-to-peer(P2P) orchestration model. Compared with centralized-orchestration model, the P2P-based orchestration model provides better scalability, reliability, and performance for the overall services. However, recent P2P-orchestration solutions have limitation in supporting complex workflow patterns. Therefore, they could not effectively handle sophisticated business workflow, which contains complex workflow patterns. In this paper, we propose the WORKGLOW system, which can deal with complex workflow patterns while it is able to perform composite services in P2P orchestration manner. Comparing with centralized orchestration systems, the WORKGLOW brings up more business logic advantages, better performance, and higher flexibility with only a little overhead.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.10 no.3
• /
• pp.976-995
• /
• 2016

Workflow scheduling is one of the challenging problems in cloud computing, especially when service reliability is considered. To improve cloud service reliability, fault tolerance techniques such as fault recovery can be employed. Practically, fault recovery has impact on the performance of workflow scheduling. Such impact deserves detailed research. Only few research works on workflow scheduling consider fault recovery and its impact. In this paper, we investigate the problem of workflow scheduling in clouds, considering the probability that cloud resources may fail during execution. We formulate this problem as a multi-objective optimization model. The first optimization objective is to minimize the overall completion time and the second one is to minimize the overall execution cost. Based on the proposed optimization model, we develop a heuristic-based algorithm called Min-min based time and cost tradeoff (MTCT). We perform extensive simulations with four different real world scientific workflows to verify the validity of the proposed model and evaluate the performance of our algorithm. The results show that, as expected, fault recovery has significant impact on the two performance criteria, and the proposed MTCT algorithm is useful for real life workflow scheduling when both of the two optimization objectives are considered.

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

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

• Journal of Internet Computing and Services
• /
• v.13 no.2
• /
• pp.73-86
• /
• 2012

This paper theoretically derives an algorithm to discover a new type of social networks from workflow models, which is termed workflow-based social network intelligence. In general, workflow intelligence (or business process intelligence) technology consists of four types of techniques that discover, analyze, monitor and control, and predict from workflow models and their execution histories. So, this paper proposes an algorithm, which is termed ICN-based workflow-based social network intelligence discovery algorithm, to be classified into the type of discovery techniques, which are able to discover workflow-based social network intelligence that are formed among workflow performers through a series of workflow models and their executions, In order particularly to prove the correctness and feasibility of the proposed algorithm, this paper tries to apply the algorithm to a specific workflow model and to show that it is able to generate its corresponding workflow-based social network intelligence.

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

• Asia pacific journal of information systems
• /
• v.11 no.3
• /
• pp.149-164
• /
• 2001

In this paper, an adaptive workflow management system, called K-WFMS, is proposed. The K-WFMS integrates database system and knowledge-based system to automate business processes that are executed with complex and various business rules such as task scheduling, role resolution, and exception handling rules. The K-WFMS is adaptable in the sense that it allows its users to change workflow schema in the course of workflow execution as well as it provides rule-based modeling constructs to handle predictable exceptions during workflow modeling. The overall architecture and implementation of K-WFMS are explained, and the change propagation mechanism to maintain validity of workflow model is suggested.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.2
• /
• pp.61-70
• /
• 2008

This paper describes case studies on workflow impact analyze with an enterprise ontology (EO). We build the EO with an ontology editor $Prot{\acute{e}}g{\acute{e}}$ and integrate concepts of enterprise architecture and a process model into it to expand the EO. We use the expanded EO and Prolog query rules to analysis workflow dependency relations from the perspectives of routing, data and role. Through this, we analyze impact of changes in workflow process. Moreover, we have found the effectiveness of the EO and $Prot{\acute{e}}g{\acute{e}}$ in modeling business management and, in particular, workflow representation and management.

• Journal of Internet Computing and Services
• /
• v.6 no.6
• /
• pp.107-115
• /
• 2005

A workflow procedure has recently become more complicated and large scaled. In this paper, we propose an advanced workflow modeling methodology, called a fragment driven cooperative workflow modeling methodology. which enables several real workflow designers to cooperatively define a workflow model. The methodology is a Bottom-Up approach in terms of integrating a set of fragment ICNs to compose a complete workflow model. Each fragment ICN is defined by each participant in the cooperative modeling session, We also use the ICN based formal description and the ICN based graphical notation as well. Finally, we prove the feasibility of the methodology by implementing a cooperative workflow modeling system.