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

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

• Journal of KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1027-1042
• /
• 2004

A Software Component is a module that is reused among a lot of projects, systems, and companies rather than a single application. Components can be reused in various systems if they provide not only the common functionalities required in many applications but also the diverse aspects to be customized for being suitable for customers' demands. From the development phase, components should be designed and developed considering the variable aspects they have for convenient customization. Easily customized components can be frequently reused in lots of applications. In the literature, there are some modeling and customizing techniques. But they suggested only conceptual or basic methods based on Object-Oriented. And the practical instructions for reusing component were not provided sufficiently. Moreover, there are few techniques that consider the proper variability types components have. Thus, those techniques are not appropriate for applying to black box component completely developed and released. In this paper, we classify variabilities that components have in functional aspect into two categories. The one is logic variability, and the other is workflow variability. For each classified variability, we propose the three kind of modeling techniques, which are selection, plug in and externalization. Also detailed instructions for practical design and application are provided.

• Journal of Internet Computing and Services
• /
• v.6 no.2
• /
• pp.13-24
• /
• 2005

Software development by component integration is the mainstream for time-to-market and is the solution for overcoming the short lifecycle of software. Therefore, the effective techniques for component integration have been working. However, the systematic and practical technique has not been proposed. One of main issues for component integration is how to specify integration and the component architecture for operating the specification, in this paper, we propose a workflow variability design technique for component integration, This technique focuses on designing to a connection contract based on the component architecture. The connection contract is designed to use the provided interface of component and the architecture can assemble and customize components by the connection contract dynamically.

• The Journal of Society for e-Business Studies
• /
• v.24 no.3
• /
• pp.53-71
• /
• 2019

As software systems become more complex and larger, software systems require a way to reuse software components or modules to provide new functionality. This paper designed a development method of web system combining SOA(Service Oriented Architecture) with MPSL(Multi-Software Product Line). According to provides SOA and MPSL, this paper suggested to service providers and service users to provide and reuse variable services. From the viewpoint of service provider, the suggested method identifies and implements reusable variable services as features by syntax-based, functional-based, and behavior-based methods applying feature identification guidelines and manages them as reuse assets. From the user's point of view, it is possible to develop a web system by constructing a service by workflow model as a method of structure and reconfigure services. As a result of measuring the reuse of the web system constructed in this paper by the function point, the cost reduction effect was verified by applying it to the similar project with the increase of reuse.

• Journal of KIISE:Software and Applications
• /
• v.31 no.5
• /
• pp.677-696
• /
• 2004

Component-based software engineering (CBSE) composes reusable components and develops applications with the components. CBSE is admitted to be a new paradigm that reduces the costs and times to develop software systems. The high quality of component designs can be assured if the consistency and correctness among the elements of a component are verified with formal specifications. Current formal languages for components include only some parts of contracts between interfaces, structural aspects and behavioral aspects of component, component-based system, component composition and variability. Therefore, it is not adequate to use current formal languages in all steps of a component design process. In this paper, we suggest a formal language to specify component designs Component-Z. Component-Z extends Object-Z, adds new notations to specify components. It can be possible to specify interfaces, the inner structure of a component, inner workflows, and workflows among interfaces with Component-Z. In addition, Component-Z provides the notations and semantics to specify variability with variation points, variants and required interfaces. The relation between interfaces and components is defined with mapping schemas. Parallel operator is used to specify component composition. It can be possible to describe deployed components with the specifications of component-based systems. Therefore, the formal specification language proposed in this paper can represent all elements to design components. In the case study, we specify an account management system in a bank so that we show that Component-Z can be used in all steps of component design.

• The KIPS Transactions:PartA
• /
• v.14A no.7
• /
• pp.399-408
• /
• 2007

Currently various techniques for efficiently developing sensor network applications are developed. However, these techniques provide the method for developing only single sensor network application easily and rapidly. Since sensor network applications control various sensor nodes based on core components of operating system, the technique to develop applications by defining common functionalities of various applications and selecting variable functionalities according to the work flow of specific application is efficient. Accordingly, this paper presents an experimental study that identifies commonality of sensor network application domain and supports optional development according to the variability of application by applying product line approach to developing sensor network application. Through the experimental study, we describe the characteristics of sensor network application domain compared with general business domain for product line development. Also, we show the effectiveness of the proposed approach by presenting that core assets designed using the proposed variability feature model and VEADL are reused according to the functionalities of each sensor node.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.6
• /
• pp.285-292
• /
• 2017

There are technological, operational and environmental constraints at tactical edge, which are disconnected operation, intermittent connectivity, and limited bandwidth (DIL), size, weight and power (SWaP) limitations, ad-hoc and mobile network, and so on. To overcome these limitations and constraints, we use service-oriented architecture (SOA) based technologies. In our research, we propose a hierarchical mission service model that supports service-oriented mission planning and execution in order for a commander to operate various SW required for mission in battlefield environment. We will also implement development tools that utilize the workflow technology and semantic capability-based recommendation and apply them to combat mission scenarios to demonstrate effectiveness.

• The Journal of the Korea Contents Association
• /
• v.5 no.4
• /
• pp.11-19
• /
• 2005

With the development of IT technologies, IT environment is making great change over life whole and is displacing business and business achievement systems of industry at the fast speed. The system which is proposed in this paper, supports environments to share codes, execution files and objects between project teams to maximize productivity and efficiency in web environments. Through impact assessment which is achieved at correction and development of existing programming codes by maintenance requirements, it minimizes obstacle occurrence factors and supports tracing obstacle sources. Through conversion the correction and development histories of existing sources and executable files between project teams to XML documents suitable to share in web, it stores them to relational database. In this paper, through impact assessment and change management for the correction and development of applications in the existing system development environments, we support efficient IT developments.