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

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.32-43
• /
• 2006

Enterprise JavaBeans (EJB) has been accepted for supporting Component-Based Development (CBD). A component is a large-grained reuse unit consisting of several objects; however, an enterprise bean in EJB is a unit of atomic object and so multiple enterprise beans should be composed to support larger-grained reuse. Therefore, we need practical methods for designing and implementing components with EJB. In this paper, we propose instructions and techniques for designing CBD elements with EJB constructs. That is, we define methods for designing and implementing single and composite components, white- and black-box components, multiple interfaces, and variability mechanism in EJB platform. We evaluate the proposed method by performing a case study and comparing the characteristics of CBD components with the method. Consequently, the method is supposed to improve reusability, applicability, portability of components in EJB platform.

• Journal of Information Technology Applications and Management
• /
• v.11 no.2
• /
• pp.167-178
• /
• 2004

Different from traditional development methodologies like waterfall model, the CBD (component based development) methodology relies on a building block approach in the design and development of information system. The audit procedure and checklist for the traditional IS development methodology are required to be modified to be suitable for CBD. This research reviewed IS audit guidelines for the existing development process and analyzed multiple projects that employed the by component based development process. For the purpose of this study, we chose a governmental project and a next-generation IS project of a financial agency as sample cases. By comparing existing IS audit checklists and items actually reviewed in audit projects, this study identified appropriate check items for the CBD-centric audit program. New items were proposed as additional items such as project control in management phase, usage case and conceptual model establishment, component evaluation and design, in implementation phase, and so forth. The result of the research provides new guidelines for the audit CBD projects for the purposed of increased efficiency and qualify of application development projects.

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

• Proceedings of the Korea Multimedia Society Conference
• /
• 2002.11b
• /
• pp.711-715
• /
• 2002

소프트웨어 위기 극복으로부터 시작한 소프트웨어 공학이 최근 가장 경쟁력 있는 소프트웨어 개발 기술로 지목하고 있는 컴포넌트 기반 개발(CBD; Component Based Development) 기술은 높은 생산성과 고품질의 소프트웨어의 개발을 가능하게 되었다. 소프트웨어 Component를 조립해 새로운 Application을 만들 수가 있어 개발기간을 단축할 수 있으며 기존의 Component를 재사용할 수 있어 생산성과 경제성을 높일 수 있다. 본 논문에서는 특정물품의 주문 관리시스템을 대상으로 하여 컴포넌트기법을 활용 분석, 설계, 구현을 하였다. 분석과 설계는 UML을 활용하였으며, 구현은 EJB를 이용하여 Component를 생성하였다.

• Journal of KIISE:Software and Applications
• /
• v.30 no.9
• /
• pp.812-820
• /
• 2003

Component-Based Development(CBD) leverages software reusability and diminishes development costs. Various works about component models, such as EJB, COM, and CCM are in progress to support CBD. However, current component models hardly support flexible assembly of pre-built components. To cope with this problem, architecture for component assembly must be defined in the abstract level and the gap between system architecture and its implementation should be diminished in the implementation level. This paper proposes a method for architecture-based design and implementation of component assembly. Architecture is described by the ADL, and the tool, COBALT Assembler, is introduced to support the proposed design and implementation phase of component assembly.

• Journal of KIISE:Software and Applications
• /
• v.32 no.3
• /
• pp.153-162
• /
• 2005

Component Based Development (CBD) is appealing as a technology to improve the productivity of software development through component reuse. Model Driven Architecture (MDA) is a new development paradigm which automatically generates application by transforming design models incrementally. Since both reusability of CBD and model transformation of MDA increase software productivity. integration of two technologies is desirable. To enable this technology integration, we need to devise a UML profile for specifying component design as a PIM. In this paper, we first define a meta-model for components, and propose a UML profile which is used to specify elements of component design as PIM. Since the proposed profile is based on Meta Object Facility (MOF) from which is MDA is derived, it is consistent and compatible with existing MDA methods and tools.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1205-1216
• /
• 2005

Component-based Development (CBD) is gaining popularity as an effective reuse technology. Especially commercial-off-the-shelf (COTS) components are mainly for inter-organizational reuse, rather than intra-organizational reuse. One of the essential tasks in CBD is to reuse the right components that provide the functionality and interface required by component consumers. If candidate components provide a limited applicability and customizability, a component consumer cannot reuse the components in application development. To resolve this partial matching problem, we need smart connectors that fill the gap between candidate components and the specification of components required. Previous researches about smart connector describe only connector types to resolve mismatch problems. However, previous researches do not address the identification and design method to resolve the problems. In this paper, we suggest taxonomy of various mismatch problems to identify partial match problems between requirements of the application and components. We identify smart connector types and suggest a systematic process for designing smart connectors using the taxonomy. Therefore, components that have the problems can be used to develop applications.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.10a
• /
• pp.376-378
• /
• 2001

CBD(Component Based development)가 이미 완성된 소프트웨어 모듈인 컴포넌트들을 특정 목적을 위해 배치하고 조립함으로써 품질 보증된 고생산성의 재사용을 가능하게 됨에 따라, 최근 IT 비즈니스 솔루션 도출을 위한 핵심 적인 기술 전략으로 인식되고 있다. 따라서 영 역에 적절한 컴포넌트의 추출과 개발 및 응용 시스템으로의 전개를 위한 컴포넌트들의 배치와 조립 등을 포함하는 일련의 CBD 프로세스를 실제화 하기 위해서는 아키텍쳐 기반의 접근과 제어가 매우 중요하다. 하지만 대부분의 CBD 연구는 비즈니스 로직들의 기능성을 그룹화한 컴포넌트의 생산에 초점을 두고 있지 컴포넌트간의 상호작용을 명시하는 아키텍쳐 정보의 관리를 간과함으로써 컴포넌트의 조립과 통합을 통한 CBD 시스템으로의 전개는 극히 어려운 실정이다. 따라서, 본 논문에서는 CHD 프로세스 상에서 아키텍쳐 접근의 중요성과 전개 방법을 살펴보고, 컴포넌트 프레임워크(Component Framework)를 위한 아키텍쳐의 계층을 새롭게 재정의 하며 그 의미를 설명한다. 이를 위해 영역 분석 및 설계 정보를 선언적으로 명시하는 수단이며, 도메인 내에서 특정 서비스를 제공하는 컴포넌트간의 일반적 결합 방식의 규정하기 위한 수단으로서 설계 패턴을 이용하여 서비스 아키텍쳐 패턴을 정의하고 실 예로 적용한다.

• Journal of KIISE:Software and Applications
• /
• v.33 no.6
• /
• pp.539-549
• /
• 2006

Component-Based Development (CBD) has emerged as a new effective technology that reduces development cost and time-to-market by assembling reusable components in developing software. The degree of conformance to standards and common features in a domain largely determines the reusability of components. In addition, variability within commonality should also be modeled and customization mechanism for the variability should be designed into components. Enterprise JavaBeans (EJB) is considered a most suitable environment for implementing components. However. the reusability of EJB is limited because EJB does not have built-in variability design mechanisms. In this paper, we present efficient variability design techniques for implementing components in EJB. We propose a method to customize the variability of EJB-based components by applying three variability design mechanisms; selection, plug-in, and external profile. And we elaborate the suitable situations where each variability design mechanism can be applied, and conduct a technical comparison to other approaches available.