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

제품계열공학(Product Line Engineering, PLE)은 효과적인 재사용 기법으로, 핵심자산(Core Asset) 개발 프로세스와 어플리케이션 공학 프로세스로 구성된다. 핵심자산 개발 프로세스는 제품계열의 여러 어플리케이션들의 공통 휘쳐(Feature)들을 모델링 한 핵심자산 개발에 사용된다. 어플리케이션 공학 프로세스에서 핵심자산을 인스턴스화(instantiation)하고, 핵심자산이 제공하지 않는 어플리케이션 종속적인 기능을 모델링 한 후, 이 두 모델을 통합하여 목표 어플리케이션을 생성 개발한다. 현재의 제품계열공학 연구는 핵심자산 개발과 인스턴스화 과정에 집중되어 있고, 어플리케이션 공학 프로세스의 연구는 개념적 수준에 머물고 있다. 특히, 인스턴스화된 핵심자산 모델과 어플리케이션 종속 모델의 통합의 실용적 기법이 미흡하다. 본 논문에서는 어플리케이션 공학 프로세스의 주요 활동들에 대한 작업 순서와 실용적 지침을 제공한다.

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

• Journal of KIISE:Software and Applications
• /
• v.32 no.9
• /
• pp.835-846
• /
• 2005

A Product Line (PL) is a set of products (applications) that share common assets in a domain. Product Line Engineering (PLE) is a set of principles, techniques, mechanisms, and processes that enables the instantiation of produce lines. Core assets, the common assets, are created and instantiated to make products in PLE. Model Driven Architecture (MDA) is a new software development paradigm that emphasizes its feasibility with automatically developing product. Therefore, we can get advantages of both of the two paradigms, PLE and MDA, if core assets are represented as PIM in MDA with predefined automatic mechanism. PLE framework in the PIM level has to be interpreted by MDA tools. However, we do not have a standard UML profile for representing core assets. The research about representing PLE framework is not enough to make automatically core assets and products. We represent core asset in PIM level in terms of structural view and semantic view. We also suggest a method for representing architecture, component, workflow, algorithm, and decision model. The method of representing framework with PLE and MDA is used to improve productivity, applicability, maintainability and qualify of product.

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

소프트웨어 프로덕트 라인 공학은 두 가지 측면에서 재사용 활동을 정의한다. 첫째는 자산들의 공통성과 가변성을 분석하고 이를 명시적으로 표현하고자 하는 재사용 계획 프로세스 즉, 도메인 공학 프로세스이다 둘째는, 존재하는 핵심자산들을 이용하여 실제 프로덕트를 개발하는데 초점을 두고 있는 재사용 적용 프로세스 즉, 애플리케이션 공학 프로세스이다. 지금까지 프로덕트 라인 공학에서 많은 연구들은 재사용 계획 프로세스에 초점을 두고 있었으며, 재사용 적용 프로세스는 핵심자산의 단순한 커스터마이즈 또는 인스턴스화하는 수준으로 언급하고 있었다. 그로인해, 핵심자산들은 각기 다른 개발 프로세스에서 사용 표준 없이 적용되거나 핵심자산에 의존하여 개발 프로세스가 변경되어야 하는 문제를 발생시켰다. 본 논문에서는 프로덕트라인 핵심자산이 각기 다른 프로덕트 개발 프로세스에서 효율적으로 재사용 될 수 있도록 가이드해 주는 적용지침서 개발 방법을 제시한다.

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

• The KIPS Transactions:PartD
• /
• v.13D no.4 s.107
• /
• pp.565-572
• /
• 2006

Product Line Engineering (PLE) is an effective reuse methodology where common features among members are captured into core assets and applications are developed by reusing the core assets, reducing development cost while increasing productivity. To maximize benefits in developing systems, business case analysis for PLE is essential. If the scope for core assets is excessively broad, it will result in high cost of asset development while lowering reusability. On the other hand, if the scope is too narrow, it will result in a limited applicability which only support a small number of members in the domain. In this paper, we propose a process for business case analysis for PLE and for deciding economical analysis of core asset scope. Then, we define guidelines for each activity of the process. Since variability often occurs in PLE, we significantly treat the variability of features among members in detailed level. By applying our framework for business case analysis, one can develop core assets of which scope provide the most economical value with applying PLE.

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

