• 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 KIISE:Software and Applications
• /
• v.33 no.7
• /
• pp.589-604
• /
• 2006

Software product lines (SPL) are recently an emerging software reuse paradigm, which helps organizations develop their products from reusable core assets rather than from scratch. For developing these assets, understanding commonality and variability (C&V) is essential. A feature-oriented approach has been used extensively for C&V analysis in the SPL. However, this contains no proposal to systematically identify features and provide the rationale for the features. Further, the approach does not directly show how the results of C&V analysis will satisfy an organization's high-level business goals and provide the rationale for the C&V. Therefore, this paper presents a domain analysis method for the SPL based on goals, scenarios, and features in order to overcome some of the deficiencies and limitations of the feature-oriented approach. In particular, the paper proposes a domain requirements model (DRM) and a domain requirements modeling method based on the DRM. This method has been applied to the home integration system (HIS) domain to demonstrate its feasibility with a supporting tool, namely IDEAS. Our approach makes it possible to systematically identify the features and provide the rationale for both the features and the C&V.