• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.705-714
• /
• 2001

The computing systems of today expanded business trade and distributed business process Internet. More and more systems are developed from components with exactly reusability, independency, and portability. Component based development is focused on advanced concepts rater than passive manipulation or source code in class library. The primary component construction in CBD. However, lead to an additional cost for reconstructing the new component with CBD model. It also difficult to serve component information with rapidly and exactly, which normalization model are not established, frequency user logging in Web caused overload. A lot of difficult issues and aspects of Component Based Development have to be investigated to develop good component-based products. There is no established normalization model which will guarantee a proper treatment of components. This paper elaborates on some of those aspects of web application to adapt user requirement with exactly and rapidly. Distributed components in this paper are used in the most tiny size on network and suggest the network-addressable interface based on business domain. We also discuss the internal and external specifications for grasping component internal and external relations of user requirements to be analyzed. The specifications are stored on Servlets after dividing the information between session and entity as an EJB (Enterprise JavaBeans) that are reusable unit size in business domain. The reusable units are used in business component through query to get business component. As a major contribution, we propose a systems model for registration, auto-arrange, search, test, and download component, which covers component reusability and component customization.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.7 no.5
• /
• pp.1089-1094
• /
• 2003

Recently, Software development method supported CBD is applied with many concern and is researched with part of application and composition based-on architecture effectively use it. Effectively, C2 architecture has been concern with the point of component composition method based-on message driven for supported GUI. But, In case of classified sequence in component and method call method in server component, component must be modified to apply it. Thus, In this paper, Message handling part with a part of C2 architecture change is locate in the message neither component not connector. So, Although method call method it can be composit and operate component for support Plug-and-Play without modification. Also, it's possible the more flexible message handling with parallel composition of component between message without classified sequence.

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.671-682
• /
• 2004

As new and diverse information technologies are being introduced and software complexity is increased, software development cost and efforts are also sharply increased. Component-Based Development (CBD) technology is appealing as a new way to reduce the cost and effort by increasing reusability and maintainability. Component in CBD has variability infernally which enables customization of the component within the specific domain. A component user can easily set up internally variability parts though Required interface which is provided by the component. Enterprise JavaBeans (EJB) is utilized as a commercial standard to implement Java-based components. However, EJB constructs are limited in directly implementing Required interfaces of coarse-grained components［8］. In this paper, we define Required interface and propose interface-storage technique, class-storage technique, interface-generation technique, and Plug -in technique for implementing required interface of component. Interface-storage technique stores variable value in Required interface and class-storage technique take the Bean containg variability as Required interface without modification of component model. Interface-generation technique generates new Bean which takes the role of Required interface for component variability and Plug-in technique sets up component variability that component user plugged-in variable part externally The proposed four techniques conform to the semantics of CBD component interface and enable the implementation of high quality components.

• ETRI Journal
• /
• v.25 no.2
• /
• pp.121-132
• /
• 2003

To enhance the productivity of software development and accelerate time to market, software developers have recently paid more attention to a component-based development (CBD) approach due to the benefits of component reuse. Among CBD processes, the identification of reusable components is a key but difficult process. Currently, component identification depends mainly on the intuition and experience of domain experts. In addition, there are few systematic methods or tools for component identification that enable domain experts to identify reusable components. This paper presents a systematic method and its tool called a component identifier that identifies software components by using object-oriented domain information, namely, use case models, domain object models, and sequence diagrams. To illustrate our method, we use the component identifier to identify candidates of reusable components from the object-oriented domain models of a banking system. The component identifier enables domain experts to easily identify reusable components by assisting and automating identification processes in an earlier development phase.

• The KIPS Transactions:PartD
• /
• v.18D no.6
• /
• pp.461-480
• /
• 2011

Component-Based Development (CBD) focuses on developing reusable components and assembling them into target applications. Service-Oriented Computing (SOC) is a relatively new paradigm where reusable services are developed, published, and composed into target service applications. Due to the popularity of CBD, many organizations already have CBD models for their applications. Hence, it is feasible and appealing to develop SOC applications economically by transforming existing CBD models, rather than developing SOC applications from the scratch. Our research is to develop a methodology for transforming existing CBD design into Service-Oriented Architecture (SOA) design. In this paper, we first compare the two paradigms and their key elements for the design; CBD design and SOA design. Then, we define mapping relationships of the transformation. For each transformation mapping, we present step-wise instructions. The benefit of applying this transformation is to increase reusability of existing design assets, to maintain the consistency between existing CBD and SOC models, and reduced cost for deploying service-oriented applications.

• Journal of the Korea Society of Computer and Information
• /
• v.7 no.4
• /
• pp.59-65
• /
• 2002

