• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2009.05a
• /
• pp.415-418
• /
• 2009

최근 서비스 지향 아키텍처 (Service Oriented Architecture SOA) 기반의 애플리케이션 개발에 맞게 비즈니스 프로세스의 유연성을 확보하고 재사용을 증진시키기 위하여 비즈니스 프로세스 패밀리 모델(Business Process Family Model: BPFM)이 제시되었다. BPFM은 소프트웨어 프로덕트 라인 방법의 가변성 분석 기법을 사용하여 비즈니스 프로세스 군 (family)에서 나타날 수 있는 가변성을 분석하여 이를 명시적으로 표현하고 있는 모델이다. BPFM으로부터 여러 개의 BPM (Business Process Model)을 개발하기 위해서는 가변성 결정 및 가지치기 (Decision and Pruning) 과정을 거쳐야 한다. 이 때 가변성 사이에는 서로 협력적 또는 배타적인 관계를 가질 수 있고 이는 가변성 결정과 가지치기에 영향을 미치게 되는데, 현재 제시된 BPFM에는 이러한 바인딩 정보에 대해서 아직 고려하지 않고 있다. 본 논문에서는 비즈니스 프로세스 군에서 식별될 수 있는 가변성들 사이의 의존관계의 유형을 분석하고 이 정보를 모델의 형태로 나타낼 수 있는 방법을 제시한다. 먼저 BPFM에 포함된 가변성 정보를 독립된 의존관계 분석모델로 추출해 내고 각 가변성 결정유형에 따라 표현방법을 제시한다. 추출된 모델에서 의존관계를 표현하고 가변성 결정이 영향을 미치는 범위의 가변성들을 클러스터할 수 있는 방법을 제공한다. 본 방법을 이용함으로써 가변성 결정회수를 현저히 줄일 수 있음을 사례연구를 통해 보여준다. 또한 잘못된 가변성 결정으로 인한 BPM의 기능 불일치를 해소할 수 있음을 보여준다.

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

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.1
• /
• pp.1-6
• /
• 2014

Many companies have tried to adopt Software Product Line Engineering for improving the quality and productivity of information systems and software product. There are several models defined in software product line methodology and each model has different abstraction level. Therefor it is important to maintain the traceability and consistency between models. In this paper, consistency checking rules are suggested by traceability matrix of work products.

• The KIPS Transactions:PartD
• /
• v.16D no.5
• /
• pp.791-800
• /
• 2009

Recently, the business process family model (BPFM), which is new approachfor assuring businessflexibility and enhancing reuse in application development with service oriented architecture (SOA), was proposed. The BPFM is a model which can explicitly represent the variabilities in business process family by using the variability analysis method of software product line. Many business process models (BPM) can be generated automatically through decision and pruning processes from BPFM. At this time, the variabilities tend to have inclusive or exclusive dependencies between them. This affects the decision and pruning processes. So far, little attention has been given to the binding information of variability dependency in the BPFM. In this paper, we propose an approach for analyzing various types of dependency relationships between variabilities and representing the variability and their relationships as a dependency analysis model. Additionally, a method which can trace the variabilities affected by a decision on the dependency analysis model is presented. The case study shows that the proposed approach helps to reduce the number of variability decision and to solve a disagreement of functions in BPM produced by incorrectly deciding the variability.

• Proceedings of the Korean Information Science Society Conference
• /
• 2011.06a
• /
• pp.124-127
• /
• 2011

스마트 폰과 같은 모바일 디바이스의 연산 능력 향상으로 다양한 모바일 어플리케이션의 개발이 증가하고 있다. 특히, 모바일 디바이스에 장착된 다양한 센서를 통해 수집되는 컨텍스트 정보를 기반으로한 모바일 컨텍스트 애플리케이션에 대한 요구가 크게 증가하는 추세이다. 하지만 모바일 컨텍스트는 모바일 디바이스의 다양한 종류와 운영체제, 정보의 종류 등에 따라 다양한 형태가 존재한다. 모바일 컨텍스트의 다양성에 의해 모바일 컨텍스트 애플리케이션 개발에 추가적인 비용이 발생한다. 본 논문에서는 효과적인 모바일 컨텍스트 애플리케이션의 개발을 위한 모바일 컨텍스트의 가변성 모델을 제안한다. 가변성 분석을 통해 모바일 컨텍스트의 다섯 가변점과 각 가변점의 가변치를 정의한다. 또한 제안된 가변성 모델을 기반으로 활용 가능한 사례를 제시하고, 제안된 모델의 평가를 수행한다.

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

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

• The KIPS Transactions:PartD
• /
• v.19D no.1
• /
• pp.81-94
• /
• 2012

FORM(Feature-Oriented Reuse Method) is one of representative product line engineering methods. The essence of FORM is the FORM architecture models, which can be reused in the development of multiple products of a software product line. The FORM architecture models, however, have the following problems when applied in practice. First, they are not standardized models like UML(Unified Modeling Language) and therefore they can be constructed only through a specific modeling tool. Second, they do not represent architectural variability explicitly. Instead their variability is only managed through a mapping from a feature model. To address these two problems, we developed at first a method for representing the FORM architecture models using UML, which enables the FORM architecture models to be constructed through various available UML modeling tools. Also, we developed an effective method for representing as well as managing the variability of the FORM architecture models through a mapping from a feature model.

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

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