• The Journal of the Korea Contents Association
• /
• v.5 no.5
• /
• pp.51-58
• /
• 2005

Software development process evolves by component based development(CBD) process and introduction to configuration management system is risen recently. In this paper, we explained component configuration management system evolved out of CBD methodology and focused on the specification management in component configuration management. The component specification is being based on XML that is a normalization document. Also, component version management and dependency management are achieved by a component name. And component dependency information is just the integration information using a component specification name used in the composition when component specification is composed. Thus we confirmed possibility of version management and dependency management using the specification.

• Journal of Korea Multimedia Society
• /
• v.9 no.6
• /
• pp.750-761
• /
• 2006

As CBD technologies and researches have been matured, component framework as a larger reuse unit than component is being introduced. Especially issues related with adaptation and integration of components in CBD are being raised as a new research topic. The component framework is given as a solution to resolve these issues. However, current approaches don't suggest a sound and comprehensive reference model and development process applying reference model. In order to develop practical and stable component framework, reference model and concrete guidelines are essential elements. In this paper, we propose a generic reference model integrating existing reference models and a design technique of component framework based on it. Especially, we propose concrete and pragmatic guidelines such as how to design component framework architecture's view and style, how to design commonality and variability of component framework, how to design macro workflows among components, and so on. We believe that the proposed reference model becomes basis for component framework development, and the proposed design technique will support reliable and effective development of the component framework.

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

• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.613-618
• /
• 2002

The component-based development methodology becomes famous as the new technology for reuse. That technology can help us easily develop a complex and large system by composing reusable components in short period with high-quality and low-cost. The component-based system nay be developed by composing more than one component. So, the quality of component-based system is determined by individual component duality. Therefore, it is necessary to measure individual component quality for the improvement in quality of component-based system. Hence, in this paper, we propose new component metrics for measuring the cohesion as relationship between classes and interfaces or among classes. Those can be applied in the early stage of software development life cycle. So, we can measure the functional cohesion of component which will be developed. Predicting functional independence of a component, we expect to reduce the software developing cost & effort and improve software quality by reusing a component.

• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.619-628
• /
• 2002

Reusable software component is an ultimate goal for the software development. Component based development is focused on advanced concepts rather than passive manipulation or class library with source codes. However, the primary component construction in component based development lead to an additional development cost and effort for reconstructing the new software component within a component model. Java application provides several features based on component model. But, we only have an opportunity to develop the smallest reuse units or the restricted set of GUI components. It cannot contributed as a component and only used in the specific domain component with high cost and efforts. In this paper, we apply java component model to the existing java application and extract javabeans through extending the component scalability. We also discuss the algorithm for transformation mechanism from legacy class to javabeans with a partial of business logic.

• Journal of KIISE:Software and Applications
• /
• v.29 no.7
• /
• pp.476-486
• /
• 2002

CBD(Component Based Development) has become the best strategical method for the business application. Because CBD is a new development paradigm which makes it possible to assemble the software components for application, it copes with the rapid challenge of business process and meets the increasing requirements for productivity. Since the business process is rapidly changing, CBD technology is the promising way to solve the productivity. Especially, the repository is the most important part for the development, distribution and reuse of components. In component repository, we can store and manage the related work-products produced at each step of component development as well as component itself. In this paper, we suggested a practical approach for repository construction to support and realize the CBD process and developed the CRMS(Component Repository Management System) as implementation product of the proposed techniques. CRMS can manage a variety of component products based on component architecture, and help software developers to search a candidate component for their project and to understand a variety of information for the component. In the paper, a practical approach for component repository was suggested, and a supporting environment was constructed to make CBD to be working efficiently. We expect this work wall be valuable research for component repository and the entire supporting Component Based Development Process.

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

• Journal of KIISE:Software and Applications
• /
• v.30 no.12
• /
• pp.1172-1184
• /
• 2003

At present, new techniques based on different component reference models for the integration of component and system of different platforms, such as EJB and COM+, are introduced. The operation between the components in the identical component platform is realized by the composition at the source level. In case of the different component platform, however, it is impossible to use combined components in real condition although they are components of similar domain. In this paper we proposed a solution for the composition problem by using component transformation methodology based on model between EJB and COM+ components which are different components. For the composition between EJB and COM+ components, we compared and analyzed each reference model, then proposed the Virtual Component Model which is implementation independent and the Implementation Table for the mutual conversion. Reffering to the Virtual Component Model and the Implementation Table, we can generalize each Implementation model to the Virtual Component Model, make the Virtual Component Model which is implementation independent through the virtual component modeling, transform EJB and COM+ components selectively. Proposing the effective Model Transformation method to the different component platform, we can combine EJB and COM+ components.

• IE interfaces
• /
• v.16 no.spc
• /
• pp.127-131
• /
• 2003

Component-based development approach is used in modern software system development projects that are very complex and large-scale. Technical components are more effective rather than business components in software development. However, on the Microsoft .net environment, the technical component-based development issues are not adopted. Moreover, software architecture on the .net environment is not studied yet because the development platform is recently used in the development of enterprise-level system. This paper proposes a technical component-based software architecture on .net environment. Seven technical components - configuration, data access, exception, file I/O, log, message, and paging - are contained in the architecture. The proposed architecture enables developers to reduce development time and to concentrate business logic rather than architectural issues. To verify the proposed architecture and the components, a partner management system is developed based on the architecture.

• Proceedings of the IEEK Conference
• /
• 2004.08c
• /
• pp.712-716
• /
• 2004

Because of rapid development of software technology, a number of software professionals have been concerned with component-based development methodologies. Up to date, the evaluation of component quality has been focused on object-oriented metric based methodology. But this paper presents the selection process and evaluation criteria based on an MCDM(Multiple Criteria Decision Making) technique for the selection of optimal COTS component from consumers' viewpoints. We considered functionality, efficiency and usability based on ISO/IEC 9126 for quality measurement and conducted practical analysis into commercial EJB component in internet. This paper shows that the proposed selection technique is applicable for the selection of the optimal COTS component.