Cross-checking disambiguated product line variability models

Many industry sectors face the challenge of how to sat-isfy the increasing demand for individualized software sys-tems and software-intensive systems. The software product line (PL) engineering paradigm (SPLE, see [5]) has proven to empower organizations to develop a diversity of similar systems at lower cost, in shorter time, and with higher qual-ity compared to single system development [5]. Key to SPLE is to exploit the commonalities of the sys-tems that belong to the PL and to handle the variability (i.e., the differences) between those systems. Commonalities are properties and qualities that are shared by all systems of the PL [1]; e.g., all mobile phones let users make calls. In SPLE, two kinds of variability can be distinguished: Software variability and PL variability. Software variability refers to the “ability of a softwar