• KIPS Transactions on Software and Data Engineering
• /
• v.10 no.6
• /
• pp.201-210
• /
• 2021

Navigation Software for the various weapon systems has common functionalities which give the possibility of common use among them. SPL(Software Product Line) framework of the navigation software for weapon system refers to developing a standardized navigation software platform from common functionalities of navigation software, managing the standardized navigation software platform, and developing weapon system navigation software such as navigation software for missile, UAV(Unmanned Air Vehicle), submarine, and etc. from the standardized navigation software platform. In this paper, we propose SPL based navigation software development process, Integrated Development Environment and operational concept of SPL framework. The operational concept will be defined by specifying the role of every stake holders and their activity scenario. The Operational concept would be referenced to implement SPL for other domain through using with detail implementation guide.

• 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.4 no.11
• /
• pp.487-498
• /
• 2015

Traceability enables software developers to trace up the changes occurring in software artifacts. In software product line, traceability is more complex than traceability in a single product as commonality and variability should be considered. Modeling traceability between features and requirements has been proposed in the past. However, traceability between requirements and architecture has more factors to consider, including many-to-many mappings and hierarchical structure of architectures. This paper proposes a method of systematically constructing platform traceability between platform requirements and platform architecture. This paper also shows the efficacy of the proposed mechanism through case studies.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.14 no.3
• /
• pp.105-110
• /
• 2014

Feature-oriented software product line engineering is to develop various products by developing product line core assets in terms of features and composing those features. However, the developed product may not behave correctly if the feature interaction problem has not be properly taken into account during the feature composition. This paper proposes techniques for identifying and modularizing undesirable feature interactions effectively. The scientific calculator product line is used for evaluating the applicability of the proposed method.

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

• Journal of KIISE:Software and Applications
• /
• v.41 no.7
• /
• pp.469-480
• /
• 2014

Software Product Line (SPL) is a software development paradigm that guarantees high productivity, reduced cost, and shorter time-to-market by systematically planning and reusing commonality and variability. In order to maximize the benefits of SPL engineering, testing should be integrated into the SPL engineering lifecycle processes that consist of domain engineering and application engineering and should be performed with as little test efforts as possible. This paper proposes a systematic software product line test cases derivation method using combinatorial test design. By applying combinatorial test design to product line test cases derivation and exploiting commonality between products at the same time, the number of generated test cases is dramatically reduced with the result that they can be effectively reused by the products of the given product line. Case studies conducted in this paper show the efficacy of our method compared with other methods that use only commonality or combinatorial design or neither of them in terms of the number of derived test cases.

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

Software product line engineering is an approach to creating core assets by systematically exploits common that can be highly reusableand different characteristics in related system families that is domain. By adapting this approachin object and component paradigm, software productivity is extended. Recently, Software development paradigm is changed to service oriented paradigm which is using services that are core assets. Therefore, to develop service oriented software more flexible, systematic and to enhance business agility about business changes, we need adaptation of product line to creation of services that are core assets. In this paper, we propose an approach to create and specify domain service through combine of product line and service oriented paradigm. Domain service explicitly specifies commonality and variability by domain service common/optional property variability, operation type variability, message type variability. By using this approach, it can support efficient and flexible service oriented development by producing various services through customization of domain service for the purpose.

• Journal of Information Technology Services
• /
• v.11 no.4
• /
• pp.295-308
• /
• 2012

Software and Systems Product Line(SSPL) is a paradigm that has been developed and applied by European Union(EU) to achieve the productivity and competitiveness of EU industries on the world market. It is not just a simple system or software development methodology, but a sophisticated technology requiring capabilities for a high level of mass customization, platforms, processes and convergence of software and systems. EU has applied SSPL for the five selected industrial sectors including aerospace, automobile, medical equipment, consumer electronics and telecommunication equipment since 1990s and led the way to other industry sectors to stimulate the application of SSPL from 2006. In order for Korea to secure competitiveness in the manufacturing and service industries in the competitive borderless market, it is essential to gain the high level of capabilities for software development and convergence of software and systems. SSPL can be a powerful means to achieve this end. This paper discusses the paradigmatic concept of SSPL, how EU's major industries and companies have secured competitiveness through SSPL, key capabilities that are necessary for successful institutionalization of SSPL in Korea, and finally suggestions on core strategies to materialize the benefits of SSPL for Korea.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.16 no.5
• /
• pp.1561-1583
• /
• 2022

Context: Testing is one of the techniques that can assure the quality of software including the domain of Software Product Line (SPL). Various techniques have been deliberated to enhance the quality of SPL including Model-based Testing (MBT). Objective: The objective of this study is to analyze and classify trends of MBT in SPL covering the solutions, issues and evaluation aspects by using taxonomy form. Method: A Systematic Literature Review (SLR) was conducted involving 63 primary studies from different sources. The selected studies were categorized based on their common characteristics. Results: Several findings can guide future research on MBT for SPL. The important finding is that the multiple measurements are still open to improving current metrics to evaluate test cases in MBT for SPL. The multiple types of measurement required a trade-off between maximization and minimization results to ensure the testing method which could satisfy multiple test criteria for example cost and effectiveness at the same time.

• The KIPS Transactions:PartD
• /
• v.14D no.7
• /
• pp.773-782
• /
• 2007

Software produce line engineering is a method that prepares for future reuse and supports seamless reuse in the application development process. Analyzing the commonality and variability between products in a product line is one of the essential concerns that must be considered when building a product line. In this paper, we suggest to combine a product line engineering approach with RFID applications technology. More concretely, common activities are identified among the RFID-enable applications and the variability in the common activities is analyzed in detail. Then, we suggest reusable product line architecture as a product line asset. In addition, as a tool for supporting this research, a framework which provides both reusable product line architecture for REID applications and the components that implement concrete realization of the architecture is developed. Sharing a common architecture and reusing assets to deploy recurrent services may be considered an advantage in terms of economic significance and overall quality.