earticle

영어

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.