• 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 Journal of Society for e-Business Studies
• /
• v.12 no.3
• /
• pp.33-47
• /
• 2007

The requirements have been changed during development progresses, since it is impossible to define all of software requirements. These requirements change leads to mistakes because the developers cannot completely understand the software's structure and behavior, or they cannot discover all parts affected by a change. Requirement changes have to be managed and assessed to ensure that they are feasible, make economic sense and contribute to the business needs of the customer organization. We propose a feature-oriented requirements change management method to manage requirements change with value analysis and feature-oriented traceability links including intermediate catalysis using features. Our approach offers two contributions to the study of requirements change: (1) We define requirements change tree to make user requirements change request generalize by feature level. (2) We provide overall process such as change request normalization, change impact analysis, solution dealing with change request, change request implementation, change request evaluation. In addition, we especially present the results of a case study which is carried out in asset management portal system in details.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2007.05a
• /
• pp.275-278
• /
• 2007

모바일 콘텐츠 시스템을 편리하고 빠르게 생산하기 위해서는 프로덕트라인의 적용이 필요하며 공통성과 가변성을 식별하는 도메인 분석은 프로덕트라인 적용의 핵심이다. 그러나 현재 모바일 콘텐츠 시스템의 도메인 분석은 휘처 중심의 도메인 분석 방법(feature-oriented approach)을 이용하고 있어 성숙되지 않은 도메인이나 새로운 도메인의 경우 분석의 결과가 프로덕트라인 방식으로 생산하고자 했던 본래의 목표를 만족시키지 못하고 분석의 단계적인 절차를 제공하지 못한다. 따라서 본 논문에서는 기존에 제시된 목표, 시나리오, 휘처 기반의 도메인 분석방법을 적용하는 방안을 제시하여 이러한 문제점을 해결한다.

• Proceedings of the Korea Association of Information Systems Conference
• /
• 2005.05a
• /
• pp.273-280
• /
• 2005

프로덕트 라인은 다양하게 빠르게 변화하는 시장의 요구사항과 특정 도메인에 속하는 응용들 간의 재사용 가능한 아키텍처 및 컴포넌트의 구성으로부터 연관된 시스템 구축 시 생산성과 품질의 향상을 제공함으로써 현재 많은 관심의 초점이 되고 있다. 이들 프로덕트 라인에서는 프로덕트들 사이의 공통성과 변화성에 초점을 두고 이들 분류 방법으로 휘처 모델링이라는 개념을 주로 사용하여 분석하고 있다. 또한 재사용 가능한 아키텍처는 많은 변화 계획들과 메커니즘을 포함하고 있다. 그러나 지금까지 이러한 변화들이 일어나는 상황을 이해하는 것과 특별한 상황에서도 가능하게 하는 옵션들을 기록하는 것은 명확히 이루어지지 못하였다. 따라서, 명확한 변화성의 표현과 아키텍처에서 변경되는 적절한 위치를 식별하는 것이 중요하다. 그러므로, 본 논문에서는 휘처 모델을 기반으로 한 아키텍처 상의 컴로넌트 변화성과 컴포넌트 간의 관련성에서의 변화성 표현방법을 기술하고. 제시한 이론을 기반으로 웹 학습 시스템을 개발하고자 한다.

• 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 the Korea Academia-Industrial cooperation Society
• /
• v.17 no.1
• /
• pp.733-744
• /
• 2016

The legacy methods for converting a business model to a feature model make it difficult to support an automatic transformation due to a dependence on a domain analyzers' intuitions, which hinders the feature oriented development for the integration of feature modeling in business modeling. This paper proposes a method for converting a BPMN business model into a feature model based on syntax. To allow the conversion between the heterogeneous models from BPMN to the FM(Feature Model), it defines the grouping mechanism based activities' syntax, and then makes translation rules and a method based on the element (represent business function) and structure (relationships and process among elements), which are common constructs of their models. This method was applied to an online shopping mall system as a case study. With this mechanism, it will help develop a mechanical or automated structure transformation from the BPMN model to the FM.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2003.11c
• /
• pp.1563-1566
• /
• 2003

프로덕트 라인은 다양하고 빠르게 변화하는 시장의 요구사항과 특정 도메인 영역에 속하는 애플리케이션 간의 재사용 가능한 아키텍처 및 컴포넌트의 구성으로부터 연관된 시스템 구축시 생사성과 품질의 향상을 제공함으로써 현재 많은 관심의 초점이 되고 있다. 또한, 이들 프로덕트 라인에서는 프로덕트들 사이의 공통성과 변화성에 초점을 두고 이들 분류 방법으로 휘처 모델링이라는 개념을 주로 사용하여 분석하고 있다. 또한 재사용 가능한 아키텍처는 많은 변화 계획들과 메카니즘을 포함하고 있다. 하지만, 아키텍처를 설계하기 위한 아키텍처에서의 변화성 관리에 대한 명확한 방법이 미흡하다. 따라서 본 논문에서는 재사용 가능한 아키텍처를 설계하기 위해 변화성의 명확한 표현과 아키덱처에서의 적절한 위치를 식별하기 위해, 다양한 변화성 타입을 정의하고, 휘처 모델을 기반으로한 아키텍처의 변화성과 아키덱처의 컴포넌트 관련성에서의 변화성 표현 방법을 기술하고 사례 연구로 웹기반교육 시스템 개발에 적용하고자 한다.

• Journal of the Korea Society of Computer and Information
• /
• v.27 no.12
• /
• pp.197-207
• /
• 2022

The Naval Combat System operates in multiple software components for efficient functional processing. Data transmission and reception between components is performed in real time using DDS(Data Distribution Service). Reliable Post-Analysis requires the collection of all DDS messages. However, Software workload and development costs increase because common functions for all messages must be developed directly. In the paper, We propose an improved Post-Analysis based on the Feature Model and a new development system using it. Functions for the modified message were applied as variable domains of the Feature Model. When Build Center updates Post-Analysis, it automatically processes all software tasks associated with Post-Analysis. The proposed development system simplified the overall work procedure, and work time was significantly reduced compared to the existing development system.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.7
• /
• pp.337-352
• /
• 2017

Clone-and-own reuse is an approach to creating new software variants by copying and modifying existing software products. A family of legacy software products developed by clone-and-own reuse often requires high maintenance cost and tends to be error-prone due to patch-ups without refactoring and structural degradation. To overcome these problems, many organizations that have used clone-and-own reuse now want to migrate their legacy products to software product line (SPL) for more systematic reuse and management of software asset. However, with most of existing methods, variation points are embedded directly into design and code rather than modeled and managed separately; variation points are not created ("engineered") systematically based on a variability model. This approach causes the following problems: it is difficult to understand the relationships between variation points, thus it is hard to maintain such code and the asset tends to become error-prone as it evolves. Also, when SPL evolves, design/code assets tend to be modified directly in an ad-hoc manner rather than engineered systematically with appropriate refactoring. To address these problems, we propose a feature-oriented method for extracting a SPL asset from a family of legacy applications. With the approach, we identify and model variation points and their relationships in a feature model separate from implementation, and then extract and manage a SPL asset from legacy applications based on the feature model. We have applied the method to a family of legacy Notepad++ products and demonstrated the feasibility of the method.

• Journal of Software Engineering Society
• /
• v.11 no.1 s.37
• /
• pp.22-39
• /
• 1998