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.
880
datasets available to search
ShareScore release 0.9.0
Dataset results
880 results for “Exploratory Study”
Model Generation from Requirements with LLMs: an Exploratory Study - Replication Package
<p>This is a replication package for the paper "<span>Model Generation from Requirements </span><span>with LLMs: an Exploratory Study</span>", by Sallam Abualhaija, Chetan Arora, and Alessio Ferrari.</p> <p><strong>Abstract: </strong>Complementing natural language (NL) requirements with graphical models can improve stakeholders’ communication and provide directions for system design. However, creating models from requirements involves manual effort. The advent of generative large language models (LLMs), ChatGPT being a notable example, offers promising avenues for automated assistance in model generation. This paper investigates the reliability of ChatGPT in generating sequence diagrams from NL requirements. Specifically, we conduct a qualitative study examining the sequence diagrams generated by ChatGPT for 28 requirements documents of various types and from different domains. Our study aims to uncover potential issues that emerge in the models generated by ChatGPT, thereby hindering its applicability in practice. Observations have systematically been captured through evaluation logs, and categorized through thematic analysis. Our results indicate that, although the models generally conform to the standard and exhibit a reasonable level of understandability, their correctness with respect to the specified requirements often presents challenges. This issue is particularly pronounced in the presence of requirements smells, such as ambiguity and inconsistency. The insights derived from this study can influence the practical utilization of LLMs in the RE process, and open the door to novel RE-specific prompting strategies targeting effective model generation.</p> <p>The replication package consists of the following folders:</p> <p><strong>logs:</strong> includes the evaluation logs produced by each evaluator</p> <p><strong>original-documents: </strong>includes the original requirements documents used for the evaluation</p> <p><strong>RQ1 - quantitative analysis:</strong> includes the analysis made on the scores given to each model and model variant. It includes five files:</p> <p>- results.csv: numerical results of the evaluation for each criterion<br>- analysis-results.Rmd: R file used to perform the quantitative analysis (requires R Studio to be executed)<br>- analysis-results.html: html file produced by analysis-results.Rmd<br>- cross-check.csv: file with the cross-checking of the two assessors applied to a subset of the models<br>- symmary_results.xlsx: final output of the quantitative results in terms of Wilcoxon signed rank tests</p> <p><strong>RQ2 - thematic analysis: </strong>includes the codebook produced by the thematic analysis of the issues in generating models with ChatGPT</p>
Dataset for TLS understory characterization: an exploratory study on hazel grouse in Italian Alps
<p>This dataset contains data collected in the middle of June 2021 with a mobile terrestrial laser scanner (mobile ZEB TLS) in 10 squared areas, of approximatively 20x20m each, in Adamello Brenta National Park. Data have been normalized using TreeLS package in R.</p> <p>This research was funded with the contribution of the Italian Ministry of Agricultural, Food, and Forestry Policies (MiPAAF) sub-project “Precision Forestry” (AgriDigit program) (DM 36503.7305.2018 of 20/12/2018).</p>
Mapping breakpoint types: an exploratory study
<p>This repository contains the breakpoint types study dataset.</p> <p><strong>Abstract</strong></p> <p>Debugging is a relevant task for finding bugs during software development, maintenance, and evolution. During debugging, developers use modern IDE debuggers to analyze variables, step execution, and set breakpoints. Observing IDE debuggers, we find several breakpoint types. However, what are the breakpoint types? The goal of our study is to map the breakpoint types among IDEs and academic literature. Thus, we mapped the gray literature on the documentation of the nine main IDEs used by developers according to the three public rankings. In addition, we performed a systematic mapping of academic literature over 68 articles describing breakpoint types. Finally, we analyzed the developers understanding of the main breakpoint types through a questionnaire. We present three main contributions: (1) the mapping of breakpoint types (IDEs and literature), (2) compiled definitions of breakpoint types, (3) a breakpoint type taxonomy. Our contributions provide the first step to organize breakpoint IDE taxonomy and lexicon, and support further debugging research.</p>
How are Solidity smart contracts tested in open source projects? An exploratory study
<p>A dataset with 139 Github Solidity projects containing information about testing files, testing tools, and testnets that each project uses.</p>
Exploratory pilot study on resource allocation along the dementia continuum under constrained and unconstrained budget scenarios
<p>Supporting quantitative data for a pilot longitudinal balance of care study. </p>
Supplementary material to the article "Finding a way into an interpreter's heart: Methodological considerations on heart-rate variability building on an exploratory study"
<p>Supplementary material to the article "Finding a way into an interpreter's heart: Methodological considerations on heart-rate variability building on an exploratory study" by Nicoletta Spinolo, Christian Olalla-Soler & Ricardo Muñoz Martín. </p> <p>The ZIP file contains the four texts that were used in the study reported in the article. </p> <p>Reference:</p> <p>Spinolo, Nicoletta; Olalla-Soler, Christian, Muñoz Martín, Ricardo (202X). "Finding a way into an interpreter's heart: Methodological considerations on heart-rate variability building on an exploratory study". </p>
The Metadata of "The punishment intensity for research misconduct and its related factors: An exploratory study on hospitals in Mainland China"
<p>This is the metadata of the research article <em>The punishment intensity for research misconduct and its related factors: An exploratory study on hospitals in Mainland China.</em></p> <p> </p>
DATASET OF "Exploratory study of OpenAlex datasets to assess productivity of authors and institutions"
<p><strong>Dataset to "Exploratory study of OpenAlex datasets to assess productivity of authors and institutions"</strong></p>
Classifying Generated White-Box Tests: An Exploratory Study
<p>The data and analysis scripts for our paper entitled Classifying Generated White-Box Tests: An Exploratory Study</p>
An exploratory study (with and without time pressure) using mouse dynamics to detect faking-good behavior in the MMPI-2 and PPI-R validity scales
<p>Please find here the dataset generated and analyzed during the study entitled "Can mouse dynamics detect faking-good behavior in personality questionnaires? An exploratory study (with and without time pressure) using the MMPI-2 and PPI-R validity scales". Moreover, here you can find the source code of the experiment to execute the task using MouseTracker software, the code of the statistical analysis and a file containing the instructions to replicate ML model results reported in the original paper.</p>
Replication package for "An Exploratory Study on Default Class Openness in Java and Kotlin"
<p>This dataset includes scripts, text files, and cached CSV/Parquet or raw TXT data files used to generate all analysis and results from the paper. A <strong>README.md</strong> file is included in <strong>replication-pkg.zip</strong> for details on using the scripts.</p> <p>If you only want to inspect the figures, you do not need a data ZIP.</p> <p>If you want to simply re-generate the figures without changes, download <strong>data-cached.zip</strong>. If you want to make any sort of change to the analyses, you will want to download <strong>data-csv.zip</strong> and/or <strong>data-raw.zip</strong>. The CSV files are converted versions of the raw TXT files.</p>
Epidemiological geography at work. An exploratory review about the overall findings of spatial analysis applied to the study of CoViD-19 propagation along the first pandemic year (DATASET)
<p><strong>Literature review dataset</strong></p> <p>This table lists the surveyed papers concerning the application of spatial analysis, GIS (Geographic Information Systems) as well as general geographic approaches and geostatistics, to the assessment of CoViD-19 dynamics. The period of survey is from January 1<sup>st</sup>, 2020 to December 15<sup>th</sup>, 2020. The first column lists the reference. The second lists the date of publication (preferably, the date of online publication). The third column lists the Country or the Countries and/or the subnational entities investigated. The fourth column lists the epidemiological data utilized in each paper. The fifth column lists other types of data utilized for the analysis. The sixth column lists the more traditionally statistically-based methods, if utilized. The seventh column lists the geo-statistical, GIS or geographic methods, if utilized. The eight column sums up the findings of each paper. The papers are also classified within seven thematic categories. The full references are available at the end of the table in alphabetical order.</p> <p>This table was the basis for the realization of a comprehensive geographic literature review. It aims to be a useful tool to ease the "due-diligence" activity of all the researchers interested in the spatial analysis of the pandemic.</p> <p>The reference to cite the related paper is the following:</p> <p><strong>Pranzo, A.M.R., Dai Prà, E. & Besana, A. Epidemiological geography at work: An exploratory review about the overall findings of spatial analysis applied to the study of CoViD-19 propagation along the first pandemic year. GeoJournal (2022). https://doi.org/10.1007/s10708-022-10601-y</strong></p> <p>To read the manuscript please follow this link: <strong>https://doi.org/10.1007/s10708-022-10601-y</strong></p> <p> </p>
An Exploratory Study of Sharing Strategic Programming Knowledge
<p>Replication package for the study of 'An Exploratory Study of Sharing Strategic Programming Knowledge'</p>
An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company: Appendix
<p>Appendix of our "An Exploratory Study on Faults in Web API Integration in a Large-Scale Payment Company: Appendix" paper.</p>
Replication Package for the Paper: "Code Reviewer Recommendation for Architecture Violations: An Exploratory Study"
<p>This is the replication package for the paper: "Code Reviewer Recommendation for Architecture Violations: An Exploratory Study".</p> <p><strong>1) scripts.zip </strong>includes the Python scripts used to run the experiments in this work. Experimental details (e.g., parameters) are described in the Python files. Choose the relevant experimental settings and run "Experiment.py" to start the experiments.</p> <p><strong>2) dataset.xlsx </strong>is the dataset used in the experiments on code reviewer recommendation, which includes the code review comments (from the four OSS projects) related to architecture violations and the file paths of code changes.</p>
Artifact for ICSE'23 paper: Using Reactive Synthesis: An End-to-End Exploratory Case Study
<p>Artifact for ICSE'23 paper: Using Reactive Synthesis: An End-to-End Exploratory Case Study </p>
An Exploratory Study on the Usage and Readability of Messages Within Assertion Methods of Test Cases
<p>This is the code and dataset that accompanies the study: "<strong>An Exploratory Study on the Usage and Readability of Messages Within Assertion Methods of Test Cases</strong>." This study has been accepted for publication at the 2023 International Workshop on Natural Language-based Software Engineering.</p> <p><strong><em>Following is the abstract of the study:</em></strong></p> <p>Unit testing is a vital part of the software development process and involves developers writing code to verify or assert production code. Furthermore, to help comprehend the test case and troubleshoot issues, developers have the option to provide a message that explains the reason for the assertion failure. In this exploratory empirical study, we examine the characteristics of assertion messages contained in the test methods in 20 open-source Java systems. Our findings show that while developers rarely utilize the option of supplying a message, those who do, either compose it of only string literals, identifiers, or a combination of both types. Using standard English readability measuring techniques, we observe that a beginner's knowledge of English is required to understand messages containing only identifiers, while a 4th-grade education level is required to understand messages composed of string literals. We also discuss shortcomings with using such readability measuring techniques and common anti-patterns in assert message construction. We envision our results incorporated into code quality tools that appraise the understandability of assertion messages. </p>
An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps
<p>This is the code and dataset that accompanies the study: "<strong>An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps</strong>." This study has been accepted for publication at the 2023 International Conference on Technical Debt.</p> <p><strong><em>Following is the abstract of the study:</em></strong></p> <p>Technical debt describes situations where developers write less-than-optimal code to meet project milestones. However, this debt accumulation often results in future developer effort to live with or fix these quality issues. To better manage this debt, developers may document their sub-optimal code as comments in the code (i.e., self-admitted technical debt or SATD). While prior research has investigated the occurrence and characteristics of SATD, this research has primarily focused on non-mobile systems. With millions of mobile applications (apps) in multiple genres available for end-users, there is a lack of research on sub-optimal code developers intentionally implement in mobile apps. </p> <p>In this study, we examine the occurrence and characteristics of SATD in 15,614 open-source Android apps. Our findings show that even though such apps contain occurrences of SATD, the volume per app (a median of 4) is lower than in non-mobile systems, with most debt categorized as Code Debt. Additionally, we identify typical elements in an app that are prone to intentional sub-optimal implementations. We envision our findings supporting researchers and tool vendors with building tools and techniques to support app developers with app maintenance. </p>
Proteomics analysis for: The platelet transcriptome and proteome in Alzheimer's disease and aging: an exploratory cross-sectional study
<p>Alzheimer’s disease (AD) and aging are associated with platelet hyperactivity. However, the mechanisms underlying abnormal platelet function in AD and aging are yet poorly understood. To explore the molecular profile of AD and aged platelets, we investigated platelet activation (i.e., CD62P expression), proteome and transcriptome in AD patients, non-demented elderly, and young individuals as controls. AD, aged and young individuals showed similar levels of platelet activation based on CD62P expression. However, AD and aged individuals had a proteomic signature suggestive of increased platelet activation compared with young controls. Transcriptomic profiling suggested the dysregulation proteolytic machinery involved in the regulation of platelet function, particularly in the ubiquitin-proteasome system in AD and autophagy in aging. The functional implication of these transcriptomic alterations remains unclear and requires further investigations. </p>
Data from: Human conjunctival transcriptome in Acanthamoeba keratitis: An exploratory study
<p>The host conjunctival transcriptome of 9 patients with <em>Acanthamoeba</em> keratitis (AK) is compared to the conjunctival transcriptome of 13 patients with keratitis and no identified pathogen. Pathway enrichment analysis identified thirty-six transcripts as most differentially expressed between patients with AK compared to patients with presumed sterile keratitis.</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.