• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.47-59
• /
• 2005

S/W product line is a S/W product or a set of S/W system, which has common functions. We can develop a specific S/W product, which satisfiesrequirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed S/W architecture through the S/W product line. S/W development methodology based on the S/W product line can develop a S/W more easily and fast by reusing the developed S/W core asset. An advanced country of S/W technology selects S/W product line as a core field of S/W production technology, and support technology development. In case of USA, CMU/SEI (Carnegie Mellon University / Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Ministry of National Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. In this paper, we aim to construct reference architecture of S/W product line for production of the S/W product line.

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.155-168
• /
• 2006

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

• The KIPS Transactions:PartD
• /
• v.15D no.6
• /
• pp.803-814
• /
• 2008

Product line architectures include variable parts to be selected according to product specific requirements. In order to derive architectures that are valid for a particular product from product line architectures, variabilities of product line architectures must be systematically managed. In this paper, we adopt an approach to variability management of product line architectures through an explicit mapping between a feature model and product line architecture models. If this mapping is incorrect or there exists inconsistency among product line architectural elements, variabilities of product line architectures cannot be managed correctly. Therefore, this paper formally defines product line architectural models in terms of conceptual, process, deployment, and module views, and mapping relationships between the feature model and the architectural models. Consistency rules for correct variability management of product line architectures are defined in terms of consistency in each of product line architecture model, consistency between different architectural view models, and consistency between a feature model and product line architectural models. These consistency rules provide a theoretical foundation for deriving valid product architecture from product line architectures.

• The Research Journal of the Costume Culture
• /
• v.19 no.3
• /
• pp.650-660
• /
• 2011

Purpose of this study is to explore: 1) the difference in color sensibility evaluation, color attractiveness, and attitude toward the product, 2) the difference in the effect of color sensibility evaluation on color attractiveness, and 3) the difference in the effect of color sensibility evaluation on attitude toward the product between the identical clothing product presented in on-line and off-line settings. Experimental method was applied with 230 male and female university students using stimuli of an on-line site as well as an off-line window display presenting the same white t-shirts. Color sensibility factors of white t-shirt were hedonic, stimulating, active, and spatial senses. These color sensibility factors of the clothing product affected product color attractiveness as well as attitude toward the product. Although there were not differences in color sensibility evaluation, product attractiveness, and attitude toward the product between items presented in on-line and off-line settings, difference was found in the effect of color sensibility on the color attractiveness and attitude toward the product. The effect of color sensibility on color attractiveness and attitude toward the product was stronger in on-line than in off-line setting. Hedonic sense was the most important factor influencing attractiveness of product color and attitude toward the product. In addition, spatial sense affected attractiveness of product color in on-line setting; and stimulating sense impacted attitude toward the product in off-line setting. Based on the results implications were generated.

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

• Journal of Software Engineering Society
• /
• v.29 no.2
• /
• pp.1-6
• /
• 2020

Software product line development is a development paradigm that efficiently develops a product family by avoiding redundant development based on separation of the common part and the variable part of the product family. In software product line development, the source code that is used to produce a product family is called a product line code base, and when the product line code base is changed and the products of the product family are affected by the change, the activity of testing the affected products is called a product line regression testing. For product line regression testing, instead of conducting regression testing individually on each product of the product family, a more efficient regression testing would be possible if unnecessary testing that are irrelevant to the change can be avoided. This paper introduces SRTS, which is an automated method to efficiently perform software product line regression testing. SRTS divides the product line code base and test cases based on commonality and variability. Then SRTS identifies and selects the test cases affected by the change. Finally, it reduces unnecessary testing by rerunning only the selected test cases.

• Industrial Engineering and Management Systems
• /
• v.8 no.1
• /
• pp.47-53
• /
• 2009

We define product line (or mix) selection problem as selecting a subset of potential product variants that can simultaneously minimize product proliferation and maintain market coverage. Selecting the most efficient product mix is a complex problem, which requires analyses of multiple criteria. This paper proposes a method based on Data Envelopment Analysis (DEA) for product line selection. Data Envelopment Analysis (DEA) is a linear programming based technique commonly used for measuring the relative performance of a group of decision making units with multiple inputs and outputs. Although DEA has been proved to be an effective evaluation tool in many fields, it has not been applied to solve the product line selection problem. In this study, we construct a five-step method that systematically adopts DEA to solve a product line selection problem. We then apply the proposed method to an existing line of staplers to provide quantitative evidence for managers to generate desirable decisions to maximize the company profits while also fulfilling market demands.

• Journal of KIISE:Software and Applications
• /
• v.33 no.3
• /
• pp.289-300
• /
• 2006

Product line is nowadays well known as a representative method for reuse. In the product line, important assets are components. Although enough concerns were given of the product line, it was not accomplished to structure and specify a product-line component with variability. This paper presents an approach to specify components in the product line. The approach describes the static and dynamic structure of a product-line component and explains the behavior and concurrency of the component. The component information is separately described in the black-box and white-box using the Feature-Oriented Reuse Method(FORM). This research also formalizes the data on a component specification in the form of BNF. The specification is described through careful consideration for many different characteristics of the product-line component, so this paper helps to easily develop the components in the product line and to well comprehend how to apply a method for the product line.

• Journal of the Korean Society of Clothing and Textiles
• /
• v.35 no.6
• /
• pp.635-645
• /
• 2011

This study explores the differences in product evaluation and approach behaviors as well as the effects of product evaluation on approach behaviors of utilitarian and hedonic products in on-line and off-line settings. A total of 332 subjects participated in the experiments to assess product evaluation and approach behaviors for utilitarian and hedonic clothing products in on-line and off-line settings. The results show that even though the same stimulus was presented, consumers' product evaluation of utilitarian clothing (i.e., t-shirts) was higher in the off-line setting than in the on-line setting while the approach behavior of hedonic clothing was better in the on-line setting than in the off-line setting. In addition, color was a crucial factor generating positive approach behaviors for utilitarian clothing while style and quality were core factors influencing the approach behaviors of hedonic products in an on-line setting. There was no consistency in the results of the important factors affecting approach behaviors of utilitarian and hedonic clothing in an off-line setting. The conclusion suggests implications for marketing based upon the results of this study.

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