• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.501-503
• /
• 2000

컴포넌트가 보편화되고 있는 현 시점에서 컴포넌트의 사용은 증가하고 있다. 이러한 컴포넌트들을 효과적으로 재사용하기 위해서는 컴포넌트 설계와 재사용의 올바른 분석과 설계가 요구된다. 재사용의 요구사랑을 만족하기 위해서 컴포넌트의 설계시에 발생할 수 있는 기능과 적합성의 불일치를 줄이고자하는 연구가 활발히 진행되고 있다. 본 논문에서는 공통성과 가변성 분석을 하기 위하여 도메인의 특성이 서비스 중심적인 관점인 경우에 대하여 접근을 했다. 이를 위하여 인터페이스의 추출이 선행되어야 하고, 추출된 인터페이스를 중심으로 두 도메인에 존재하는 공통성과 가변성을 추출하였다.

• Journal of KIISE:Software and Applications
• /
• v.32 no.2
• /
• pp.119-127
• /
• 2005

Product line analysis is an activity for analyzing requirements, their relationships, and constraints in a product line before engineering product line assets (e.g., architectures and components). A feature-oriented commonality and variability analysis (called feature modeling) has been considered an essential part of product line analysis. Commonality and variability analysis, although critical, is not sufficient to develop reusable and adaptable product line assets. Dependencies among features and feature binding time also have significant influences on the design of product line assets. In this paper. we propose a feature-oriented product line analysis model that extends the existing feature model in terms of three aspects (i.e., feature commonality and variability, feature dependency, and feature binding time). To validate the consistency among the three aspects we formally define the feature-oriented product line analysis model and provide rules for checking consistency.

• Journal of KIISE:Software and Applications
• /
• v.34 no.3
• /
• pp.196-211
• /
• 2007

In the Product Line Engineering (PLE), current studies about an analysis of the feature have uncertain and ad-hoc criteria of analysis based on developer’s intuition or domain expert’s heuristic approach and difficulty to extract explicit features from a product in a product line because the stakeholders lack comprehensive understanding of the features in feature modeling. Therefore, this paper proposes a model of the analyzing commonality and variability of the feature based on the Ontology. The proposed model in this paper suggests two approaches in order to solve the problems mentioned above: First, the model explicitly expresses the feature by making an individual feature attribute list based on the meta feature modeling to understand common feature. Second, the model projects an analysis model of commonality and variability using the semantic similarity between features based on the Ontology to the stakeholders. The main contribution of this paper is to improve the reusability of distinguished features on developing products of same line henceforth.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07b
• /
• pp.325-327
• /
• 2005

컴포넌트는 컴포넌트 기반 개발(Component Based Development, CBD)기술에서 재사용되는 기본 단위로서 OOP(Object Oriented Programming, OOP)의 객체보다 상대적으로 큰 단위의 기능성을 제공하며 재사용성이 뛰어나다. 모델 기반 아키텍처(Model Driven Architecture, MDA)는 모델들 간의 다양한 변환(Transformation)을 활용하여 어플리케이션 개발을 자동화하는 새로운 패러다임으로서 소프트웨어의 생산성을 향상시킨다. 그러나 MDA 는 컴포넌트와 같은 어플리케이션들 간의 공통성과 가변성을 활용한 재사용성을 직접적으로 지원하지는 않는다. 본 논문에서는 CBD 와 MDA 의 장점과 한계점을 알아보고 서로의 단점을 보완할 수 있도록 컴포넌트 PIM 과 컴포넌트 기반의 MDA 공학 프로세스를 제안한다. 제안된 컴포넌트 PIM 과 프로세스를 이용하면 어플리케이션들 간의 공통성과 가변성을 이용한 뛰어난 재사용성과 자동화를 통한 생산성의 ,향상 및 높은 유지보수성을 가질 수 있다.

• Journal of KIISE:Software and Applications
• /
• v.27 no.9
• /
• pp.920-930
• /
• 2000

컴포넌트 기반의 소프트웨어 개발이 소프트웨어 복잡성, 비용, 그리고 품질을 해결하기 위한 새로운 대안으로 소개되고 있다. COM, Enterprise JavaBeans, CORBA 컴포넌트 모델등과 같은 다양한 컴포넌트 아키텍쳐들이 소개되고 있으며 컴포넌트 기반의 소프트웨어 개발 방법론과 여러 CASE 도구들이 이를 지원하고 있다.[1,2,3,4]. 그러나 현재 컴포넌트를 구현할 수 있는 기술은 제시되어 있지만 컴포넌트를 모델링하는 기법들에 대한 연구는 미약한 상태이다. 본 논문에서는 도메인 분석에서 공통성과 가변성 추출 및 클러스터링 기법을 이용한 컴포넌트를 분석하는 기법을 제시한다. 즉 컴포넌트 추출 기법, 컴포넌트의 핫스팟(또는 가변성)표현 기법, 컴포넌트 요구사항 정의 기법 등을 제시한다. 컴포넌트 개발에 있어서 이러한 모델링 기법을 적용함으로써 컴포넌트를 효율적으로 개발할 수 있을 뿐만 아니라 재사용성이 높은 고품질의 컴포넌트 개발을 지원할 수 있다.

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

