Towards feature-driven planning of product-line evolution

ABSTRACT

Industries that successfully apply product line approaches often operate in markets that are well established and have a strategic perspective. Consequently, such organizations have a tendency towards long-term planning of products and product lines. Although there are numerous approaches for efficient product line engineering, there is surprisingly little support for a long-term, strategic perspective and an evolution of product lines. To address these challenges, we aim to integrate evolution into model-driven product line engineering. In particular, we explore how feature models can be applied to describe the evolution of product lines. The paper contributes (i) concepts for describing the evolution of product lines with feature models, (ii) a corresponding framework, which puts this into a bigger context and (iii) three scenarios that show how this framework can be applied. The concepts are motivated with examples from automotive software engineering and embedded systems, which are industries with a strong affinity to product lines, where long term planning of the product portfolio are common strategies.

REFERENCES

• 1: M. Alanen and I. Porres. Difference and union of models. In The Unified Modeling Language, Modeling Languages and Applications, 6th International Conference (UML 2003), pages 2--17, San Francisco, CA, USA, October 2003.
• 2: S. Apel, C. Kastner, and C. Lengauer. Featurehouse: Language-independent, automated software composition. In 31st International Conference on Software Engineering (ICSE '09), pages 221--231, Washington, DC, USA, 2009. IEEE Computer Society.
• 3: D. Batory, J. Sarvela, and A. Rauschmayer. Scaling step-wise refinement. IEEE Transactions on Software Engineering, 30:1278--1295, 2004.
• 4: P. Clements and L. M. Northrop. Software Product Lines: Practices and Patterns. The SEI series in software engineering. Addison-Wesley, Boston, MA, USA, 2002.
• 5: K. Czarnecki and U. W. Eisenecker. Generative Programming. Addison Wesley, Reading, MA, USA, 2000.
• 6: S. Deelstra, M. Sinnema, and J. Bosch. Product derivation in software product families: a case study. Journal of Systems and Software, 74(2):173--194, 2005.
• 7: G. Deng, G. Lenz, and D. C. Schmidt. Addressing domain evolution challenges in software product lines. In J.-M. Bruel, editor, MoDELS Satellite Events, volume 3844 of LNCS, pages 247--261. Springer, 2005.
• 8: D. Dhungana, T. Neumayer, P. Grunbacher, and R. Rabiser. Supporting evolution in model-based product line engineering. In 12th International Conference on Software Product Lines (SPLC 2008), pages 319--328, Limerick, Ireland, September 2008. IEEE Computer Society.
• 9: Eclipse-Foundation. ATL (ATLAS Transformation Language). http://www.eclipse.org/m2m/atl/.
• 10: Eclipse-Foundation. Xtext. http://www.eclipse.org/Xtext.
• 11: Eclipse Modeling Framework Technology (EMFT). EMF Compare. http://wiki.eclipse.org/index.php/EMF_Compare.
• 12: C. Kaestner, T. Thum, G. Saake, J. Feigenspan, T. Leich, F. Wielgorz, and S. Apel. FeatureIDE: A tool framework for feature-oriented software development. In ICSE '09: Proceedings of the 2009 IEEE 31st International Conference on Software Engineering, pages 611--614, Washington, DC, USA, 2009. IEEE Computer Society.
• 13: K. Kang, S. Cohen, J. Hess, W. Novak, and S. Peterson. Feature oriented domain analysis (FODA) feasibility study. SEI Technical Report CMU/SEI-90-TR-21, ADA 235785, Software Engineering Institute, 1990.
• 14: D. S. Kolovos. Establishing correspondences between models with the epsilon comparison language. In 5th European Conference on Model Driven Architecture - Foundations and Applications, pages 146--157, Enschede, The Netherlands, 2009.
• 15: N. Loughran, A. Rashid, W. Zhang, and S. Jarzabek. Supporting product line evolution with framed aspects. In AOSD ACP4IS Workshop, 2004.
• 16: T. Mens and T. D'Hondt. Automating support for software evolution in UML. Automated Software Engineering, 7(1):39--59, 2000.
• 17: D. Parnas. On the design and development of program families. IEEE Transactions on Software Engineering, SE-2(1):1--9, March 1976.
• 18: R. Phaal, C. J. P. Farrukh, and D. R. Probert. Technology roadmapping--a planning framework for evolution and revolution. Technological Forecasting and Social Change, 71(1--2):5--26, 2004.
• 19: S. Schach and A. Tomer. Development/maintenance/reuse: software evolution in product lines. In 1st Software Product Lines Conference (SPLC 2000), pages 437--450, Denver, Colorado, August 28--31 2000.
• 20: Software Engineering Institute. SPL Hall of Fame. Web site, 2008. http://splc.net/fame.html.
• 21: M. Svahnberg and J. Bosch. Evolution in software product lines: Two cases. Journal of Software Maintenance: Research and Practice, 11(6):391--422, 1999.
• 22: M. Voelter and I. Groher. Product line implementation using aspect-oriented and model-driven software development. In 11th International Software Product Line Conference (SPLC 2007), Kyoto, Japan, September 2007.
• 23: D. M. Weiss and C. T. R. Lai. Software Product Line Engineering: A Family-Based Software Development Process. Addison-Wesley, 1999.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.13 Reusable Software

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques

General Terms:
Algorithms, Design, Management

Keywords:
evolution, feature modeling, product line engineering