With current trends towards moving variability from hardware to software, and given the increasing desire to postpone design decisions as much as is economically feasible, managing the variability from requirements elicitation to implementation is becoming a primary business requirement in the product line process. Nowadays, a medium size software system may encompass hundreds if not thousands of variability points introducing a new level of complexity that current techniques struggle to manage. In this paper, we present a new approach to variability management by introducing a multiple views model (4VM) where each view caters for specific set of concerns that relate to a particular group of stakeholders.
Rabih Bashroush, Ivor T. A. Spence, Peter Kilpatri