Investigating the Safe Evolution of Software Product Lines

Laís Neves, Leopoldo Teixeira, Demóstenes Sena, Vander Alves, Uirá Kulesza and Paulo Borba

Abstract for GPCE'2011

The adoption of a product line strategy can bring significant productivity and time to market improvements. On the other hand, evolving a product line is risky because it might impact many products and their users. So, when evolving a product line to introduce new features or to improve its design, it is important to make sure that the behavior of existing products is not affected. In fact, to preserve the behavior of existing products one usually has to analyze different artifacts, like feature models, configuration knowledge and the product line assets. To better understand this process, in this paper we discover and analyze concrete product line evolution scenarios and, based on the results of this study, we describe a number of safe evolution transformation templates that developers can use when working with product lines. For each template, we show examples of their use in existing product lines. We evaluate the templates by also analyzing the evolution of two different product lines and demonstrating that they can express the corresponding modifications and then help to avoid the mistakes that we identified during our analyses. (PDF)

Safe Evolution Templates for GPCE'2011

• Template 1 - Split Asset

• Template 2 - Refactor Asset

• Template 3 - Add New Optional Feature

• Template 4 - Add New Mandatory Feature

• Template 5 - Replace Feature Expression

• Template 6 - Add New Alternative Feature

• Template 7 - Add New OR Feature

• Template 8 - Delete Asset

TaRGeT SPL Analyzed Releases

• Latest Version: https://targetspl.googlecode.com/svn/trunk/trunk

• Major Releases
  • Release 4.0 FM
  • Release 5.0 FM
  • Release 6.0 FM

• Minor Releases
  • Between Releases 4.0 and 5.0
    • Minor Release 1: http://targetspl.googlecode.com/svn/branches/target_fsf2_cnl_integrado_com_target4.0/
    • Minor Release 2: http://targetspl.googlecode.com/svn/branches/target_fsf2_cm_integrado_com_target4.0/
    • Minor Release 3: http://targetspl.googlecode.com/svn/branches/target_faa_cm_interruption/
    • Minor Release 4: http://targetspl.googlecode.com/svn/branches/target_fsf2-lmn3-pvcv_reuso_ufpe/
    • Minor Release 5: http://targetspl.googlecode.com/svn/branches/target_fsf2_cnl_intregrado_com_target4.0_e_interruption/
    • Minor Release 6: http://targetspl.googlecode.com/svn/branches/target_fsf2_tc3_e_tc4_spl/
    • Minor Release 7: http://targetspl.googlecode.com/svn/branches/target_fsf2_tc4_sem_spl/
    • Minor Release 8: http://targetspl.googlecode.com/svn/branches/target_mmr3_input_xml_doc_spl/
  • Between Releases 5.0 and 6.0
    • Minor Release 9: http://targetspl.googlecode.com/svn/branches/target_fsf2_onthefly/
    • Minor Release 10: http://targetspl.googlecode.com/svn/branches/target_mcms_xml_editor/

• TaRGeT safe evolution scenarios

• Some evolution scenarios are detailed here.

As we migrated the data from our SVN to a public one, the commit comments were lost. If you need the comments, you can send an email to lmn3 at cin.ufpe. br requesting them.

MobileMedia SPL Analyzed Releases

• http://mobilemedia-evolving-study.googlecode.com/svn/trunk/ (All releases)

• MobileMedia safe evolution scenarios

If you want to use the evolution scenarios data, please cite the following work: Lais Neves, Leopoldo Teixeira, Demóstenes Sena, Vander Alves, Uirá Kulesza, and Paulo Borba. Investigating the safe evolution of software product lines. In Proceedings of the 10th International Conference on Generative Programming and Component Engineering (GPCE 2011), Portlan, OR, USA, 2011. ACM.

-- LaisNeves - 25 Oct 2011 -- LaisNeves - 20 May 2011 -- LaisNeves - 01 Mar 2011