Evolution in multiple-view models of software product families

Based on a survey of domain engineering methods, current approaches address the evolution of software product families in an ad hoc way. There is no multiple-view modeling approach that addresses the evolution of software product families in a systematic and consistent way. Hence, it is necessary to be able to evolve a multiple-view model such that the different views, within the same life cycle phase or in different phases, remain consistent with each other.; In order to solve this problem, this research develops a multiple-view modeling approach for consistently evolving multiple views of software product families. The multiple-view modeling approach addresses evolution points, which are locations where changes in each view can take place. Each view of a multiple-view model evolves through its evolution points by considering its relationships with other views. The relationships among multiple views are defined in a multiple-view meta-model for software product families. The meta-model describes how each meta-class in a view relates semantically to meta-classes in other views. Consistency checking and mapping rules are derived from the semantic relationships between multiple views in the meta-model. They focus on resolving inconsistencies between multiple views in the same phase or other phases, and on mapping between multiple views in the different phases. In addition, based on the meta-model, the impact of evolutionary change is analyzed to determine what impact a change made in a view has on other meta-classes within this view, on other views in the same phase, and on other phases.; A proof-of-concept prototype, the Product Line UML. Based Software Engineering Environment (PLUSEE), is also developed to demonstrate consistency checking and mapping between multiple views of software product families. This prototype addresses both domain engineering and target system configuration. Using the PLUSEE, this research is validated through case studies of a factory automation product family and an electronic commerce product family.; In addition, this research applies the multiple-view modeling approach to model security requirements for software product families to show how the approach works with a security extension. The security requirements are captured in security use cases and encapsulated in security objects, which are separated from non-secure application requirements. The security use cases and objects are reused in other software product families.