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

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

• The KIPS Transactions:PartD
• /
• v.13D no.6 s.109
• /
• pp.807-814
• /
• 2006

Along with the enlargement of application scope, the growth of requirements complexity, and the fast development of product for embedded system, lots of industries developing embedded software try to evolve their traditional development environment into the new paradigm such as product line engineering approach. In order to sufficiently support the evolution, software architecture is essentially required to develop the embedded software. In this paper, we propose a tool, named TToSA which translates the conventional software models to software architecture models. Our TToSA is developed with the critical implication about that an industry can approach toward the new development paradigm without the big change of the existing software development method.

• 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.33 no.12
• /
• pp.1008-1021
• /
• 2006

Product line engineering(PLE) is one of the recent and effective reuse approaches that enables developing a number of applications by instantiating a core asset. Elements of a core asset are product line architecture(PLA), component, and decision model. Among these elements, PLA is the key element since it defines the overall structure of the core asset. Although numerous PLE methodologies have been introduced, it is still unclear what should be the elements of a PLA and how to systematically instantiate it for specific applications. Formal specifications can play a key role in defining detailed and precise instantiation process. In this paper, we first present a meta model of PLA and show how to specify PLA in a formal language, Object-Z. Then, we propose instantiation rules using formal specification and those rules precisely define constraints for instantiating PLA. By applying the proposed formal specification, we believe PLA instantiation can be carried out precisely and correctly, yielding high quality software development.

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

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

• The KIPS Transactions:PartD
• /
• v.15D no.6
• /
• pp.803-814
• /
• 2008

Product line architectures include variable parts to be selected according to product specific requirements. In order to derive architectures that are valid for a particular product from product line architectures, variabilities of product line architectures must be systematically managed. In this paper, we adopt an approach to variability management of product line architectures through an explicit mapping between a feature model and product line architecture models. If this mapping is incorrect or there exists inconsistency among product line architectural elements, variabilities of product line architectures cannot be managed correctly. Therefore, this paper formally defines product line architectural models in terms of conceptual, process, deployment, and module views, and mapping relationships between the feature model and the architectural models. Consistency rules for correct variability management of product line architectures are defined in terms of consistency in each of product line architecture model, consistency between different architectural view models, and consistency between a feature model and product line architectural models. These consistency rules provide a theoretical foundation for deriving valid product architecture from product line architectures.

• The KIPS Transactions:PartD
• /
• v.16D no.1
• /
• pp.93-104
• /
• 2009

Modular implementation of a feature is a first step toward feature-oriented product line engineering, which develops and then utilizes core assets to configure products in terms of features. Aspect-oriented programming provides effective mechanisms for improving the modularity of feature implementations. However, as features in general are not independent of each other, changes in the implementation of one feature may cause changes to or side effects in the implementation of other features. Moreover, since the time at which a feature is incorporated into products, called feature binding time, may be various from compile time through load time to run time, a feature may have to be implemented differently depending on when the feature is bound into a product. To make each feature implementation module as independent as possible, this paper proposes aspectual implementation patterns that can effectively separate feature dependencies as well as feature binding time from feature implementation modules. These patterns enable flexible composition of feature implementation modules without affecting other modules according to feature selection. The approaches are demonstrated and evaluated based on a product line of scientific calculator applications.

• 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
• /
• 2006.06c
• /
• pp.154-156
• /
• 2006

제품 계열 공학은 재사용에 기반을 둔 소프트웨어 개발 방법론으로서 웹 응용들에서 요구되는 비용 절감 및 시장 적시성의 성취를 이루는데 도움을 주고 있다. 웹 응용의 개발을 제품 계열로 이루고자 하는 연구가 진행되었지만, 웹 응용이 가진 핵심 자산들을 확인하고. 정의하는 체계적인 절차를 제안하지는 못한다. 본 논문에서는 인해 웹 응용 도메인에 적합한 핵심 자산으로서의 체계적인 도메인 요구사항 추출 방법을 제안한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2005.05a
• /
• pp.263-266
• /
• 2005

다중센서데이터 융합시스템(MSDFS)은 여러 센서로부터 획득된 이질의 데이터를 정규화된 포맷으로 융합하고 단일 센서에서의 획득오차를 최소한으로 줄여 표적의 정확한 식별 및 판단을 지원하는 시스템이다. 이 시스템들은 고유의 기능을 수행하는 모듈들에 대한 고수준의 재사용성을 요구하므로, 현재의 소프트웨어공학 기법을 적용시 공통부분에 대한 효율적 설계가 어렵다. 따라서 본 논문에서는 시스템 개발에 이러한 비효율적인 요소를 제거하는 제품-계열 개발방법론을 MSDFS의 임베디드 소프트웨어 설계에 적용한다. 이를 위해 분석 대상에 대한 영역지정에서부터 재사용가능한 컴포넌트의 식별까지 설계 하며, 마지막으로 설계된 모델에 대한 검증을 위해 GQM 패러다임을 적용한다. 또한 산출물에 대한 성능평가 기준을 제시하여 시스템 개발을 효과적으로 향상시킬 수 있는 방안을 제시한다.