Software product line testing: A feature oriented approach

Software Product Lines (SPLs) are not intended to create one application, but a number of them: a product family. In contrast to one-off development, SPLs are based on the idea that the distinct products of the family share a significant amount of assets. This forces a change in how software is developed. Likewise, software testing should mimic its code counterpart: product testing should also be produced out of a common set of assets. Specifically, this paper addresses how model-driven testing, used for one-off development, can be moved to an SPL setting. We focus on feature-oriented software development as the SPL realization technique. UML sequence diagrams are used to represent the common and feature scenarios. This models are transformed through model transformations to obtain test cases that conform to the UML Testing Profile.

[1]  Danilo Caivano,et al.  Model-driven Testing - Transformations from Test Models to Test Code , 2011, ENASE.

[2]  Sven Apel,et al.  Model Superimposition in Software Product Lines , 2009, ICMT@TOOLS.

[3]  José Manuel Marqués Corral,et al.  Seamless development of software product lines , 2007, GPCE '07.

[4]  Paul Clements,et al.  Software product lines - practices and patterns , 2001, SEI series in software engineering.

[5]  Per Runeson,et al.  Software product line testing - A systematic mapping study , 2011, Inf. Softw. Technol..

[6]  Oscar Díaz,et al.  Feature Oriented Model Driven Development: A Case Study for Portlets , 2007, 29th International Conference on Software Engineering (ICSE'07).

[7]  Sarfraz Khurshid,et al.  Incremental Test Generation for Software Product Lines , 2010, IEEE Transactions on Software Engineering.

[8]  Jean-Marc Jézéquel,et al.  Model driven design and aspect weaving , 2008, Software & Systems Modeling.

[9]  Don S. Batory,et al.  Scaling step-wise refinement , 2004, IEEE Transactions on Software Engineering.

[10]  Beatriz Pérez Lamancha,et al.  Automated model-based testing using the UML testing profile and QVT , 2009, MoDeVVa '09.

[11]  Iris Groher,et al.  Product Line Implementation using Aspect-Oriented and Model-Driven Software Development , 2007 .

[12]  Ina Schaefer,et al.  Variability Modelling for Model-Driven Development of Software Product Lines , 2010, VaMoS.

[13]  Myungchul Kim,et al.  Towards a Formal Framework for Product Line Test Development , 2007, 7th IEEE International Conference on Computer and Information Technology (CIT 2007).

[14]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[15]  Maider Azanza Sesé,et al.  Model driven product line engineering : core asset and process implications , 2011 .

[16]  Jean Bézivin,et al.  A Canonical Scheme for Model Composition , 2006, ECMDA-FA.

[17]  Klaus Pohl,et al.  Model-Based System Testing of Software Product Families , 2005, CAiSE.

[18]  Don Batory,et al.  Scaling Step-Wise Refinement , 2004, IEEE Trans. Software Eng..

[19]  Clémentine Nebut,et al.  Automated requirements-based generation of test cases for product families , 2003, 18th IEEE International Conference on Automated Software Engineering, 2003. Proceedings..

[20]  Oscar Díaz,et al.  Domain-Specific Composition of Model Deltas , 2010, ICMT@TOOLS.

[21]  John D. McGregor,et al.  A systematic mapping study of software product lines testing , 2011, Inf. Softw. Technol..

[22]  Antonia Bertolino,et al.  Use case-based testing of product lines , 2003, ESEC/FSE-11.

[23]  Mario Piattini,et al.  Software Product Line Testing - A Systematic Review , 2009, ICSOFT.

[24]  James E. Rumbaugh,et al.  Unified Modeling Language (UML) , 2010, Encyclopedia of Software Engineering.