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.
199
datasets available to search
ShareScore release 0.9.0
Dataset results
199 results for “software studies”
Software Variability Tools: Industrial Survey and Systematic Mapping Study
<p>Software Variability Tools: Industrial Survey and Systematic Mapping Study</p>
Supplemental material for: Software System Testing assisted by Large Language Models: An Exploratory Study
<p>This is the supplemental material of the paper titled as “Software System Testing Assisted by Large Language Models: An Exploratory Study” presented at the 36th International Conference on Testing Software and Systems.</p> <p>It contains the raw execution data generated by both models, GPT-4o and GPT-4omini, during the exploratory study. The supplementary material includes the following files:</p> <ul> <li><em>GPT-4ominiRQ1-2ExecutionData.zip</em>: contains the JSON outputs from the OpenAI API for the GPT-4o mini model. Each output is labeled according to the research question number and the corresponding timestamp (for RQ1) or the requested test case (for RQ2), all provided in plain text format.</li> <li><em>GPT-4oRQ1-2ExecutionData.zip</em>: contains the JSON outputs from the OpenAI API for the GPT-4o model. Like the previous file, each output is named in plain text format based on the research question number and timestamp (for RQ1) or the requested test case (for RQ2).</li> </ul> <p>To cite this work: </p> <p>C. Augusto, J. Morán, A. Bertolino, C. de la Riva and J. Tuya, “S<em>oftware System Testing assisted by Large Language Models: An Exploratory Study</em>”, in <em>Testing Software and Systems</em> (pp. 239–255). Springer Nature Switzerland. https://doi.org/10.1007/978-3-031-80889-0_17</p>
Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts" - Umbrella Review
<p>Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts"</p> <p>Umbrella review - First review</p> <p>The objective of this umbrella review is to check that there are no reviews in the defined period from 2000 to 2024 that respond to the objective of this research</p> <p> </p>
Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts" - Systematic Literature Review
<p>Dataset for the study "Agile Change Approach for Collaborative Software Development Contexts" </p> <p>Second review</p> <p> </p> <p>This is the dataset for the full systematic literature review</p>
Operator-Software Impact in Local Tie Networks: Case study at Geodetic Observatory Wettzell (Data set)
<p>The operator-software impact describes the differences between results introduced by different operators using identical software packages but applying different analysis strategies to the same data. This contribution studies the operator-software impact in the framework of local tie determination, and compares two different analysis approaches. Both approaches are used in present local tie determinations and mainly differ in the consideration of the vertical deflection within the network adjustment. However, no comparison study has yet been made so far. Selecting a suitable analysis approach is interpreted as a model selection problem, which is addressed by information criteria within this investigation. A suitable model is indicated by a sufficient goodness of fit and an adequate number of model parameters. Moreover, the stiffness of the networks is evaluated by means of principle component analysis. Based on the date of a measurement campaign performed at the Geodetic Observatory Wettzell in 2021, the impact of the analysis approach on local ties is investigated. For that purpose, an innovated procedure is introduced to obtain reference points of space geodetic techniques defining the local ties. Within the procedure, the reference points are defined independently of the used reference frame, and are based on geometrical conditions. Thus, the results depend only on the estimates of the performed network adjustment and, hence, the applied network analysis approach. The comparison of the horizontal coordinates of the determined reference points shows a high agreement. The differences are less than 0.2 mm. However, the vertical components differ by more than 1 mm, and exceed the coverage of the estimated standard deviations. The main reasons for these large discrepancies are a network tilting and a network bending, which is confirmed by a residual analysis.</p>
ChatGPT Software Testing Study
<p>This repository contains the dataset and replication package for the TestEd'23 paper </p> <blockquote> <p>Sajed Jalil, Suzzana Rafi, Thomas LaToza, Kevin Moran, and Wing Lam, "ChatGPT and Software Testing Education: Promises & Perils", in Proceedings of the 2nd International Workshop on Software Testing Educaiton (co-located with ICST'23), Dublin Ireland</p> </blockquote> <p> </p>
Value-based Software Engineering: A Systematic Mapping Study
<p><strong>Abstract</strong><br> <strong>Background: </strong>Integrating value-oriented perspectives into the principles and practices of software engineering is fundamental to ensure that software development activities address key stakeholders’ views and also balance short-and long-term goals. This is put forward in the discipline of value-based software engineering (VBSE)<br> <strong>Aim:</strong> This study aims to provide an overview of VBSE with respect to the research efforts that have been put into VBSE.<br> <strong>Method:</strong> We conducted a systematic mapping study to classify evidence on value definitions, studies’ quality, VBSE principles and practices, research topics, methods, types, contribution facets, and publication venues.<br> <strong>Results:</strong> From 143 studies we found that the term “value” has not been clearly defined in many studies. VB Requirements Engineering and VB Planning and Control were the two principles mostly investigated, whereas VB Risk Management and VB People Management were the least researched. Most studies showed very good reporting and relevance quality, acceptable credibility, but poor in rigor. The main research topic was Software Requirements and case study research was the method used the most. The majority of studies contribute toward methods and processes, while very few studies have proposed metrics and tools.<br> <strong>Conclusion:</strong> We highlighted the research gaps and implications for research and practice to support VBSE.</p>
Dataset: Challenges, Strengths, and Strategies of People with ADHD in Software Engineering: A Case Study
<p>This dataset accompanies the paper "Challenges, Strengths, and Strategies of People with ADHD in Software Engineering: A Case Study". It contains interview guides as well as anonymous interview transcripts for six interviewees who explicitly consented to the publication.</p> <p>Specifically:</p> <ul> <li>Interview transcripts are Excel files starting with "<strong>interview</strong>".</li> <li>The interview instruments used for the 19 interviews are named "<strong>interview_guide_professionals</strong>" followed by a version number. V1 was used for the first 3 interviews, V2 for the 9 following interviews, and V3 for the remaining 7.</li> <li><strong>manager_feedback_guide.pdf</strong> is the interview guide used for discussions with the 4 managers. The preliminary results we showed them are depicted in <strong>01_challenges_themes_relations_noStrat_v2</strong>, <strong>02_strengths_themes_relations_v1</strong> and <strong>02_strengths_themes_relations_v2</strong></li> <li><strong>consent_form.pdf</strong> is a PDF version of the online form used to handle consent and intake of interviewees.</li> </ul>
Are Game Engines Software Frameworks? A Three-perspective Study
<p>Dataset for the paper: "Are Game Engines Software Frameworks? A Three-perspective Study"</p>
What constitutes software? An Empirical, Descriptive Study of Artifacts - Reproduction Dataset
<p>Dataset for reproducing the numbers, figures, and tables in the results section of the MSR 2020 paper <em>"What constitutes Software? An Empirical, Descriptive Study of Artifacts"</em>.</p> <p>The data is given in this release as extra file (<code>all_repo_files_categorized.csv.bz2</code>) as it is too big to be part of the repository directly.</p>
A Case Study on the Communication of a Local Software Developer Team
<p>Raw data and scripts for the analysis of the paper "A Case Study on the Communication of a Local Software Developer Team"</p> <p>The files with the extension "list" contain the communication of the according channel. For example, "talks.list" contains all the recorded talks. The first two columns of a file contains the communication patners, the third column the date, the fourth the time of day. The sixth column contains the duration of a talk, the seventh column the rough topic, followed by the id of the event in column eight. Since often, additional developers entered the conversation, which we recorded as extra event, we have summarized the events to one conversation, denoted by the last column. That is, the last column contains the id of the conversation.</p> <p>The file analysis.Rmd contains the script that we used to analyze the data and create the plots. We used the library coronet (available at GitHub:https://github.com/ecklbarb/coronet/tree/read-data-from-company). The input data must have the folder structure as discribed in the Readme of the coronet project.</p> <p>The file analysis.Rmd must be copied in the folder of the coronet library.</p>
Software Evolution and Quality Data from Controlled, Multiple, Industrial Case Studies
<p>This data was obtained from a controlled, multiple case study involving six professional developers and four real-life, industrial systems. The study was designed to control for the moderator factors: programmer skill, maintenance task and learning effect. The primary data set contains multiple sets of defects, in the form of reports (excel files) extracted from six issue tracking systems. The secondary data consists of a series of attributes extracted from the software systems (i.e., code smells) and their evolution (i.e., code churn), and a log specifying the dates on which developers worked on each of the systems/tasks, in the form of excel files. Details on the controlled, multiple case study can be found in the doctoral dissertation by Yamashita titled: "Assessing the Capability of Code Smells to Support Software Maintainability Assessments: Empirical Inquiry and Methodological Approach" (online) Available at: https://www.duo.uio.no/handle/10852/34525</p>
Supplementary Material for the Paper "Design Recommendations for Self-Monitoring in the Workplace: Studies in Software Development"
<p>Contains the supplementary material for the paper "Design Recommendations for Self-Monitoring in the Workplace: Studies in Software Development" submitted to CSCW'18. All contents are explained in the file README.txt.</p> <p>Abstract:<br> One way to improve the productivity of knowledge workers is to increase their self-awareness about productivity at work through self-monitoring. Yet, little is known about expectations of, the experience with and the impact of self-monitoring in the workplace. To address this gap, we studied software developers, as one community of knowledge workers. We used an iterative, feedback-driven development approach (N=20) and a survey (N=413) to infer design elements for workplace self-monitoring, which we then implemented as a technology probe called WorkAnalytics. We field-tested these design elements during a three-week study with software development professionals (N=43). Based on the results of the field study, we present design recommendations for self-monitoring in the workplace, such as using experience sampling to increase the awareness about work and to create richer insights, the need for a large variety of different metrics to retrospect about work, and that actionable insights, enriched with benchmarking data from co-workers, are likely needed to foster productive behavior change at work.</p>
Software Development Waste amidst COVID-19 Pandemic: An Industry Study
<p>The dataset is to support the publication "Software Development Waste amidst COVID-19 Pandemic: An Industry Study" in ISEC 2024. </p>
Artifact for "Inside Bug Report Templates: An Empirical Study on Bug Report Templates in Open-Source Software"
<p>This is the artifact for the paper "Inside Bug Report Templates: An Empirical Study on Bug Report Templates in Open-Source Software".</p> <p><strong>What the artifact does:</strong><br>1) a questionnaire that we used for our online survey (PDF);<br>2) the valid responses of our online survey (CSV).</p> <p>3) the code of preprocessing (.py).</p> <p>4) the dataset of preprocessing and labeling (CSV).</p>
Artifact for ACM CSUR article: "A Meta-Study of Software-Change Intentions"
<p>This archive includes the CSV files with the raw and aggregated data we used for our meta study:</p> <p>"A Meta-Study of Software-Change Intentions" published at the ACM Computing Surveys journal.</p> <p> </p> <p>Please refer to the readme for details on the files.</p>
Dataset: A Study on the Mental Models of Users Concerning Existing Software
<p>In 2022, we conducted a study on the mental models of users concerning existing software.</p> <p>Information on the execution of the study are presented in the paper linked below:</p> <p>https://doi.org/10.1007/978-3-030-98464-9_18</p>
Study Data: Semi-Automated Prioritization of Industrial Security Findings in Agile Software Development
<p>Dataset for the study of the paper "Semi-Automated Prioritization of Industrial Security Findings in Agile Software Development"</p>
Exploring Gender Bias in Remote Pair Programming among Software Engineering Students: The Twincode Original Study and First External Replication (datasets)
<p>This repository contains the datasets of the original experiment (University of Seville, December 2021) and its first external replication (University of California, Berkeley, May 2022) of the Twincode exploratory study on the effects of gender bias in remote pair programming among software engineering students.</p>
Supplementary material of the study "Flying over Brazilian Organizations with Zeppelin: A Preliminary Panoramic Picture of Continuous Software Engineering"
<p><strong>Supplementary Material</strong></p> <p><em>Context</em>: Software organizations have faced several challenges, such as the need for faster deliveries, frequent changes in requirements, lower tolerance to failures and the need to adapt to contemporary business models. Agile practices have allowed organizations to shorten development cycles and increase customer collaboration. However, this has not been enough. Organizations should evolve to continuous and data-driven development in a continuous software engineering approach. Continuous Software Engineering (CSE) consists of a set of practices and tools that support a holistic view of software development with the purpose of making it faster, iterative, integrated, continuous and aligned with business. Implementing CSE requires changes in the organization’s culture, practices and structure, which may not be easy. <em>Objective</em>: We aim to provide a preliminary picture of CSE adoption in Brazilian software organizations. <em>Method</em>: We adapted and used Zeppelin, a diagnostic instrument of CSE adoption based on the Stairway to Heaven Model (StH), to perform a survey with 28 Brazilian organizations aiming at investigating the adoption of CSE practices. <em>Results</em>: The results indicate that organizations have better addressed agile and continuous deployment practices than the ones related to continuous integration and continuous experimentation, but this scenario changes a bit depending on the organization type. The results also show that CSE adoption has been heterogeneous, but there are patterns in the adoption of some practices. <em>Conclusion</em>: Although the StH model proposes a sequential and evolutionary path for CSE adoption, organizations have not always followed that path systematically. There are indeed CSE practices that depend on others and thus contribute to sequential implementation. However, organizations tend to adopt the practices gradually, covering different stages, and evolving according to the organization needs.</p> <p>This package contains supplementary material of the study performed to investigate the adoption of CSE practices in Brazilian organizations. It contains:</p> <ul> <li>The questionnaire used to collect data (Google Forms format) – in Portuguese only (available at https://forms.gle/oWpiQ1VJ8oywj4sXA)</li> <li>The questionnaire used to collect data (pdf format) </li> <li>A spreadsheet containing raw data, some tables and graphs</li> <li>Python Notebook files for showing exploratory analysis (using Spearman Coefficient) </li> </ul> <p>Please cite: <em>Paulo Sérgio dos Santos Júnior, Monalessa P. Barcellos, Fabiano B. Ruy, and Moisés S. Omêna. 2022. Flying over Brazilian Organizations with Zeppelin: A Preliminary Panoramic Picture of Continuous Software Engineering. In 36th Brazilian Symposium on Software Engineering (SBES ’22), October 21–23, 2022, Uberlândia, Brazil.</em></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.