• Journal of Software Engineering Society
• /
• v.26 no.2
• /
• pp.31-44
• /
• 2013

Software product line (SPL) engineering is a reuse paradigm that helps organizations increase productivity and improve product quality by developing product from reusable core assets. In SPL, product configuration is the process of selecting the desired features and feature attributes for a given product from a feature model. In order to develop a successful product, feature and feature attribute selection that can achieve the product goal is important. There can be thousands of features and feature attributes resulting in myriads of configurations and finding the best configuration efficiently is a hard task. This paper proposes a systematic process for feature-based product configuration. To support development of a product that satisfys all product goals(business goals and quality goals), a model showing how feature and feature attribute combinations are related to product goals is included and a method for deriving an optimal product configuration using the model is proposed.

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

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2017.01a
• /
• pp.79-82
• /
• 2017

IoT devices are interconnected in global network with different functionalities and manage the data transfer in cloud computing. IoT devices can be used anytime, anywhere with any device with different applications and protocols. Same devices but different applications according to end user requirements such as sensors and Wi-Fi devices, reusability of these applications can enhance the development process. However, large number of variations in cloud computing make it difficult the features selection in application because of compatibility issues of devices. In this paper we have proposed multi-Software Product Lines (multi-SPLs) approach to manage the variabilities and commonalities of IoT applications and protocols. Feature modeling is used to manage the commonalities and variabilities of SPL. We proposed that multi-SPLs feature model is more appropriate for modeling of IoT applications and protocols.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.51-60
• /
• 2006

Product Line Engineering(PLE) is an effective software development technique which produces applications using core assets. Because of reusing the core assets, PLE can save cost for developing products in a domain but increase reusability. There are about ten PLE methodologies available, but there are not yet common agreements on PLE process and artifacts. This makes developers harder to choose a methodology and to apply it in practice. A comprehensive technical evaluation and comparison on existing PLE methodologies would be essential for practitioners. In this paper, we present a technical assessment of representative PLE methodologies; FAST, SEI SPL, PuLSE, Bosch's PL proceis, FOPLE, ESAPS, KobrA/PoLITe, Alexandria, COPA, QADA. They are compared in the criteria of process, artifacts, instructions, and special features. And we identify common or variable elements between methodologies and confirm elements to be improved in each PLE methodology. The assessment result would be well utilized in defining a practical methodology for PLE projects and in choosing an appropriate methodology among available ones.

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

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.15 no.7
• /
• pp.2455-2475
• /
• 2021

Patient Navigation Program (PNP) is considered as an important implementation of health care systems that can assist in patient's treatment. Due to the feasibility of PNP implementation, a systematic reuse is needed for a wide adoption of PNP computerized system. SPL is one of the promising systematic reuse approaches for creating a reusable architecture to enabled reuse in several similar applications of PNP systems which has its own variations with other applications. However, stakeholder decision making which result from the imprecise, uncertain, and subjective nature of architecture selection based on quality attributes (QA) further hinders the development of the product line architecture. Therefore, this study aims to propose a quality-driven approach using Multi-Criteria Decision Analysis (MCDA) techniques for Software Product Line Architecture (SPLA) to have an objective selection based on the QA of stakeholders in the domain of PNP. There are two steps proposed to this approach. First, a clear representation of quality is proposed by extending feature model (FM) with QA feature to determine the QA in the early phase of architecture selection. Second, MCDA techniques were applied for architecture selection based on objective preference for certain QA in the domain of PNP. The result of the proposed approach is the implementation of the PNP system with SPLA that had been selected using MCDA techniques. Evaluation for the approach is done by checking the approach's applicability in a case study and stakeholder validation. Evaluation on ease of use and usefulness of the approach with selected stakeholders have shown positive responses. The evaluation results proved that the proposed approach assisted in the implementation of PNP systems.