• Journal of KIISE:Software and Applications
• /
• v.32 no.8
• /
• pp.717-729
• /
• 2005

Product Line Engineering (PLE) consists of two phases; Core Assets Development and Application Engineering. The core asset development is to model common features of members in a domain and to develop them. The application engineering is to effectively generate an application by instantiating the core asset. Today, PLE research mainly focuses on developing core assets, whereas activities and instructions for application engineering are weakly defined. Moreover, instructions of application engineering are not enough to be practically applied. To widely apply PLE to industry, researches on systematic and practical methods such as instantiation processes, instructions, and artifacts are needed. In this paper, we propose a practical PLE process, instructions, and artifacts about each activity. And then, we also present a case study to show applicability and practicality of the process proposed in this paper.

• Journal of Korean Institute of Industrial Engineers
• /
• v.40 no.4
• /
• pp.366-374
• /
• 2014

This study assessed and analysed a result of a product design experiment through Product Data Analytics (PDA), to find reasons for failure of some projects in the experiment. PDA is a computer-based data analysis that uses Product Data Management (PDM) databases as its operational databases. The study examines 20 product design projects in the experiment, which are prepared to follow same product development process by using an identical PDM system. The design result in the PDM database is assessed and analysed by On-Line Analytical Processing (OLAP) and data mining tools in PDA. The assesment and analysis reveals the lateness in creation of 3D CAD models as the main reason of the failure.

• Journal of KIISE:Software and Applications
• /
• v.32 no.4
• /
• pp.237-246
• /
• 2005

Product Line Engineering(PLE) is one of the technologies that develop applications economically reusing core assets. PLE consists of Framework Engineering(FE) and Application Engineering. Framework Engineering is to develop core assets that have common functionality shared by a set of family members. Application Engineering is to develop a specific application by instantiating the core assets. The PLE process increases reusability and efficiency because a specific application is developed by using core assets with less time and effort. Since definition of PLE artifacts and relationship between artifacts are not clear. developers have several troubles to make artifacts based on PLE process, are difficult to maintain consistency between artifacts, and do not use PLE process more practically. In this paper, we define meta-models of artifacts that are produced in PLE activities of PLE process and describe the traceability relationship between artifacts by using traceability map and guidelines that can apply traceability relationship. Finally, we define the way how trace links and guidelines of traceability map are applied.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.41 no.2
• /
• pp.159-166
• /
• 2018

The proliferation of information technologies made it possible to produce information products of different versions at much lower cost comparing to traditional physical products. Thus it is common for information product manufacturers to consider vertically differentiated product line for more profit through improved market coverage. Another salient characteristic of most information product is network externality. Existing researches dealing with vertical differentiation and network externality usually assumed oligopolistic market where vertically differentiated products are provided by competing companies, respectively. Moreover, they analyzed the essentially dynamic characteristic of network externality statically. In this study, different from the previous researches, the vertical differentiation strategy of a monopolistic company under network externality is dynamically analyzed. We used a two-period model to accommodate the dynamic feature of network externality. Based on the two-period model, the profit maximizing solutions are analyzed. The results showed that a monopolistic company has no incentive to differentiate products vertically when the network externality is absent. On the contrary, when the network externality exists, the monopolistic company can derive more profit by vertically differentiating the product line. It is also shown that, for more profit, the monopolistic company should keep the quality difference between the high quality product and the low quality product as greater as possible.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.14 no.2
• /
• pp.115-120
• /
• 2014

Many product line engineering methods use the feature model to structure commonality and variability among products in terms of features and to derive a product feature configuration, which is the set of features required for the development of a product. Features to be selected during product derivation are mainly determined based on the quality attributes required for a product. Most methods published so far derived an optimal product feature configuration through linear co-relationship between features and quality attributes. However, the co-relationship between features and quality attributes can be formulated as a non-linear function because of feature interactions. This paper proposes a method that derives an optimal product feature configuration considering feature interactions. Four product line cases are used to validate the proposed methods.

• Journal of Industrial Technology
• /
• v.3
• /
• pp.39-46
• /
• 1983

This paper presents a quantitative measure of the degree of part commonality and redundancy in a product line based on entropy measure of information theory. The several possible methods of analysis are discussed and the use of the entropy measure is discussed. These commonality and redundancy measure can be applied to analyze the usage pattern of part across a product line and to determine which parts have the broadest usage across the firm's product lines. An analysis of the results by entropy statistics is compared with the practical part usage in a simulation of several types of part usage's distributions.

• 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.16D no.1
• /
• pp.93-104
• /
• 2009

Modular implementation of a feature is a first step toward feature-oriented product line engineering, which develops and then utilizes core assets to configure products in terms of features. Aspect-oriented programming provides effective mechanisms for improving the modularity of feature implementations. However, as features in general are not independent of each other, changes in the implementation of one feature may cause changes to or side effects in the implementation of other features. Moreover, since the time at which a feature is incorporated into products, called feature binding time, may be various from compile time through load time to run time, a feature may have to be implemented differently depending on when the feature is bound into a product. To make each feature implementation module as independent as possible, this paper proposes aspectual implementation patterns that can effectively separate feature dependencies as well as feature binding time from feature implementation modules. These patterns enable flexible composition of feature implementation modules without affecting other modules according to feature selection. The approaches are demonstrated and evaluated based on a product line of scientific calculator applications.

• The Journal of the Korea institute of electronic communication sciences
• /
• v.18 no.5
• /
• pp.769-776
• /
• 2023

In this paper, we designed an MLSA(Match-line Sense Amplifier) for low-power CAM(Content Addressable Memory). By using the MLSA and precharge controller, we reduced power consumption during CAM operation by employing a selective match-line charging technique to mitigate power consumption caused by mismatch. Additionally, we further reduced power consumption due to leakage current by terminating precharge early when a mismatch occurs during the search operation. The designed circuit exhibited superior performance compared to the existing circuits, with a reduction of 6.92% and 23.30% in power consumption and propagation delay time, respectively. Moreover, it demonstrated a significant decrease of 29.92% and 52.31% in product-delay-product (PDP) and energy-delay-product (EDP). The proposed circuit was validated using SPECTRE simulation with TSMC 65nm CMOS process.

• Journal of KIISE:Software and Applications
• /
• v.33 no.2
• /
• pp.154-166
• /
• 2006

Product Line Engineering(PLE) is a software reuse paradigm that core assets are defined using common features in a domain and are instantiated in various applications. To apply the core asset effectively, variants which satisfy application requirements are extracted and the core asset should be also instantiated based on the variants. For the work, variability on architecture and components should be extracted exactly and an instantiation process and guidelines should be defined based on this variability In this paper, we define variability types depending on core assets elements and describe artifact templates related to tile variability. We also propose a systematic process which uses defined core assets including variability and verify practicability of the proposed process and variability expression through doing ease study. If utilizing with the proposed process in PLE, it can be feasible to model concrete core asset and variability and to utilize practical application engineering.