• Journal of Distribution Research
• /
• v.10 no.1
• /
• pp.59-84
• /
• 2005

Most of previous studies have proposed representative product categories which are likely to be sold on the on-line based only on the on-line benefits and risks. However, on-line shopping can be perceived another form of distribution channels from the perspectives of consumers. Therefore, in order to identify product categories which have a great potential to be sold on on-line stores, it is necessary to consider the perception and behavior at off-line shopping contexts as well as on on-line shopping circumstances. In this paper, we investigate the consumers' perception and behavior under both on-line and off-line shopping situations and classify them into several groups based on their perceptual and behavioral characteristics. Based on this classification, we empirically examine the product categories selling well on the on-line shopping. The empirical results show that there exist some patterns between distribution channels (on-line and off-line) and product categories. In addition, there are some differences among consumers regarding the perceptions and behaviors at on-line and off-line situations. Consumers who have high preference for on-line shopping tend to buy much wider product categories from on-line.

• KIPS Transactions on Software and Data Engineering
• /
• v.10 no.7
• /
• pp.251-256
• /
• 2021

Software Product Line Engineering (SPLE) has been known as an efficient and effective software reuse methodology. One of the key activities of SPLE is scoping analysis, which determines the range of the features to be developed as reusable assets. Although several scoping methods has been reported, they are not sufficient to apply them to the defense domain. In this paper, we present a scoping method applicable to the defense domain, and present a case study for applying SPLE to inertial navigation weapon system. At first, the proposed method determines the range of candidate features to be applied for the platform. The range is then adjusted from the perspective of product benefit. The final range of features is decided through considering the total cost of a product line. We will demonstrate and evaluate the applicability of the proposed method by showing how we can decide the scope of features to be engineered for the navigation software product line.

• Journal of Software Engineering Society
• /
• v.24 no.3
• /
• pp.77-89
• /
• 2011

Software product line engineering is a software reuse paradigm that helps organizations improve software productivity and quality by developing software products from reusable core assets. For the satisfaction of common and variable requirements among products in the product line, the core assets must be configurable according to the selection of variable features. Therefore, unlike software architecture model of a single product, product line architecture model must embed and express variabilities among the products. Many researches have proposed methods of embedding and expressing variabilities in the product line architecture models, but there are few comparative studies on the proposed methods. In this paper we discuss strong points and weak points of the proposed methods and compare expressiveness of the methods, which helps select a proper method.

• The KIPS Transactions:PartD
• /
• v.13D no.4 s.107
• /
• pp.583-592
• /
• 2006

Software development based on product lines has been proved a promising technology that can drastically reduce cycle time and guarantee quality by strategically reusing quality core assets that belong to an organization. However, how to measure within a product line is different from how to measure within a single software project in that we have to consider the aspects of both core assets and projects that utilize the assets. Moreover, the performance aspects of overall project lines need to be considered within a product line context. Therefore, a systematic approach to measure the performance of product lines is essential to have consistent, repeatable and effective measures within a product line. This paper presents a context-based measurements elicitation approach for product lines that reflects the performance characteristics of product lines and the diversity of their application. The approach includes both detailed procedures and work products resulting from implementation of the procedures, along with their templates. To show the utility of the approach, this paper presents the elicited measurements, especially for technical management practices among product line practices. This paper also illustrated a real application case that adopt this approach. The systematic approach enables management attributes, i.e., measurements to be identified when we construct product lines or develop software product based on the product lines. The measurements will be effective in that they are derived in consideration of the application context and interests of stakeholders.

• Journal of KIISE:Software and Applications
• /
• v.33 no.12
• /
• pp.1008-1021
• /
• 2006

Product line engineering(PLE) is one of the recent and effective reuse approaches that enables developing a number of applications by instantiating a core asset. Elements of a core asset are product line architecture(PLA), component, and decision model. Among these elements, PLA is the key element since it defines the overall structure of the core asset. Although numerous PLE methodologies have been introduced, it is still unclear what should be the elements of a PLA and how to systematically instantiate it for specific applications. Formal specifications can play a key role in defining detailed and precise instantiation process. In this paper, we first present a meta model of PLA and show how to specify PLA in a formal language, Object-Z. Then, we propose instantiation rules using formal specification and those rules precisely define constraints for instantiating PLA. By applying the proposed formal specification, we believe PLA instantiation can be carried out precisely and correctly, yielding high quality software development.

• Journal of KIISE:Software and Applications
• /
• v.33 no.5
• /
• pp.449-459
• /
• 2006

Product Line Engineering (PLE) has been widely accepted as a representative software reuse methodology by using core assets. As a key element of core assets, product line architecture (PLA) should be generic to a set of applications in the product line (PL). However, the difference between PLA and single system architecture has not been treated well enough, so evaluating PLA still remains as one of the difficult tasks in PLE. In this paper, we identify two intrinsic but overlooked issues in PLA; variability propagation chain and conflicts between architectural elements. And, we present a metric-based methodto evaluate PLA from the perspective of the two issues. We believe that the two issues in PLA and the evaluation method would make designing high-quality PLA more feasible and effective.

• 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 KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1010-1026
• /
• 2004

The goal of product line engineering is to support the systematic development of a set of similar software systems by understanding and controlling their common and distinguishing characteristics. The product line engineering is a process that develops reusable core assets and develops a set of software-intensive systems from a common set of core assets in a prescribed way. Currently, many software development technologies are accomplished in context of product line. However, much of the product line engineering research have focused on the reuse of work products relating to the software's architecture, detail design, and code. The product lines fulfill the promise of tailor-made systems built specifically for the needs of particular customers or customer groups. In particular, commonality and variability play central roles in the all product line development processes. These must be treated already during the requirement analysis phase. Requirements in product line engineering are basis of software development just like as traditional system development engineering, and basis of deciding other core assets' property - commonalities and variabilities. However, it is difficult to elicit, analyze and manage correct requirements. Therefore, it is necessary to develop systematic methods which can develop and manage requirement as core asset, which can be stable in anticipative change and can be well adapted to unpredictable change. In this paper, we suggest a method of managing requirements as core asset in product line. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity can be increased.

• Journal of the Korean Home Economics Association
• /
• v.40 no.10
• /
• pp.113-121
• /
• 2002

The purpose of this study was to investigate the effect of the depth of fashion product line on sales. The depth of the fashion product line was defined as the variety of style, color, and size in the outwear line for this study. Data were collected from the 98 brands in 4 department stores located in Seoul and Pusan. The result showed the significant impact of the variety of the outwear style on sales. Even after controlling the effect of advertising and the level of price in each brand, significant effect of the variety of outwear style were noticed on sales.

• Proceedings of the Korea Society of Design Studies Conference
• /
• 2001.10a
• /
• pp.61.2-61
• /
• 2001