Implementation Issues in Product Line Scoping

Abstract

This is the unspecified version of the paper.This version of the publication may differ from the final published version.Permanent repository link: http://openaccess.city.ac.uk/257/ Link to published version: http://dx. ABSTRACTOften product line engineering is treated similar to the waterfall model in traditional software engineering, i.e., the different phases (scoping, analysis, architecting, implementation) are treated as if they could be clearly separated and would follow each other in an ordered fashion. However, in practice strong interactions between the individual phases become apparent. In particular, how implementation is done has a strong impact on economic aspects of the project and thus how to adequately plan it. Hence, assessing these relationships adequately in the beginning has a strong impact on performing a product line project right.In this paper we present a framework that helps in exactly this task. It captures on an abstract level the relationships between scoping information and implementation aspects and thus allows to quickly analyze implementation aspects of the project. We will also discuss the application of our framework to a specific industrial project.

Feature-oriented re-engineering using product line approach

“…Scoping is a key step in any product line. It determines actually which parts of the systems will be supported by reusable assets [2]. If there are too many assets supported among which some are with low priority currently, the resulting architecture would be much more complex which against the principle of focusing on simplification [6].…”

Product Lines for Digital Information Products

“…More details can be found in [BFK + 99, DS99, Sch03b, Sch04]. Other issues related to the implementation of scoping are discussed in [SG00].…”