• The Journal of Society for e-Business Studies
• /
• v.9 no.2
• /
• pp.145-161
• /
• 2004

CBD(Component Based Development) can make use of component of block unit that is implementation beforehand and shorten software development cost and time. Also, component can reduce complexity for the large application development because it can hide detail part of internal and offer interface. Common requirement of family in the enterprise framework environment can express workflow, but it is very difficult that express special workflow in single component on various family member's requirement. Therefore, necessity about workflow variability management between component for family member and implementation method had been required constantly This treatise presents implementation techniques for component workflow variability in enterprise framework under .NET base. Presented component workflow variability implementation techniques supposes that commonness business workflow that family can use in enterprise workflow was created already in component, and improve workflow's extensity between component by workflow composition between special component and techniques for practice to various family member.

• The KIPS Transactions:PartD
• /
• v.12D no.7 s.103
• /
• pp.1023-1030
• /
• 2005

CBD(Component Based Development) can make use of component of block unit that is implementation beforehand and shorten software development cost and time. Also, component can reduce complexity for the large application development because it can hide detail part of internal and offer interface. Common requirement of family in the enterprise framework environment can express workflow, but it is very difficult that express special workflow in single component on various family member's requirement. Therefore, necessity about workflow variability management between component for family member and implementation method had been required constantly. This treatise presents implementation techniques for component workflow variability in enterprise framework under Banking Loan Presented component workflow variability implementation techniques supposes that commonness business workflow that family can use in enterprise workflow was created already in component, and improve workflow's extensity between component by worikflow composition between special component and techniques for practice to various family member.

• 한국디지털정책학회:학술대회논문집
• /
• 2004.11a
• /
• pp.299-310
• /
• 2004

Business process in e-government mostly embody as the flow of documents. Constructing a web-based document flow system becomes an critical task for today s digital government. But few of them use an off-the-shelf workflow product. Why? One of the reasons is that most of the workflow system are heavyweight, monolithic, and package a comprehensive set of features in an all-or-nothing manner. Another reason is that workflow technology lacks the constructs and modeling capability as programming language. It is incumbent on government IT organizations to transform their solution development to component-based computing model. Component technology isolates the computation and communication parts, but how to compose different software components is still a hard nut. An integrated development environment is necessary for CBSD. In this paper we propose a XML and component-based document flow-oriented integrated development environment (DFoIDE) for software developers. By writing some xml configure file, and operate on DFoIDE, developer can construct a workflow application quickly. This method divides system to several components and the activities in process are implemented as business component. Different components are discribed detailedly in this paper, especially one of the core component. Component Integrating Tool. Different perspectives in workflow application are seperated and depicted as different XML files. Correspondly, A component composition method for developing workflow application instead of workflow itself is proposed.

• 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 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:Software and Applications
• /
• v.29 no.10
• /
• pp.703-725
• /
• 2002

It is well recognized that component-based development (CBD) is an effective approach to manage the complexity of modem software development. To achieve the benefits of low-cost development and higher productivity, effective techniques to maximize component reusability should be developed. Component is a set of related concepts and objects, and provides a particular coarse-grained business service. Often, these components include various message flows among the objects in the component, called 'business workflow`. Blackbox components that include but hide business workflow provide higher reusability and productivity. A key difficulty of using blackbox components with business workflow is to let the workflow be customized by each enterprise. In this paper, we provide techniques to model the variability of family members and to customize the business workflow of components. Our approach is to provide formal specification on the component variability, and to define techniques to customize them by means of the formalism.

• Journal of the Korea Society for Simulation
• /
• v.5 no.2
• /
• pp.13-24
• /
• 1996

Workflow is an ordered sequence of interdependent component data activities each of which can be executed on an integrated information system by accessing a remote information system. In our previous research [4], we proposed a distributed CIM Workflow system which consists of a workflow execution model called DAF-Net and an agent-based information systems called AIMIS. Given a component data activity, there needs an interaction protocol among agents which allocates the component data activity to a relevant information systems exist. The objective of this research is to propose and test two protocols: ARR(Asynchronous Request and Response)protocol and NCL(Negotiation with Case based Learning) protocol. To test the effectiveness of the protocols, we applied the PVM(Parallel Virtual Machine) software to simulate the distributed CIM Workflow system. PVM provides a distributed computing environment in which users can run different software processes in different computers while allowing communication among the processes.

• The Journal of the Korea Contents Association
• /
• v.6 no.1
• /
• pp.54-63
• /
• 2006

In this paper we will propose a domain analysis methodology that uses an extended workflow mechanism based on dynamic modeling to solve problems of a traditional domain analysis on legacy systems. This methodology is called WODA(Workflow Oriented Domain Analysis). Following procedures on WODA, we can identify common/uncommon component, and also extract the cluster of components. It will be effectively reusable on developing new systems with these components. With our proposed component testing metrics, we can determine highly reusable component/scenario on identifying possible scenarios of the particular system. We can also recognize most critical/most frequent reusable components and prioritize possible component scenarios of the system. This paper contains one application of UPS that illustrates our autonomous modeling tool, WODA.

• Journal of KIISE:Software and Applications
• /
• v.27 no.5
• /
• pp.499-509
• /
• 2000

When the developers develop the software, the cost and time of the software development can be reduced by using blocks that are implemented previously. We call these implemented blocks components. They provide only the interfaces of component to developers, while the detailed infernal information is being hidden. The components can be used to develop large applications fast and easily. Developers use the black-boxed components that the internal details of components are invisible. But, Developers want the properties and workflows of components to be modified. To do this, the customization technique is needed. The existing customization techniques are limited in the customization of component properties. In this paper, it proposes the technique that can change the workflow of component as well as properties In the business point of view. In the existing workflow customization technique, which is called white box component, the internal details of component should be understood by developers and should be modified in code level. In this paper, we propose a customization technique which using the component interface in black box form only. This customization technique can be used more generally in a business field.

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