• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.11
• /
• pp.739-746
• /
• 2013

Variability of the software product line that differentiates member products within a product line must be described with precise meaning and visualized so as easy to select. Moreover, it should be easy to manage. Variability description approaches can largely be divided into two approaches, integrated variability description approach and orthogonal variability description approach. Orthogonal Variability Description Language (OVDL) was developed for clear and precise description of variability without ambiguity. This paper validates the variability description capability of OVDL by translating the variability models of Inter-Working Function (IWF) product line described by using Orthogonal Variability Model (OVM) notations into variability descriptions in OVDL.

• Electronics and Telecommunications Trends
• /
• v.23 no.1 s.109
• /
• pp.21-32
• /
• 2008

임베디드 시스템을 위한 응용 프로그램 개발 도구로서 통합개발환경을 이용하는 것은 소프트웨어 개발의 생산성과 코드의 완성도를 향상시킬 수 있다는 점에서 매우 중요하게 인식되고 있다. 최근에 USN에 대한 관심이 높아지면서 이를 위한 여러 가지 응용소프트웨어들이 개발되고 있으나, 통합개발환경의 부재로 명령어 라인 기반의 개발 방식이 사용되고 있는 실정이다. 이와 같은 방식은 불편함을 야기할 뿐만 아니라 개발 시간을 증가시킬 수 있으며, 궁극적으로 USN 응용 소프트웨어의 개발을 어렵게 만드는 요인이 된다. 본 고에서는 이와 같은 문제점을 해결하기 위하여 USN 응용 소프트웨어를 빠르고 편리하게 개발할 수 있는 통합개발환경의 동향을 살펴보고 ETRI의 본 연구팀에서 개발한 USN 소프트웨어 통합개발 도구인 “NanoEsto”를 기술하고 상용 제품과의 비교를 수행하였다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2012.11a
• /
• pp.1547-1550
• /
• 2012

소프트웨어 제품라인의 핵심 자산을 개발할 때 제품라인에 포함된 휘처 사이의 관계를 고려하여 핵심 자산을 개발하지 않으면, 한 휘처의 변화가 핵심 자산의 많은 부분에 영향을 미칠 수가 있고, 미처 고려하지 못한 휘처 관계에 의해 제품이 동작중에 의도치 않은 문제가 발생할 수 있다. 휘처 사이의 존재할 수 휘처 관계 타입을 미리 알고 있다면, 실제 휘처 관계를 분석할 때 도움이 되고, 각 타입별로 어떻게 핵심 자산을 개발해야 하는지 가이드라인을 제시할 수 있다. 기존에 많은 연구자들이 휘처 관계 타입을 제시하였지만 아직까지 제안된 휘처 관계 타입들을 비교하고 분석하는 연구가 이루어지지 않았다. 이에 본 논문에서는 지금까지 제안된 휘처 관계 타입들을 살펴보고, 제안된 관계 타입들을 비교 및 논의하고자 한다. 또한 기존에 제안된 휘처 관계 타입 중 위쳐 사이의 관계로 보기 어렵거나 중복이 되는 타입을 제외하여 휘처 관계 타입 리스트를 정리 및 제안하였다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2010.11a
• /
• pp.276-279
• /
• 2010

소프트웨어 제품 라인 개발 패러다임은 관련 제품들 사이의 공통점과 차이점을 이용해 보다 전략적인 재사용을 가능하게 함으로써 소프트웨어 개발 생산성을 높여 주는 개발 방법론이다. 공통점과 차이점을 분석하고 모델링하기 위해 가장 중요한 모델이 특성 모델이다. 특성 모델은 규모가 커짐에 따라 오류를 포함할 가능성이 커지며 이를 검증하기 위한 자동화된 도구가 필요하다. 본 논문에서는 온톨로지를 자바 언어로 구현 가능하게 해주는 Protege API, OWL기반의 시맨틱 웹 규칙 언어인 SWRL, 규칙 추론 엔진인 Pellet Reasoner 등의 기술을 이용한 특성 모델 검증 도구를 제안한다.

• Journal of KIISE:Software and Applications
• /
• v.36 no.6
• /
• pp.431-442
• /
• 2009

The Software Product Line (SPL) engineering is one of the most promising software development paradigms. With Feature-Oriented Reuse Method (FORM), reusable and flexible components can be built to aid the delivery of various software products such as mobile phone and digital TV applications based on commonalities and variabilities identified during Feature modeling. Model Driven Architecture (MDA) is also an emerging technology which supports developing software products to work on different platforms with platform independent models (PIM). Combining advantages of these two approaches is helpful to build a group of software products which share common Features while working on various platforms. As first step to combine FORM with MDA, we extend UML2.0 with profiles by which FORM architectures and parameterized Statecharts can be modeled. Secondly, we provide rules to examine whether Features are allocated at positions of elements of Statecharts consistently between a Feature model and a parameterized Statechart. Some rules are designed to check the consistency between FORM architectures and parameterized Statecharts. A case study on an elevator control system is provided to demonstrate the feasibility of our modeling approach and consistency checking rules.

