Abstract : Nowadays, adopting software product line (SPL) development approach becomes a successful strategic decision in software development since the rapid time to market necessity is guaranteed by SPLs due to assets reusability [1,2]. However, the expansion of the market segment implies a boost of user's requirements that should be satisfied by quickly developing new products . Thus, an agile evolution of SPLs becomes a necessity. The general purpose of a SPL is the automated construction of a new product based on the reusability of existing features . A feature is a characteristic defined by the domain experts  that abstracts a set of software-related resources called assets. Thus, a feature model (FM) represents all the products of the SPL and permits capturing products commonalities and variability . To generate a new product, a user selects a set of features via a process called configuration by respecting the constraints defined in the FM . Despite that SPLs permit reusability, generating a new product that uses features related to different products is not supported by a classic FM . In other words, if two products í µí± 1 and í µí± 2 leaded respectively to the injection of the features í µí°¹ 1 and í µí°¹ 2 in the í µí°¹í µí±, the latter does not support the generation of a new product í µí± 3 that uses both í µí°¹ 1 and í µí°¹ 2 since they refer to different products. However, in our desired approach we want to design evolved í µí°¹í µí±í µí± that make the previous operation feasible. In addition, to benefit from a valuable reusability, we are interested in focusing on the fact that a product can be constructed from a subset of the SPLs' features – regardless of referring to one or many products, or from a set of features that some of them are not part of the SPL. Thus, we should identify the features that are not part of the SPL once requested, connect them – if required – to the existing features that we still need from the SPL and integrate them in the SPL to be able to use them later. On the other hand, it is necessary to guarantee an agile evolution of the SPL, thus our approach should adopt mechanisms that automate as much as possible the software development process, minimize its overhead and simplify its complexity.