Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
4
datasets available to search
ShareScore release 0.9.0
Dataset results
4 results for “Software product line evolution”
Architectural Feature Re-Modularization for Software Product Line Evolution
<p>Extensive maintenance leads to the Software Product Line Architecture<br> (PLA) degradation over time. When there is the need of<br> evolving the Software Product Line (SPL) to include new features,<br> or move to a new platform, a degraded PLA requires considerable<br> effort to understand and modify, demanding expensive refactoring<br> activity. In the state of the art, search-based algorithms are used to<br> improve PLA at package level. However, recent studies have shown<br> that the most variability and implementation details of an SPL are<br> described in the level of classes. There is a gap between existing<br> approaches and existing practical needs. In this work, we extend<br> the current state of the art to deal with feature modularization in<br> the level of classes by introducing a new search operator and a set<br> of objective functions to deal with feature modularization in a finer<br> granularity of the architectural elements, namely at class level. We<br> evaluated the proposal in an exploratory study with a PLA widely<br> investigated and a real-world PLA. The results of quantitative and<br> qualitative analysis point out that our proposal provides solutions<br> to properly re-modularize features in a PLA, being preferred by<br> practitioners, in order to support the evolution of SPLs.</p>
Comparing the Intensity of Variability Changes in Software Product Line Evolution - Related Research Artifacts
<p>This archived open repository contains open science material related to the following submission to the <a href="https://www.journals.elsevier.com/journal-of-systems-and-software/call-for-papers/software-reuse-for-the-next-generation">Journal of Systems and Software (JSS) special issue <em>Software Reuse for the Next Generation</em></a>:</p> <p>C. Kröher, L. Gerling, K. Schmid, <em>Comparing the intensity of variability changes in software product line evolution</em>, Journal of Systems and Software. Submitted November 2022.</p> <p>The paper presents the application of a fine-grained, variability-centric analysis approach to four different software product lines: <a href="https://github.com/torvalds/linux">Linux kernel</a>, <a href="https://github.com/coreboot/coreboot">coreboot firmware</a>, <a href="https://github.com/mirror/busybox">BusyBox UNIX utilities</a>, and <a href="https://sourceforge.net/projects/axtls/">axTLS embedded SSL</a>. The approach is based on the differentiation between artifact-specific and variability information in code, build, and variability model artifacts to identify the intensity (the frequency and the amount) with which developers change variability information in practice.</p> <p>In order to complement the results presented in the submission and support reproducibility as well as reuse, the following artifacts are available:</p> <ul> <li><strong>JSS-VM_2022-11-01.zip</strong>: a compressed archive containing the virtual machine in which the analysis was executed. This virtual machine was created with <a href="https://www.vmware.com/content/vmware/vmware-published-sites/us/products/workstation-player/workstation-player-evaluation.html.html">VMware Workstation 16 Player</a> based on <a href="https://ubuntu.com/download/desktop">Ubuntu Desktop 22.04.1</a> (username and password: jss). It provides all installed software, configuration files, data sets, and results as described in the submission. Download, extract, and start the virtual machine to access the detailed description of its content and usage on the desktop.</li> <li><strong>ComAnI-Applications.zip</strong>: a compressed archive containing the technical realization of the analysis approach and the configuration files used to apply it to the individual software product lines. This includes: <ul> <li><em>ComAnI_Guide.pdf</em>: the guide explaining the application and its usage in general</li> <li><em>ComAnI.jar</em>: the Java executable archive file representing the main application for starting an analysis</li> <li><em>ComAnI-PS.jar</em>: a modified version of the previous Java executable archive file, which provides the number of code, build, and variability model artifacts as specified by the regular expressions of a given configuration file as well as their total number of lines based on the current state of a repository only (no history)</li> <li><em>DeadCodeChangeAnalyzer.jar</em>: a commit analyzer plug-in for detecting changes relevant to dead code detection (not used in the submission)</li> <li><em>GitCommitExtractor.jar</em>: a commit extraction plug-in for extracting commits from Git repositories</li> <li><em>SvnCommitExtractor.jar</em>: a commit extraction plug-in for extracting commits from Subversion (SVN) repositories</li> <li><em>VariabilityChangeAnalyzer.jar</em>: a commit analyzer plug-in for detecting changes to artifact-specific and variability information in code, build, and variability model artifacts (realization of the commit analysis process described in the submission)</li> <li><em>busybox-commit-list</em>: a plain text file containing a subset of the BusyBox commits as required by the application to extract and analyze only those parts of its entire history relevant for the submission (quote from the submission: <em>"For BusyBox, we had to further exclude commits before the complete migration to Kbuild and after the introduction of a script for extracting variability model information from code artifacts, which initiated defining variability information of the variability model as part of comments in code artifacts. This mixing of information and artifact types is not supported by our tooling"</em>)</li> <li><em>axtls.properties</em>: the configuration (file) defining the required properties for extracting and analyzing commits of the axTLS history</li> <li><em>busybox.properties</em>: the configuration (file) defining the required properties for extracting and analyzing all commits of the BusyBox history</li> <li><em>busybox-subset.properties</em>: the configuration (file) defining the required properties for extracting and analyzing the commits specified in the busybox-commit-list file only, resulting in the respective subset of the BusyBox history</li> <li><em>coreboot.properties</em>: the configuration (file) defining the required properties for extracting and analyzing all commits of the coreboot history</li> <li><em>linux.properties</em>: the configuration (file) defining the required properties for extracting and analyzing all commits of the Linux kernel history</li> <li><em>template.properties</em>: the configuration (file) template including descriptions of each property and its valid values</li> </ul> </li> <li><strong>ComAnI-Results.zip</strong>: a compressed archive containing the (raw) analysis results from applying the approach via its realization as provided by the previous archive to each of the software product lines. Hence, for each subject, a directory with the respective name exist, which in turn contains the following artifacts: <ul> <li><em>VariabilityChangeAnalyzer-Results_2022-09-[…]</em>: the directory containing the respective analysis results and some automated visualizations. Please note that some files are not correctly labeled, .e.g. some files for axTLS and BusyBox are prefixed with "coreboot", while containing the correct data for the respective subjects. Further, for BusyBox, two directories exist, which the additional readme-file explains</li> <li><em>project-size-trace.txt</em>: the complete trace from starting ComAnI-PS.jar (see description above) with a specific configuration file to its final output</li> </ul> </li> <li><strong>JSS23_Extended-Evolution-Analysis_Statistics.ods</strong>: a <a href="https://www.libreoffice.org/discover/calc/">LibreOffice Calc</a> spreadsheet containing data derived from the raw ones of the ComAnI-Results.zip and the respective visualizations as presented in the submission. Further, some sheets include additional data preparations used to write certain parts of the result and discussion sections.</li> </ul> <p>The additional <strong>LICENSE</strong> file defines <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache License Version 2.0, January 2004</a> to apply for all artifacts in this repository.</p> <p>This work is partially supported by the Evoline project, funded by the DFG (German Research Foundation) under Priority Programme SPP 1593 and by the ITEA3 project REVaMP², funded by the BMBF (German Ministry of Research and Education) under grant 01IS16042H. Any opinions expressed herein are solely by the authors and not of the DFG or BMBF.</p>
Architectural Feature Re-Modularization for Software Product Line Evolution
<p>Extensive maintenance leads to the Software Product Line Architecture<br> (PLA) degradation over time. When there is the need of<br> evolving the Software Product Line (SPL) to include new features,<br> or move to a new platform, a degraded PLA requires considerable<br> effort to understand and modify, demanding expensive refactoring<br> activity. In the state of the art, search-based algorithms are used to<br> improve PLA at package level. However, recent studies have shown<br> that the most variability and implementation details of an SPL are<br> described in the level of classes. There is a gap between existing<br> approaches and existing practical needs. In this work, we extend<br> the current state of the art to deal with feature modularization in<br> the level of classes by introducing a new search operator and a set<br> of objective functions to deal with feature modularization in a finer<br> granularity of the architectural elements, namely at class level. We<br> evaluated the proposal in an exploratory study with a PLA widely<br> investigated and a real-world PLA. The results of quantitative and<br> qualitative analysis point out that our proposal provides solutions<br> to properly re-modularize features in a PLA, being preferred by<br> practitioners, in order to support the evolution of SPLs.</p>
The Impact of Microservices on the Evolution of a Software Product Line
<p>Video apresentação artigo The Impact of Microservices on the Evolution of a Software Product Line</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.