Detecting feature interactions in SPL requirements analysis models


The consequences of unwanted feature interactions in a Software Product Line (SPL) can range from minor problems to critical software failures. However, detecting feature interactions in reasonably complex model-based SPLs is a non-trivial task. This is due to the often large number of interdependent models that describe the SPL features and the lack of support for analyzing the relationships inside those models. We believe that the early detection of the points, where two or more features interact --- based on the models that describe the behavior of the features ---, is a starting point for the detection of conflicts and inconsistencies between features, and therefore, take an early corrective action. This vision paper foresees a process to find an initial set of points where it is likely to find potential feature interactions in model-based SPL requirements, by detecting: (i) dependency patterns between features using use case models; and (ii) overlapping between use case scenarios modeled using activity models. We focus on requirements models, which are special, since they do not contain many details about the structural components and the interactions between the higher-level abstraction modules of the system. Therefore, use cases and activity models are the means that help us to analyze the functionality of a complex system looking at it from a high level end-user view to anticipate the places where there are potential feature interactions. We illustrate the approach with a home automation SPL and then discuss about its applicability.

DOI: 10.1145/1629716.1629738

Extracted Key Phrases

10 Figures and Tables

Cite this paper

@inproceedings{Alfrez2009DetectingFI, title={Detecting feature interactions in SPL requirements analysis models}, author={Mauricio Alf{\'e}rez and Ana Moreira and Uir{\'a} Kulesza and Jo{\~a}o Ara{\'u}jo and Ricardo Mateus and Vasco Amaral}, booktitle={FOSD}, year={2009} }