Configuration Generation

#Configuration Generation This page explains how the configurations are generated to test the transformation depending on the framed features. This solution is a simplified method inspired by [1]. It uses requirements that can be seen in the table Requirements below. The requirements are tied to a configuration of its dependant feature. Features on which the require dont depend are not shown in the table. An algorithm goes through a list of the requirements and constructs complete configurations of requirements that dont contradict each other. This is done until every requirement is used once. The algorithm uses a set of a reduced number of features. This list can be seen in the table Reduced feature list.

##Reduced feature list

Number	Feature
0
0
0

Role_Properties, Role_Behavior
config[1] = Role_Inheritance
config[2] = Compartments
config[3] = Dates
config[4] = Role_Implication
config[5] = Role_Prohibtion
config[6] = Role_Equivalence
config[7] = Group_Constraints
config[8] = Occurence_Constraints
config[9] = Relationship
config[10] = Relationship_Cardinality
config[11] = Intra_Relationship_Constraints
config[12] = Inter_Relationship_Constraints
config[13] = Compartment_Types
config[14] = Compartment_Properties, Compartment_Behavior
config[15] = Compartment_Inheritance
config[16] = Playable_By_Defining_Compartment
config[17] = Data_Types
config[18] = Data_Type_Inheritance

##Requirements

Requirement	Description	Dependat Configuration
R1	Role properties and operation are transformed

[1] K.D. Scheidemann, Optimizing the selection of representative configurations in verification of evolving product lines of distributed embedded systems, in: Proceedings of the 10th International Software Product Line Conference (SPLC’06), 2006, pp. 75–84.