Skip to main content
Powered by ShareScore

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.

12

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

12 results for “Anti-Pattern”

Learn how ShareScore rates datasets ↗
zenodo40/100

Cataloging Dependency Injection Anti-Patterns in Software Systems

<p><strong>Background</strong> Dependency Injection (DI) is a commonly applied mechanism to decouple classes from their dependencies in order to provide better modularization of software. In the context of Java, the availability of a DI specification and popular frameworks, such as Spring, facilitate DI usage in software projects. However, bad DI implementation practices can have negative consequences, such as increasing coupling, hindering the achievement of DI&#39;s main goal. Even though the literature suggests the existence of DI anti-patterns, there is no detailed documentation of such bad practices. Moreover, there is no evidence on their occurrence and perceived usefulness from the developer&#39;s point of view.&nbsp;</p> <p><strong>Aims</strong> Our goal is to review the reported DI anti-patterns in order to analyze their completeness and to propose and evaluate a novel catalog of Java DI anti-patterns.&nbsp;</p> <p><strong>Method</strong> We propose a catalog containing twelve Java DI anti-patterns. We selected four open-source and two closed-source software projects that adopt a DI framework and developed a tool to statically analyze the occurrence of the candidate DI anti-patterns within their source code. Also, we conducted a survey through face to face interviews with three experienced developers that regularly apply DI. We extended the survey in order to gather the perception of a set of fifteen expert and novice developers through an online questionnaire.&nbsp;</p> <p><strong>Results</strong> At least nine different DI anti-patterns appeared frequently in the analyzed projects. In addition, the feedback received from the developers confirmed the relevance of the catalog. Besides, the respondents expressed their willingness to refactor instances of anti-patterns from source code.</p> <p><strong>Conclusions</strong> The catalog contains Java DI anti-patterns that occur in practice and are useful. Sharing it with practitioners may help them to avoid such anti-patterns.</p>

opencc-by-4.0Jan 2020View details →
zenodo36/100

Supplementary material for "can you tell me if it smells? A study on how developers discuss code smells and anti-patterns in Stack Overflow"

<p>This dataset contains all data and results from the &quot;Can you tell me if it smells? A study on how developers discuss code smells and anti-patterns in Stack Overflow&quot; paper that was accepted at&nbsp;the&nbsp;22nd International&nbsp;Conference&nbsp;on&nbsp;Evaluation&nbsp;andAssessment&nbsp;in&nbsp;Software&nbsp;Engineering (EASE), Christchurch, New Zealand.</p>

opencc-by-4.0May 2018View details →
zenodo36/100

Replication Package for "Automated Reporting of Anti-Patterns and Decay in Continuous Integration"

<p>This is the replication package for the paper &quot;Automated Reporting of Anti-Patterns and Decay in Continuous Integration&quot; accepted for publication at <a href="https://2019.icse-conferences.org/track/icse-2019-Technical-Papers#event-overview">ICSE 2019 (Technical Track)</a>.</p> <p>We include all the artifacts necessary to replicate the results obtained in our paper. Specifically, we provide (i) all the scripts used to conduct our statistical tests and to process the data obtained from our surveys, (ii) the queries used to perform the project selection, (iii) and a runnable version of our CI anti-patterns detection tool along with the external source code used to quantify the presence of CI anti-patterns in our dataset.<br> Furthermore, we provide raw and processed data from our surveys and data (build logs and repositories) that can be used as input to our detection pipeline. We also include a Docker container image with a working environment containing the artifacts.</p> <p>Preprint of corresponding paper is available&nbsp;<a href="http://doi.org/10.5281/zenodo.2578271">here</a>.</p>

openapache2.0Jan 2019View details →
zenodo36/100

Microservice Anti-Patterns and Bad Smells: A Tertiary Study

<p>This dataset contains the search and classification processes&nbsp;of anti-patterns and bad smells catalog tertiary&nbsp;study.</p>

opencc-by-4.0Apr 2023View details →
zenodo32/100

[GAS 2022] Software Project Management Anti-Patterns for Video Game Development

<p>This dataset contains an analysis of 440 project management problems described in game postmortems from gamedeveloper.com (formerly Gamasutra). We grouped these problems into candidate anti-patterns, an then we link these candidates with anti-patterns documented in the Software Engineering literature.&nbsp;Specifically, we aim to answer the following research question how video game anti-pattern fits into the software anti-patterns literature?&nbsp;</p>

opencc-by-4.0Jan 2022View details →
zenodo32/100

DrAsync: Identifying and Visualizing Anti-Patterns inAsynchronous JavaScript [Anonymous Experimental Data]

