Dataset for the paper: Managing Systems Evolving in Space and Time: Four Challenges for Maintenance, Evolution and Composition of Variants

The dataset contains ground truth variants and their configurations for all scenarios described in the paper: Managing Systems Evolving in Space and Time: Four Challenges for Maintenance, Evolution and Composition of Variants.

The ground truth variants for feature location and composition of variants with features is in the folder named by <systemName>_Variants_With_Features.rar

The ground truth for feature revision location and composition of variants with feature revisions is in the folder named by <systemName>_Variants_With_Feature_Revisions.rar

The additional scenario is in the folder named by LibSSH_Variants_With_Feature_Revisions_ExtraScenario.rar

For every scenario use as input variants the variants inside a folder named by inputConfigurations.

For every scenario use as ground truth variants of new configurations the variants inside a folder named by newConfigurations.

The scenarios for feature location are split according to the number of variants, therefore the first scenario, for example, has the first variant of the file named by Inputconfigurations.csv. The second scenario must have the first variant + the second variant of the file named by Inputconfigurations.csv. The third scenario must have the first three variants of the file named by Inputconfigurations.csv, and so on, according to the Table 1 in the paper.

Regarding composing new configurations with features, use the new configurations in the file Newconfigurations.csv or NewConfigurations.txt and as ground truth variants the variants in the folder newConfigurations.

The scenarios for feature revision location are split according to the number of Git commits, therefore the first scenario, for example, has all the variants of the first Git commit in the file named by inputConfigurations.csv. The second scenario must have all the variants from the first 5 Git commits in the file named by inputConfigurations.csv, and so on, according to the Table 2 in the paper. Note: For every line of the file inputConfigurations.csv, the first column represents the number of a Git commit, the second column contains the hash of a Git commit and the following columns contain the feature revisions of a configuration.

Regarding composing new configurations with feature revisions, use the new configurations in the file newConfigurations.csv and as ground truth variants the variants in the folder newConfigurations.