• Journal of KIISE:Software and Applications
• /
• v.31 no.10
• /
• pp.1286-1303
• /
• 2004

Component-based Development is gaining a wide acceptance as an economical software development paradigm to develop applications by utilizing reusable software components. Well-defined interface manages coupling and cohesion between components, minimizes the effect on the user in case of component evolvement, and enhances reusability, extendibility and maintainability. Therefore, study on systematic development process and design guidelines for component interface has been required since the component has been introduced. In this paper, we propose three types of interfaces based on software architecture layers and functionality types； Provided Interface which provides functionality of a component, Required Interface which specifies required functionality that is provided by other components, and Customize Interface which tailors the component to customer's requirement. In addition, we suggest design criteria for well-designed interface, and systematic process and instructions for designing interface. We firstly cluster operations extracted from use case model and class model to identify Provided interfaces, and design Customize interfaces based on artifacts for variability. We also specify Required interfaces by identifying dependency among interfaces. Proposed interface design method provides traceability, throughout the component interface design. And furthermore, proposed guidelines support practical design for high quality component based on a case study.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.06c
• /
• pp.196-198
• /
• 2006

소프트웨어 프러덕트 라인 개발 방법론이란 개발 초기에 시스템의 공통적인 부분과 가변적인 부분을 명확히하여 소프트웨어 자산을 구축한 후 다양한 요구 사항에 따라 가변적인 부분을 커스터마이징하여 목표 시스템을 생성하는 소프트웨어 개발 패러다임이다. 일반적인 소프트웨어 프러덕트 라인에 대한 연구는 활발히 진행되고 있지만, 병렬성을 지원하는 소프트웨어 프러덕트 라인에 대한 연구는 상대적으로 미약하다. 본 논문에서는 병렬 소프트웨어 프러덕트 라인 구축에 있어서 특성 모델을 통해 기능적 가변성을 지원하고 상태 다이어그램을 통해 동시성을 지원하는 컴포넌트의 코드를 자동 생성하는 도구를 제안한다. 본 연구 결과는 병렬성이 중요한 실시간 임베디드 소프트웨어 프러덕트 라인 구축에 활용될 수 있다.

• Journal of KIISE:Software and Applications
• /
• v.29 no.9
• /
• pp.605-618
• /
• 2002

The CBD (Component Based Development) is a requisite technique for the Time-To-Market, and a highly reusable component should be provided to develop a variety of domain applications with the use of components. To increase the reusability of components, they should be developed by analyzing requirements of many different kinds of domains. However, to analyze requirements of a variety of domains related to the components to be developed and to include them inside the components will give burden to developers. Also, providing only general components that have common facilities for the several domains is not easy to accomplish the time-to-market since there are other domains that the developers have to develop. As such, developing common component through the analysis of several domains at the time of the CD (Component Development) does not always guarantee high reusability of the component, but gives burden to developers to develop another development since such components have common functions. Considering this, this paper proposes the component customization technique to reuse common components as well as special components. The reusability of the component can be increased by providing changeability of the attribute, behavior and message flow of the component. This customization technique can change the message flow to integrate developed components or to provide new functions within the component. Also, provides a technique to replace the class existing within the component with other class or to exchange the integrated component with the component having a different function so that requirements from a variety of domains may be satisfied. As such, this technique can accept the requirements of several domains. As such, this customization technique is not only the component with a common function, but it also secures reusability components in the special domain.

• Journal of KIISE:Software and Applications
• /
• v.33 no.3
• /
• pp.289-300
• /
• 2006

Product line is nowadays well known as a representative method for reuse. In the product line, important assets are components. Although enough concerns were given of the product line, it was not accomplished to structure and specify a product-line component with variability. This paper presents an approach to specify components in the product line. The approach describes the static and dynamic structure of a product-line component and explains the behavior and concurrency of the component. The component information is separately described in the black-box and white-box using the Feature-Oriented Reuse Method(FORM). This research also formalizes the data on a component specification in the form of BNF. The specification is described through careful consideration for many different characteristics of the product-line component, so this paper helps to easily develop the components in the product line and to well comprehend how to apply a method for the product line.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.319-321
• /
• 2004