In these days, educational environment has been changing as Slowing of internet. This is why we have to consider a Web-based cyber education. The LMS is functionally constituted with Class-part and Management-part. Class-part take part in planning of lecture, loading the presentation material and class service. In this system, UML is used to support a specification of Component-based LMS. Through this study, we will show the effectiveness of CBD(Component Based Development) in during LMS development.

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

Recently, software quality evaluation based on ISO/IEC 9126 and ISO/IEC 14598 has been widely accepted in various areas. However, these standards for software quality do not provide practical guidelines to apply the quality model and the evaluation process of software product=5. And the qualify management in most software projects has been conducted by managing defects without applying the standards for software qualify. Thus, we present a quantitative quality evaluation approach of artifacts in the Component Based Development (CBD). Particularly, our evaluation approach allows most of the standard evaluation process and adopts a quantitative quality model which uses the weights of quality characteristics obtained through carefully selected questionnaires for stakeholder and Analytic Hierarchical Process(AHP). Moreover, we have also examined the proposed evaluation approach with applying the checklists for the artifacts of the CBD to a small-scale software project. As a result, we believe that the proposed approach will be helpful for acquiring the high quality software.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.645-656
• /
• 2001

Recently, component-based development (CBD) is rapidly spreading as a way of improving the reusability, productivity, and quality of software. For CBD to be effective in achieving such design objectives, the creation and integration of components must be based on a well-defined architecture that guides the correct composition and cooperation of application components. Software architecture must be described using an architecture description language (ADL) to ensure the correctness and preciseness of architecture models. In this paper, we propose the system architecture of an ADL tool set that can effectively support the use of CBD based on the domain architecture and we describe each component of the proposed system architecture. We also modify and redefine C2SADL that was developed to support the use of the description of C2 architectural style by UCI (University of California in Irvine) to facilitate the integration of separately described architecture models, and introduce the method of design and implementation of our ADL processor that partially implements the proposed ADL system architecture.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.04a
• /
• pp.555-557
• /
• 2000

CBD(Component Based Development)는 미리 만들어진 검증된 부품을 합성, 조립하는 작업으로, 최근에 빠른 속도로 생겨난 카타르시스는 객체와 프레임워크로 CBD를 위한 완벽한 지원을 제공하는 차세대 방법론이다. 네트워크 환경과 인터넷의 보급으로 인한 인프라 구축과 다양한 방법론의 개발은 소프트웨어 부품화로써의 컴퍼넌트 기반 소프트웨어 개발에 대한 관심을 높이고 제반 여건을 조성하는 계기가 되었다. 또한 네트워크 기반의 분산 환경이 응용의 개발과 활용을 위한 표준 아키텍쳐로 자리잡아 가면서 네트워크 관리가 개별 응용으로서 뿐 아니라 대부분의 응용에서 하부 계층 지원 서비스로 요구되는 중요한 응용 도메인이 된다. 따라서 다수의 개발자들이 환경적 제약없이 네트워크 관리를 위한 응용 컴퍼넌트를 획득, 조립함으로써 요구되는 서비스를 구현할 수 있다. 그러므로 본 논문에서는 컴포넌트 소프트웨어 설계를 위한 방법론인 카타르시스를 사용하여 네트워크 관리 시스템(NMS)을 위한 컴포넌트를 설계하고 필요한 컴포넌트를 식별, 개발한다. 이를 통해 NMS를 위한 공용의 컴퍼넌트를 확보함으로써 체계적인 CBD 방법론에 의한 NMS 개발로의 표준화된 접근할 수 있다.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.390-398
• /
• 2003

폭포수 모델 개발 생명주기를 근간으로 한 전통적 프로그램 개발방법론과 달리, 부품 형태의 컴포넌트를 조립하여 개발하는 방법론이 확산되고 있다. 컴포넌트 기반 개발(Component Based Development)의 감리에는 전통적 개발방법에 근간을 둔 감리기준이 아닌 컴포넌트 기반 개발방법에 적합한 감리가 실시되어야 한다. 본 연구에서는 전통적 개발방법론 근간의 감리기준과 CBD 적용 프로젝트 사례 분석을 통하여 감리기준의 개선점 여부를 탐색하고자 하였다. 연구 사례로는 정부 공공프로젝트와 금융기관의 차세대정보시스템 구축 프로젝트를 선정하였다. 기존의 정보시스템감리 기본점검표와 사례에서의 감리검토항목을 비교 분석한 결과 감리검토항목의 개선점을 발견할 수 있었다. 사례분석의 결과로 CBD 프로젝트에 적합한 감리검토항목을 제시하였으며, 연구결과는 소프트웨어 제품 개발의 효율성 제고 및 품질향상에 이바지 할 것이다.