• 인터넷정보학회논문지
• /
• 제9권6호
• /
• pp.89-97
• /
• 2008

최근 기업 및 조직들은 대규모 엔터프라이즈 환경에서 발생하는 대량의 업무 인스턴스들을 안정적으로 처리해줄 수 있는 초대형 워크플로우 관리 시스템 도입에 대한 활성화를 요구하고 있다. 워크플로우 벤더들은 초대형 워크플로우 서비스를 제공하는데 적합한 워크플로우 엔진을 구현하기 위해, 하드웨어들의 추가적인 연계를 통한 워크플로우 엔진의 물리적 성능 확장에 초점을 맞추고 있다. 그러나 워크플로우 엔진의 소프트웨어적인 아키텍처를 고려하지 않은 단순한 물리적 성능 확장은 불필요한 서비스 구축 시간 및 비용의 낭비를 야기할 수 있다. 이러한 한계를 개선하기 위하여, 본 논문에서는 워크플로우 엔진을 구성하는 소프트웨어 아키텍처를 고려하는 논리적 관점에서의 성능 향상을 위한 접근 방법을 모색한다. 이를 위해 워크플로우 서비스의 하드웨어 인프라를 전형적인 단위 클라이언트-서버 구조를 채택하고 있다고 가정하고, 대다수의 워크플로우 벤더들이 채택하고 있는 액티비티 인스턴스 아키텍처 기반 워크플로우 엔진과 본 논문에서 제안하는 워크케이스 아키텍처 기반 워크플로우 엔진의 성능을 비교 측정한다. 우리는 성능 측정의 분석 결과를 통해 논리적인 소프트웨어 아키텍처가 워크플로우 엔진의 초대형성에 많은 영향을 미칠 수 있음을 보여주고자 한다.

• 경영과학
• /
• 제16권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.

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

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

• 정보처리학회논문지D
• /
• 제13D권1호
• /
• pp.139-146
• /
• 2006

본 논문에서는 분산 트랜잭션 워크플로우 모니터링 시스템의 설계 및 구현에 관하여 기술한다. 워크플로우 인스턴스들의 실행 상태 관리를 주요 목적으로 하는 전통적인 워크플로우 시스템의 모니터링 기능은 워크플로우의 초대형화와 트랜잭션화를 특징으로 하는 분산형 트랜잭션 워크플로우 시스템에서는 워크플로우의 처리 상태 관리뿐만 아니라 구조적인 정보의 수집, 통계 정보 제공, 사용자들의 처리 상태 정보 등과 같은 다양한 부가적인 정보 처리 및 관리 기능을 제공하는 분산형 모니터링 서비스를 필요로 한다. 본 논문에서는 이러한 분산형 트랜잭션 워크플로우 시스템에서 필수적으로 요구되는 새로운 워크플로우 모니터링의 특징을 확장 정의하고, 이를 지원하는 점 기반의 분산 트랜잭션 워크플로우 모니터링 시스템의 상세 설계 및 이의 구현 방안을 소개한다.

• 한국데이타베이스학회:학술대회논문집
• /
• 한국데이타베이스학회 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.

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

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

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

• 대한안전경영과학회:학술대회논문집
• /
• 대한안전경영과학회 2006년도 추계공동학술대회
• /
• 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.

• KIEAE Journal
• /
• 제16권5호
• /
• pp.21-28
• /
• 2016

Purpose: The Objective of this study is to explore the capabilities of an integrated modelling and simulation workflow when applied to an experiment-based research process, aimed at deriving daylight optimization strategies specific to tall buildings. Methods: Two methods were devised to apply this workflow with the help of DIVA and Rhino/Grasshopper. The first method is a multiple variant analysis by setting up an appropriate base case and analysing its daylight and energy performance, forming the basis of comparison for subsequent cases for design variants. The second method involved setting up the base case within a site context and conducting a solar irradiation study. An architectural variables such as overhang and shading device, were then defined as inputs in the parametric definition in Grasshopper to control the selected variable. Results: While the first method took advantage of the speed and efficiency of the integrated workflow, the second method was derived based on the ability to directly process simulation data within the integrated, single-software platform of the proposed workflow. Through these methods, different architectural strategies were explored, both to increase daylight penetration and to reduce radiant heat gain. The focus is on methods by which this workflow can be applied to facilitate the experimental derivation of daylight optimization strategies that are specific to tall building design.

• 대한조선학회논문집
• /
• 제44권3호
• /
• pp.332-339
• /
• 2007

Integration of engineering information through the IT (Information Technology) is very important key during the collaboration design process. How can we realize the data efficiently in real-time at the early design stage? How can we manage to integrate the separate information made by each designer or department effectively in real time? IT global trend is the unique way of handling these complicated problems from the information inundation. This paper suggests the design process management system deduced from the analytical results considering BPM (Business Process Management) solution workflow. Workflow based design process management system can help user share and integrate the needed information at the right time through Internet. It is found that the proposed tool works well for a beam design case, and this framework can be thus further expanded for an engineering design environment smoothly.