Product line engineering (PLE) is a new effective approach to software reuse, where applications are generated by instantiating a core asset which is a large-grained reuse unit. Hence, a core asset is a key element of PLE, and therefore the reusability of the core asset largely determines the success of PLE projects. A tore asset is a reusable part not a whole system, and supports not only variable functions but also common functions. However, there are limitations to evaluate reusability of core asset that has these unique characteristics. This paper proposes a comprehensive quality system for evaluating the reusability of core assets, based on ISO/IEC 9126. We first identify the key characteristics of core assets, and derive the set of quality attributes that characterizes the reusability of core assets. finally, we define metrics for each quality attribute. In addition, we provide guidelines for applying the metrics and perform a case study based on rental product line. Using the proposed quality system, reusability of core assets can be more effectively and correctly evaluated.

• Journal of KIISE:Software and Applications
• /
• v.33 no.10
• /
• pp.896-914
• /
• 2006

Product line engineering (PLE) is one of the most recent and emerging reuse approaches in software engineering. Core asset, which is a reusable unit of PLE, is shared by several members in a product line (PL). So, developing a well-defined core asset is a prerequisite to increase productivity and time-to-market. Existing PLE methodologies emphasize the importance of core asset but mainly focus on analyzing core asset. And, several processes for designing core asset do not fully cover all elements of core asset which is from product line architecture (PLA) to decision model and need to augment systematic process, detailed instructions, and templates of artifacts. These problems result in difficulty with designing core asset and applying PLE. In this paper, we present an overall process and templates of artifacts to design core assets. And, we apply proposed process to a case study in order to show its applicability. With the proposed process, detailed instructions, and templates of artifacts, we believe that we can more systematically and more easily design high-quality core assets and we fully cover product line architecture, component, and decision model when designing a core asset.

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

PLE 방법론은 단일 제품이 아니라 유사한 제품들간의 공통성(Commonality)과 가변성(Variability)을 개발하고 관리하며 소프트웨어 개발 전체 생명주기에 걸쳐 부품을 조립하는 형태로 만들어진다. 또한 PLE 방법론은 재사용 단위가 가장 큰 방법론이기 때문에 최근에는 소프트웨어 업계에서 주목을 많이 받고 있다. 따라서 소프트웨어 재사용 분야가 점점 다양화되면서 어플리케이션의 특성에 적합한 프로세스에 대한 요구가 늘어나고 있다. 어플리케이션 과정은 요구사항 정의에 따라서 설계가 되어야 하고 이렇게 설계가 된 요구사항 정의와 핵심자산의 Gap 분석을 통해 정제된 설계를 얻을 수 있다. 하지만, 현재는 체계적인 절차와 기법에 대한 연구가 많이 미흡한 상태이다. 이렇게 체계적인 절차와 기법이 있다면 어플리케이션을 개발하는데 있어 보다 효율적이고, 보다 완성도 높은 어플리케이션이 개발 될 것이라고 기대한다. 따라서 본 논문에서는 제품계열공학의 핵심자산과 어플리케이션간의 Gap 분석 절차를 제안하고자 한다.

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

CEC, 근접방어무기체계, 지휘통제체계 등에 사용되는 위협평가시스템은 자동위협평가, 방어구역 위협지수, 무기할당 등의 공통된 기능을 포함하고 있고, 시스템 환경의 변화 또는 성능 향상에 따라 수시로 업그레이드가 요구된다. 따라서 본 논문에서는 생산성 향상과 중복투자 방지로 인한 비용감소 효과를 거둘 수 있는 제품계열 방법론을 위협평가시스템 개발에 적용하는 방안을 제안한다. 위협평가시스템의 제품계열 방법론 적용을 위해 핵심자산 개발 프로세스를 수행하여 제품계열 영역지정, 핵심자산, 제품계획을 정의한다. 제품계열 영역지정은 Feature 모델링을 이용하여 공통점과 차이점을 식별하고, 핵심자산은 아키텍처 설계 중심으로, 그리고 각 핵심자산의 부착 프로세스를 종합하여 제품계획을 수립한다.