The Software Product Line (SPL) is an emerging methodology for developing software products. SPL has two main processes, the domain-engineering process and the application-engineering process. Collecting software assets regarding a specific business area is a domain-engineering consciousness. The process of presenting the software assets (in domain engineering) is called variability modelling. The principal objective of application-engineering is to configure a successful specific software product from the domain-engineering process by managing SPL assets using variability modelling technique.
    Hence, the main challenge in domain engineering is the representation of software artifacts and the dependency constraint relations between them while the main challenge in application engineering is the configuration of a correct software product. To ensure the correctness of the generated software product from application engineering, user or developer should evolve in the process. Therefore, the applicable and suitable model of SPL should handle these two challenges in addition to supporting Visualization.
    Historically SPL has been delivered from the Feature Model (FM) [1] which is formally considered as the first modeling of SPL. Later, new models have been suggested for modeling SPL. For instance, Orthogonal Variability Model (OVM), [2], Unified modeling Language (UML) [3], FM-OVM [4], [5], Domain specific language (DSL) [6], and Extensible Mark-up Language (XML) [7]. On the other hand, in the literature, many models have been used for reasoning SPL such as production and predicate logic, and Constraint Satisfaction Problem (CSP). Although the first step of using these methods is modelling SPL in suitable numerical or logical format, still these methods cannot be counted as modelling techniques as it used only for specific reasons.
    As a conclusion, the successful SPL modeling technique should be able to:
    * Represent all software artifacts in the domain engineering;
    * Provide an interactivity during the configuration process;
    * Providing reasoning tool for auto-validation, auto-verification, or analysis of SPL.
    * Have an ability of extending. Developing SPL is dynamic, and continuous process where new software                  artifacts might be added from time to time.
    * Have an ability to represent the lifecycle of SPL: design, implementation, and testing.
    * Have standard and documented notations.
    * Supporting Visualization
    Selecting the suitable modeling technique is the most important and first decision that should be considered when there is a plan for developing SPL. Nowadays, in both academic and industry, there are many working SPL models that could support one or more of the successful modeling criteria. And according to the best of our knowledge, still there is a critical need for finding one model that can achieve all issues of successful modeling criteria in SPL community.