• The KIPS Transactions:PartD
• /
• v.10D no.4
• /
• pp.697-708
• /
• 2003

In a software product line approach, developers first develop common software architecture and components by analyzing the characteristics of all software members, and then produce each application by integrating components. The approach is considered very effective means for developing and maintaining in parallel a software product family. Main disadvantage of this approach is that it requires a big up-front investment in preparing product line. Therefore, it takes time to deliver the first version. In this paper, we present an incremental method to develop software families, which requires small additional cost for initial versions and allows an organization to move smoothly to full-scale product line. We present our method by explaining how to record and upgrade the results of variations analysis, and show the application of our method by developing a family of YBS. Our method is a low-risk approach that can be effectively applied to an organization that starts developing software systems but has to deliver the first versions quickly to the market.

• Journal of Korea Society of Industrial Information Systems
• /
• v.20 no.3
• /
• pp.51-60
• /
• 2015

Traceability targets provision of information to stakeholders required for analyzing impacts among artifacts due to changes. Unlike single product development, in software product line developing the family of products the complexity of maintaining and managing traceability between two life cycles, domain and application engineering is so high. Accordingly, variability traceability management approach centred on orthogonal variability model that manages variability separated from development artifacts has been conceptually proposed, but its efficiency has not verified yet. This paper verifies whether orthogonal variability model based traceability can provide required traceability through an example. As the results, the OVM-based variability tracing method supports well to narrow down artifacts affected by the changes. However, the method does not support tracing the exact artifacts or exact part of an artifact affected by the change.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.14 no.2
• /
• pp.115-120
• /
• 2014

Many product line engineering methods use the feature model to structure commonality and variability among products in terms of features and to derive a product feature configuration, which is the set of features required for the development of a product. Features to be selected during product derivation are mainly determined based on the quality attributes required for a product. Most methods published so far derived an optimal product feature configuration through linear co-relationship between features and quality attributes. However, the co-relationship between features and quality attributes can be formulated as a non-linear function because of feature interactions. This paper proposes a method that derives an optimal product feature configuration considering feature interactions. Four product line cases are used to validate the proposed methods.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.35 no.2
• /
• pp.57-63
• /
• 2012

Software release planning model of software product lines was formulated as a precedence-constrained multiple 0-1 knapsack problem. The purpose of the model was to maximize the total profit of an entire set of selected features in a software product line over a multi-release planning horizon. The solution approach is a dynamic programming procedure. Feasible solutions at each stage in dynamic programming are determined by using backward dynamic programming approach while dynamic programming for multi-release planning is forward approach. The pre-processing procedure with a heuristic and reduction algorithm was applied to the single-release problems corresponding to each stage in multi-release dynamic programming in order to reduce the problem size. The heuristic algorithm is used to find a lower bound to the problem. The reduction method makes use of the lower bound to fix a number of variables at either 0 or 1. Then the reduced problem can be solved easily by the dynamic programming approaches. These procedures keep on going until release t = T. A numerical example was developed to show how well the solution procedures in this research works on it. Future work in this area could include the development of a heuristic to obtain lower bounds closer to the optimal solution to the model in this article, as well as computational test of the heuristic algorithm and the exact solution approach developed in this paper. Also, more constraints reflecting the characteristics of software product lines may be added to the model. For instance, other resources such as multiple teams, each developing one product or a platform in a software product line could be added to the model.

• Journal of Internet Computing and Services
• /
• v.11 no.4
• /
• pp.107-117
• /
• 2010

The feature models representing the common and variable concepts among the software products and the feature configurations generated by selecting the features to be included in the target product are the essential components in the software product lines methodology. Although the researches on the formal semantics and reasoning of the feature models and feature configurations are in progress, the researches on feature model ontologies and feature configuration validation using the semantic web technologies are yet insufficient. This paper defines the formal semantics of the feature models and proposes a feature configuration validation technique based on ontology and semantic web technologies. OWL(Web Ontology Language), a semantic web standard language, is used to represent the knowledge in the feature models and the feature configurations. SWRL(Semantic Web Rule Language), a semantic web rule languages, is used to define the rules to validate the feature configurations. The approach in this paper provides the formal semantic of the feature models, automates the validation of feature configurations, and enables the application of various semantic web technologies, such as SQWRL.