<p>////////////////////////////////////<br> //</p> <p>This directory contains the raw data used to compute aggregate numbers in the paper.<br> There are five files, and 2 subdirectories:</p> <p>(1) apply_run_times: has the raw execution times of various calls to apply throughout vuepress&#39; tests;</p> <p>(2) cpdir_run_times: has the raw execution times of calling cpDir on a large directory as part of the cpDir case study;</p> <p>(3) eleventy_test_executions: contains 50 run times x 2 (before, after refactoring) for eleventy&#39;s test suite;</p> <p>(4) promise_resolve_then_case_study: contains execution times for the code fragment from strapi&#39;s evaluate function;</p> <p>(5) vuepress_test_executions: contains 50 run times x 2 (before, after refactoring) for vuepress&#39; test suite.</p> <p>For the subdirectories:</p> <p>(1) DynamicAndExecutedAntiPatterns: for each of 20 subject applications x for each of 8 anti-patterns, contains the number<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; of static occurences of anti-patterns which are executed, as well as how often.</p> <p>(2) StaticAntiPatterns: for each of 20 subject applications x for each of 8 anti-patterns, contains the number of static<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; occurrences of the anti-pattern. We further filtered this by discounting anti-patterns appearing<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; in test, generated, build, etc. directories with a separate command.</p> <p>////////////////////////////////////<br> //</p> <p>CodeQL queries for the anti-patterns are given in supplemental material (available on the submission form).&nbsp;<br> We will make the code for the visualization tool available as part of the artifact submission process if this paper is accepted.</p>

opencc-by-4.0Sep 2021View details →
zenodo32/100

Detection of the Fire Drill anti-pattern: 15 real-world projects with ground truth, issue-tracking data, source code density, models and code

<p>This package contains&nbsp;artifacts for <strong>15</strong>&nbsp;real-world software projects. The data is supposed to aid the detection of the presence of the Fire Drill anti-pattern. We include original data, ground truth, code (experimental setups and models), and notebooks. The data supports two distinct methods of detecting the AP: a) through issue-tracking data, and b) through the underlying source code. This version of the dataset corresponds to&nbsp;<strong>v8</strong>&nbsp;of the <a href="https://arxiv.org/abs/2104.15090v8">technical report</a> and the <a href="https://github.com/MrShoenel/anti-pattern-models/releases/tag/arxiv-v8">GitHub repository</a>.&nbsp;The&nbsp;package includes the following:</p> <p>Original data:</p> <ul> <li>For each project, its&nbsp;<strong>original</strong>&nbsp;artifacts (e.g., wikis, meeting minutes, mentor&#39;s notes, etc.)</li> <li>Evaluation of raters&#39; notes by the assessor</li> </ul> <p>Fire Drill in issue-tracking data:</p> <ul> <li><strong>Ground truth</strong> for whether and how strong each project exhibits the Fire Drill AP, on a scale from [0,10]. This was determined by two individual raters, who also reached a consensus.</li> <li>Coefficients for indicators for the first method, per project.</li> <li>Detailed issue-tracing data for each project: what occurred and when.</li> <li>Time logs for each project.</li> </ul> <p>Fire Drill in source-code data:</p> <ul> <li><strong>Four</strong> technical reports that&nbsp;document the developed method of how to translate a description into a detectable pattern, and to use the pattern to detect the presence and to score it (similar to the rating). Also includes a report for how activities were assigned to individual commits.</li> <li>Source code density data (metrics) for each commit in each of the nine projects as a separate dataset.</li> <li>Code: a snapshot of the repository that holds all code, models, notebooks, and pre-computed results, for utmost reproducibility (the code is written in R).</li> </ul>

opencc-by-nc-sa-4.0Jan 2023View details →
zenodo32/100

Detecting microservice anti-patterns using interactive service call graphs: Effort Assessment

<p>Supplemental Figures for&nbsp;<em>Detecting microservice anti-patterns using interactive service call graphs: Effort Assessment</em></p>

opencc-by-4.0Feb 2023View details →
zenodo32/100

Detecting microservice anti-patterns using interactive service call graphs: Effort Assessment

<p>Case Study Results for&nbsp;<em>Detecting microservice anti-patterns using interactive service call graphs: Effort Assessment</em></p>

opencc-by-4.0Feb 2023View details →
zenodo28/100

A Large Scale Empirical Study of the Impact of Spaghetti Code and Blob Anti-patterns on Program Comprehension

<p>Dataset and scripts used for the paper.</p>

opencc-by-4.0Dec 2019View details →
zenodo28/100

Principle-Driven Continuous Integration: Simplifying Failure Discovery and Raising Anti-Pattern Awareness (Appendix)

<p>Appendix to my thesis</p>

opencc-by-4.0Jan 2021View details →
zenodo28/100

Effective Teaching through Code Reviews: Patterns and Anti-Patterns

Open the record for dataset details and reuse information.

opencc-by-4.0May 2024View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated 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.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

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.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

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.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

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.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

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.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record