Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Dataset . 2021
License: CC BY
Data sources: Datacite
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Dataset . 2021
License: CC BY
Data sources: ZENODO
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Dataset . 2021
License: CC BY
Data sources: Datacite
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Dataset . 2021
License: CC BY
Data sources: Datacite
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Dataset . 2021
License: CC BY
Data sources: ZENODO
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Dataset . 2021
License: CC BY
Data sources: Datacite
versions View all 4 versions
addClaim

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

Authors: Michelon, Gabriela Karoline; Obermann, David; Assunção, Wesley K. G.; Linsbauer, Lukas; Grünbacher, Paul; Egyed, Alexander;

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

Abstract

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.

Keywords

software product line, feature location, repository mining, benchmark extractor, feature revision

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
    OpenAIRE UsageCounts
    Usage byUsageCounts
    visibility views 8
    download downloads 7
  • 8
    views
    7
    downloads
    Powered byOpenAIRE UsageCounts
Powered by OpenAIRE graph
Found an issue? Give us feedback
visibility
download
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
views
OpenAIRE UsageCountsViews provided by UsageCounts
downloads
OpenAIRE UsageCountsDownloads provided by UsageCounts
0
Average
Average
Average
8
7