제품 계열 공학(Product Line Engineering, PLE)는 패밀리 멤버들의 공통성과 가변성을 분석하여 만든 핵심 자산을 특화시켜 어플리케이션을 개발함으로써 재사용성과 이용가능성을 증대시키는 접근 방법이다. 핵심 자산은 제품 계열에 속하는 패밀리 멤버들이 어플리케이션을 만드는데 기초가 되는 모든 자산을 포함하며, 아키텍처, 컴포넌트 둥이 포함될 수 있다. 범용 아키텍처는 패밀리 멤버들이 공통적으로 사용할 수 있는 아키텍처로, 제품 계열에 속하는 제품들의 구조를 정의하고 컴포넌트의 인터페이스 명세를 제공하여 컴포넌트만큼 중요한 재사용 단위이다. 본 논문에서는 대표적인 PLE 방법론에서 정의한 제품 계열 아키텍처와 일반 소프트웨어 아키텍처를 비교하여 범용 아키텍처에 포함되는 요소들을 선정하고, 메타 모델을 이용하여 범용 아키텍처 구성요소와 구성요소간 관계를 명확히 정의함으로써, 개념적인 아키텍처를 보다 실용적으로 설계하는데 도움이 되게 하고자 한다.

• Journal of Internet Computing and Services
• /
• v.7 no.4
• /
• pp.11-22
• /
• 2006

Software product-lines methodology is the software development paradigm to build the target system by customizing the variable part of software assets according to requirements. To attain this, the commonalities and variabilities of the system family should be modeled explicitly at early stage. Although the researches on general software product-lines are active, the researches on component-based real-time embedded software product-lines are rather inactive. In this paper a code generation system to support the functional variabilities via feature model and generate the code for synchronization via state model is proposed to increase the productivity of the development of the real-time embedded software product-lines.

• Journal of the Korea Society for Simulation
• /
• v.19 no.4
• /
• pp.179-188
• /
• 2010

The concern of Software Product Line(SPL) engineering is spreading widely because the program or product developers are able to satisfy the customer's demands quickly and give a way to handle maintenance efficiently. SPL is a reuse paradigm that reuse common parts and adopts variable parts optionally to form a differentiated product by analyzing domains. Purposes of this paper are to design an architecture which has a dynamic reconfiguration function and to develop basic components which are the basic unit of reconfiguration to raise the reuse level of the guided weapon system using the SPL. Initially we design an architecture and define basic components for developing a dynamic reconfigurable components based on SPL. Then we develop the composer for physical components and behavior components referenced by behavior models of OneSAF.

• The Journal of the Korea Contents Association
• /
• v.12 no.8
• /
• pp.96-104
• /
• 2012

The reusability problems in the existing object-oriented development method and component development method is the problem that should be also resolved in the mobile development. Changing the function in mobile applications need to upgrade the entire mobile application, which can cause problems in mobile application in conjunction with other applications within the device. Thus, the changable functions in mobile application should be developed by considering their reusability. In this paper, we propose the customization technique that can be improved reusability for a variety of requirements of mobile application. We propose the self-adaptable customization technique that can change dynamically for the function to require changes by applying the data variability among variabilities.

• Journal of the Korea Society for Simulation
• /
• v.15 no.2
• /
• pp.59-69
• /
• 2006

Component-based software development is introduced as a new development paradigm in software development method. This approach is different from existing software development approach because it is based on reusable and autonomous unit, component. Therefore, component-based development(CBD)is divided into two stages; component development process and component assembly process; application development process. Component development process is the core of CBD because component has a key for good software. Currently many methodologies or tools have been introduced by various academies or industries. However, those don't suggest systematic and flexible modeling techniques adaptable easily into component development project. Existing approaches have a unique orarbitrary modeling technique or provide heuristic guidelines for component modeling. As a result, many component developers are faced with a difficult problems; how to developcomponent models, when develop which diagrams, and so on. In order to address this problem, we suggest a meta-model driven approach for component development in this paper. We provide meta-models according to both layer and development phase. We expect that suggested meta-models allow component developers to develop appropriate models of the time.

• Journal of KIISE:Software and Applications
• /
• v.33 no.2
• /
• pp.154-166
• /
• 2006

Product Line Engineering(PLE) is a software reuse paradigm that core assets are defined using common features in a domain and are instantiated in various applications. To apply the core asset effectively, variants which satisfy application requirements are extracted and the core asset should be also instantiated based on the variants. For the work, variability on architecture and components should be extracted exactly and an instantiation process and guidelines should be defined based on this variability In this paper, we define variability types depending on core assets elements and describe artifact templates related to tile variability. We also propose a systematic process which uses defined core assets including variability and verify practicability of the proposed process and variability expression through doing ease study. If utilizing with the proposed process in PLE, it can be feasible to model concrete core asset and variability and to utilize practical application engineering.