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

• 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
• /
• 2003.11c
• /
• pp.1563-1566
• /
• 2003

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

• 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 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.12D no.4 s.100
• /
• pp.589-600
• /
• 2005

Application developers need effective reuseable methodology to meet rapidly changes and variety of users requirements. Product Line and CBD(Component Based Development) offer the great benefits on quality and productivity for developing the software that is mainly associate with reusable architectures and components in a specific domain and rapidly changing environments. Product line can dynamically focus on the commonality and variety feature model among the products. The product line uses the feature modeling for discovering, analyzing, and mediating interactions between products. Reusable architectures include many variety plans and mechanisms. In case of those architecture are use in product version for a long time, It is very important in architecture product line context for product line design phase. Application developer need to identify the proper location of architecture changing for variety expression. It is lack of specific variety managements to design the product line architecture until nowdays. In this paper, we define various variety types to identify the proper location of architecture changing for variety expression and to design the reusable architecture. We also propose architecture variety on feature model and describe variety expression on component relations. We implemented the web learning system based on the methodology. We finally describe how these methodology may assist in increasing the efficiency, reusability, productivity and quality to develop an application. In the future, we are going to apply the methodology into various domain and suggest international and domestic's standardization.

• Journal of KIISE:Software and Applications
• /
• v.36 no.7
• /
• pp.539-547
• /
• 2009

Software product line (SPL) engineering is an emerging paradigm for successful software reuse and has been adopted for various industrial and consumer products to improve their productivity and quality. However, most SPL methods require high initial costs and long development time, which makes many companies hesitate to adopt the SPL paradigm. In this paper we introduce a method to construct an SPL by extracting core assets from legacy components based on the feature model, which requires less initial time and effort. We also present a case study on cable set-top box software to illustrate the applicability of this method, and lessons learned that will provide guidelines for many companies to adopt the SPL paradigm.

• Journal of the Korea Society of Computer and Information
• /
• v.26 no.11
• /
• pp.101-110
• /
• 2021

The Weapon Control Software performs the function of supporting weapon operation within the Naval Combat System in connection with the Weapon System. As Weapon Control Software depends on an Weapon System, it has the characteristic that software modification is unavoidable with the change in Interface information. Modification of software causes an increase in development costs since it must take verification step such as software reliability test. In this paper, We design the standard architecture of weapon control software to minimize the modification elements of existing weapon control software. For Interface information management, Feature Model were applied to make a division between common factor and variable factor. In addition, Strategy Pattern were applied to improve the software design. Software evaluation test results show that new architecture provides better modifiability and reuse than existing software as well as the cost of development decrease.

• Journal of the Korea Society of Computer and Information
• /
• v.29 no.1
• /
• pp.139-149
• /
• 2024

In this paper, we propose the standard architecture for the IFF interface SW in naval combat management system(CMS). The proposed standard interface architecture is a method designed to reduce modification efforts and man-month of reliability test for the existing the IFF interface SW of 11 types. We identified highly dependent CMS and GFE information, leading to the redefinition of standard requirements and functions, and proceeded with the initial design applying the Naval Shield Component Platform(NSCP). Subsequently, using the Feature Model, we derived additional common and variable elements for the interface of multiple CMS and GFE. Considering the S.O.L.I.D principles, we designed the final architecture. The proposed IFF Interface SW, based on the standard architecture, is expected to enhance management efficiency through a common architecture, increase code reusability and scalability, and reduce development costs by shortening reliability testing times.

• Journal of KIISE
• /
• v.43 no.4
• /
• pp.460-469
• /
• 2016

Internet of Things (IoT) is an environment where various devices are connected to each other via a wired/wireless network and where the devices gather, process, exchange, and share information. Some of the most important types of IoT devices are mobile IoT devices such as smartphones. These devices provide various high-performance services to users but cannot be supplied with power all the time; therefore, power management appropriate to a given IoT environment is necessary. Power management of mobile IoT devices involves complex relationships between various entities such as application processors (APs), HW modules inside/outside AP, Operating System (OS), platforms, and applications; a method is therefore needed to systematically analyze and manage these relationships. In addition, variabilities related to power management such as various policies, operational environments, and algorithms need to be analyzed and applied to power management development. In this paper, engineering principles and a method based on them are presented in order to address these challenges and support systematic development of IoT device power management. Power management of connected helmet systems was used to validate the feasibility of the proposed method.