Software product line engineering is a method that prepares for the future reuse and supports to seamless reuse in application development process. Commonality and variability play central roles in all product line development processes. Reusable assets will become core assets by explicitly representing C&V. Indeed, the variabilities that art identified at each phase of core assets development have different levels of abstraction. In the past, these variabilities have been handled in an implicit manner and without distinguishing the characteristics of each core assets. In addition, previous approaches have depended on the experience and intuition of a domain expert to recognize commonality and variability. In this paper, we suggest a 2-dimensional analyzing method that analyzes the variabilities of core assets in software product line. In horizontal analysis process, the variation types are analyzed in requirements, architecture, and component that are produced at each phase of development process. In vertical analysis process, variations are analyzed in different abstract levels, in which the region of commonality is identified and the variation points are refined. By this method, the traceability of variations between core assets will be possible and core assets can be reused seamlessly.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.328-341
• /
• 2007

When the decision to initiate a software product line has been taken, the first step is the domain analysis describing the variability in the requirements, the second important step is the definition of a domain architecture that captures the overall structure of a series of closely related products. A domain architecture can be a core asset in product line by describing the commonalities and variabilities of the products contained in the software product line. The variabilities, which are identified at each phase of the core assets development, are diverse in the level of abstraction. Therefore, it is important to clearly define, systematically identify, and explicitly represent variability at the architectural level. However, it is difficult to identify and represent the variability which should be considered at the architecture level, because these may be appeared in architecture elements and in architecture configuration. In this paper, we suggest a method of developing domain architecture as a core asset in product line where commonality and variability are explicitly considered. First of all, we will describe a domain architecture metamodel that can explicitly define commonality and variability concepts by extending the Object Management Group's ($OMG^{TM}$ Reusable Asset Specification eRAS) model. Using the domain architecture metamodel, architecture elements are defined and the variations that can be identified at the architecture level are classified into two types in according th abstract level. Additionally, we describe a domain architecture where commonality and variability are explicitly considered on basis of this metamodel.

• Journal of KIISE
• /
• v.42 no.1
• /
• pp.76-85
• /
• 2015

Software Product Line Engineering is a collection of techniques that analyze the commonalities and variabilities of the products within a product family and produce products using such information. In Software Product Line Engineering, construction of the correct core assets is very important. To accomplish this, the commonalities and variabilities must first be definitively identified, both to provide traceability between the core assets, and to guarantee the reliability of the products. This paper suggests software product line development and test processes based on CVL for the differentiation of commonalities and variabilities. The proposed approach enables correct building of the core assets through procedures to keep traceability and guarantee the reliability of the products.

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

개발한 자산의 재사용성을 증대시키기 위해서는 프로덕트 라인에서 가장 중요한 제품간의 공통성과 가변성을 식별하고 이를 표현하는 기술이 잘 정의되어 있어야 한다 이를 위해서는, 다양한 제품의 요구사항을 만족시켜 줄 수 있도록 자산을 모델링 할 때 가변성을 제공하는 부분을 명세화하고 이를 독립적인 모델로 관리함으로써 자산의 재사용성을 향상시키는 방법이 필요하다. 본 논문은 핵심 자산 개발시 정의하는 결정 모델의 유형을 정의하고 결정요소들 간의 관계를 추적할 수 있는 지원 도구의 프로토타입을 제안한다

• The KIPS Transactions:PartD
• /
• v.14D no.7
• /
• pp.773-782
• /
• 2007

Software produce line engineering is a method that prepares for future reuse and supports seamless reuse in the application development process. Analyzing the commonality and variability between products in a product line is one of the essential concerns that must be considered when building a product line. In this paper, we suggest to combine a product line engineering approach with RFID applications technology. More concretely, common activities are identified among the RFID-enable applications and the variability in the common activities is analyzed in detail. Then, we suggest reusable product line architecture as a product line asset. In addition, as a tool for supporting this research, a framework which provides both reusable product line architecture for REID applications and the components that implement concrete realization of the architecture is developed. Sharing a common architecture and reusing assets to deploy recurrent services may be considered an advantage in terms of economic significance and overall quality.