Tricks and traps of initiating a product line concept in existing products

Many industries are hampered with introducing the product line concept into already existing products. Though appealing, the concept is very difficult to introduce specifically into a legacy environment. All too often the impacts and risks are not considered adequately. This article describes the introduction of a product line approach in Alcatel's S12 Voice Switching System Business Unit. Practical impacts during the introduction are described as well as tricks and traps. The article not only summarizes the key software engineering principles, but also provides empirical evidence and practical techniques on which to build.

[1]  David M. Weiss,et al.  Software Product Line Engineering , 2005, SEKE.

[2]  Christof Ebert,et al.  Improving Validation Activities in a Global Software Development , 2000, IWSM.

[3]  Karen Southwick,et al.  Making the Cisco Connection: The Story Behind the Real Internet Superpower , 2000 .

[4]  Harvey P. Siy,et al.  Parallel changes in large scale software development: an observational case study , 1998, TSEM.

[5]  Jan Bosch,et al.  Software product lines: organizational alternatives , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[6]  Even-André Karlsson,et al.  Daily build and feature development in large distributed projects , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[7]  Steve McConnell,et al.  Software Project Survival Guide , 1997 .

[8]  Juha Kuusela,et al.  Requirements engineering for product families , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[9]  David M. Weiss,et al.  Software Product-Line Engineering: A Family-Based Software Development Process , 1999 .

[10]  Klaus Schmid,et al.  Applying Product Line Concepts in Small and Medium-Sized Companies , 2000, IEEE Software.