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.
164
datasets available to search
ShareScore release 0.7.1
Dataset results
164 results for “software development”
A Qualitative Analysis of Themes in Instant Messaging Communication of Software Developers
<p>Data available:</p> <ul> <li>Lists of public Gitter and Slack chat rooms selected for our study (see related DOI)</li> <li>Keywords used to search Gitter chat rooms</li> <li>Name, description and analysis of 87 Gitter cha rooms (downloaded with Gitter API - https://developer.gitter.im/docs/welcome)</li> <li>Name, description and analysis of 184 Slack cha rooms (found at Slofile - https://slofile.com/)</li> </ul>
Towards Developing and Analysing The Metric-Based Software Defect Severity Prediction Model
<p>This is a metric based approach to solve software defect severity prediction problem. In addition to that, this work proposes a new evaluation scheme that comprised of five metrics to analyze the performances.</p>
Dataset for an analysis of selected studies on software development and reuse in the field of software documentation
<p>The data record contains bibliographical metadata from 2012 to 2023, which have been extracted from the databases ScienceDirect, SpringerLink and IEEE Xplore. It was created in the context of a master thesis which will be published later. The aim was to make a selection of studies on software documentation from the perspective of software development based on the master thesis.</p>
An empirical study on the influence of developers' experience on software test code quality
<p>Software developers' engagement in open-source software projects lies in different levels of participation, e.g., core or peripheral developers. Recent studies have investigated the role of developers' contributions and their influence on software quality. However, few studies investigate the relationship between the developers' experience and test code quality in software projects. In this study, we aim to investigate the relationship between the developers' experience and the test code quality from the perspective of test smells. We performed an empirical study to analyze the insertion and removal of test smells in four open-source Java projects. We collected 18 test smells and calculated their authorship through the projects' Tags. The four software projects contain 386 test classes and 5,178 test smells. We found out that the insertion of 67.28\% of test smells occurs during the test class creation, and the removal of 20.88\% of test smells occurs during the evolution of projects. In addition, core developers are responsible for inserting 88.91\% and removing 89.82\% test smells. Core developers insert and remove more test smells than the peripheral developers. Most test smell removal is due to test code deletion, which may indicate that both core and peripheral developers are unaware of test smells in test code.</p>
Applying short text topic models to instant messaging communication of software developers
<p>Content related to paper "Applying short text topic models to instant messaging communication of software developers" published in the Journal of Systems and Software.</p> <p><strong>Data available:</strong></p> <ul> <li>Data sets used: JSONs with messages from Gitter chat rooms (downloaded with previous Gitter API - <a href="https://developer.gitter.im/docs/welcome" rel="nofollow">https://developer.gitter.im/docs/welcome</a>): <ul> <li>"Android.json"</li> <li>"ConsenSys.json"</li> <li>"WebpackDocs.json"</li> <li>"Jenkinsci.json"</li> <li>"Locomotive.json"</li> <li>"SpringSecurity.json"</li> <li>"Flutter.rar" - json file was compressed due to its size</li> <li>"GitterHQ.rar" - json file was compressed due to its size</li> <li>"Laravel.rar" - json file was compressed due to its size</li> </ul> </li> <li>"stopwords_list": Customized list of stop words</li> <li>"topics_sttm_results.csv": Topics obtained with each combination of model and corpus (both lemmatized and stemmed corpora)</li> <li>"intrusion_tasks.csv": Results of the survey for the Intrusion Tasks and its participants' background</li> <li>"topicnaming_tasks.csv": Results of the survey for the Topic Naming Tasks and its participants' background</li> <li>"intrinsic_metrics.csv": Scores of topic coherence metrics at topic level ('average' represents the score at model level)</li> <li>"topics_themes_chatrooms.csv": Results of the exercise described in Section 5.2 with the topics and themes identified in each of the 87 Gitter chat rooms.</li> <li>"sensitivity_analysis": Results of a smaller-scale sensitivity analysis to check the impact of the number of topics on the main findings of the paper.</li> </ul>
Current state of vulnerability handling from the perspective of software operators and developers: semi-structured interviews
<p>This archive contains the transcripts of semi-structured interviews, conducted as part of the study "Leveraging Fine-grained Telemetry Data for the Detection and Prevention of Vulnerability Exploits" by Konrad Ponichtera and Sebastian Proksch. The goal of the interviews was to collect insights about the current state of vulnerability handling in the software engineering industry and identify improvement possibilities from the perspective of the system operator.</p> <p>The interviews have been conducted with ten software engineers with system administration/operation backgrounds, meaning that either they perform system administration/operation as part of their responsibilities, or used to do so in the past. Each participant has been assigned an identifier from P1 to P10. Their roles and industry experience have been disclosed in the attached CSV file with the questionnaire responses.</p> <h1>Interview structure</h1> <p>The interviews were conducted online, and transcribed to the text file, which was then reviewed and pseudonymized. Each interview took approximately one hour. During each interview, the participants were asked to look into a problem of system vulnerabilities from the perspective of a system operator, who can configure and monitor the infrastructure, as well as deploy the applications. The participants were also informed that the operator cannot modify the applications' source code and artifacts. Then the participants were asked seven open questions about the status quo of vulnerability handling in software engineering and its three aspects of awareness, impact, and mitigation. The interviewees responded in accordance with their knowledge and experience.</p> <p>Afterwards, the researcher guiding the session introduced the proposed system to the interviewees, by describing its goal and functionality. To avoid the moderator acceptance bias, we explained that the system was designed within the Software Engineering Research Group of Delft University of Technology. The mitigation of social desirability bias has been achieved by describing the actions taken by an imaginary operator named Albert.</p> <p>After going through the wireframes of the operator's dashboard interface and describing the content of each screen, the participants were asked to follow a supervised walkthrough, where they played the role of an operator. They were presented with a hypothetical situation, where a critical vulnerability, similar to the <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2021-44228" target="_blank" rel="noopener">Log4Shell</a> appears on the dashboard. During this part, the guiding researcher was streaming the window of a wireframe editor. The interviewees were then asked to follow a think-aloud protocol, and indicate their actions as they "use" the system. Meanwhile, the researcher made changes to the wireframes to simulate the effect of the participants' actions.</p> <p>After the walkthrough, participants filled out a System Usability Scale (SUS) questionnaire and were asked additional questions about the impact the proposed system would have on their vulnerability awareness, impact analysis, and mitigation capability.</p> <h1>Files</h1> <p>The archive contains three types of artifacts from the interview: pseudonymized transcripts, the questionnaire and the wireframes.</p> <h2>Transcripts</h2> <p>The <em>transcripts</em> directory contains ten text files with pseudonymized interview transcripts. In each file, the parts spoken by the interviewing researcher have been prepended with "R:", while the parts spoken by the interviewee have been prepended by the interviewee's identifier.</p> <h2>Questionnaire</h2> <p>The CSV file contains the answers participants gave at the start of the interview. <br>Each participant was asked to provide their current job title and how many years they worked in the software engineering industry. They were also asked to specify which DevOps tools and technologies they used, and what system operator tasks they had a chance to do during their career. The goal of these questions was to estabilsh the interviewee's system operation background. Finally, after the prototype walkthrough, participants filled out SUS questionnaires, the results of which are included in the PDF.</p> <h2>Wireframes</h2> <p>The <em>wireframes</em> directory contains diagrams in DrawIO format (also exported to PDF), used during the interview.<br>The vision GUI wireframes were used to introduce participants to what the envisioned system would look like.<br>The walkthrough wireframes were used during the semi-supervised walkthrough scenario, where the interviewing researcher modified them following the participants' actions.</p>
Gamification of Student Development Projects in Software Engineering Education - Master's Thesis Dataset
<p>This dataset contains all questionnaire results of the Master's Thesis <em>Gamification of Student Development Projects in Software Engineering Education</em>. The thesis will be linked to this set as soon as it is completed and publically available.</p> <p>In total, five questionnaires were conducted. To analyze users and requirements, a questionnaire with students and project supervisors was conducted. The implemented tool was evaluated using a pre-, mid-, and post-study questionnaire. This dataset contains a folder for each questionnaire including results in CSV format, results in HTML format, which is more human readable, and the questionnaire in PDF format. Due to the used survey tool, <em>lamapoll</em>, some parts of the files are in German. However, the questions and responses are all in English.</p> <p>Additionally, the scripts folder contains the Python scripts that were used to produce the graphics of the thesis. The Python libraries <code>matplotlib</code>, <code>pandas</code>, <code>scipy</code>, <code>numpy</code>, and <code>plot_likert</code> are required to run the scripts. Some of them use the two provided files <code>evalutation_concat_raw_excel.csv</code>, which is a concatenation of the results of the three evaluation questionnaires, and <code>sprint_stats.csv</code>, which contains statistics of the sprints relevant to the user study.</p>
Supplementary Material for "Investigating Software Development Teams Members' Perceptions of Data Privacy in the Use of Large Language Models (LLMs)"
<h3>ABSTRACT<strong>: </strong></h3> <p><strong>Context</strong>: Large Language Models (LLMs) have revolutionized natural language generation and understanding. However, they raise significant data privacy concerns, especially when sensitive data is processed and stored by third parties. <br><strong>Goal</strong>: This paper investigates the perception of software development teams members regarding data privacy when using LLMs in their professional activities. Additionally, we examine the challenges faced and the practices adopted by these practitioners. <br><strong>Method</strong>: We conducted a survey with 78 ICT practitioners from five regions of the country. <br><strong>Results</strong>: Software development teams members have basic knowledge about data privacy and LGPD, but most have never received formal training on LLMs and possess only basic knowledge about them. Their main concerns include the leakage of sensitive data and the misuse of personal data. To mitigate risks, they avoid using sensitive data and implement anonymization techniques. The primary challenges practitioners face are ensuring transparency in the use of LLMs and minimizing data collection. Software development teams members consider current legislation inadequate for protecting data privacy in the context of LLM use. <br><strong>Conclusions</strong>: The results reveal a need to improve knowledge and practices related to data privacy in the context of LLM use. According to software development teams members, organizations need to invest in training, develop new tools, and adopt more robust policies to protect user data privacy. They advocate for a multifaceted approach that combines education, technology, and regulation to ensure the safe and responsible use of LLMs.</p>
Supplementary Material for the Paper "Characterizing Software Developers by Perceptions of Productivity"
<p>Contains the survey questions and preprint for the paper "Characterizing Software Developers by Perceptions of Productivity" submitted to ESEM'17. </p> <p>Please contact Thomas Zimmermann (tzimmer@microsoft.com) in case you have any questions.</p> <p> </p> <p><strong>Paper Abstract:</strong></p> <p>Understanding developer productivity is important to deliver software on time and at reasonable cost. Yet, there are numerous definitions of productivity and, as previous research found, productivity means different things to different developers. In this paper, we analyze the variation in productivity perceptions based on an online survey with 413 professional software developers at Microsoft. Through a cluster analysis, we identify and describe six groups of developers with similar perceptions of productivity: social, lone, focused, balanced, leading, and goal-oriented developers. We discuss design implications of these clusters for tools to support developers’ productivity.</p>
Towards a Theory of Software Development Expertise — Supplementary Material
<p>Software development includes diverse tasks such as implementing new features, analyzing requirements, and fixing bugs. Being an expert in those tasks requires a certain set of skills, knowledge, and experience. Several studies investigated individual aspects of software development expertise, but what is missing is a comprehensive theory. We present a first conceptual theory of software development expertise that is grounded in data from a mixed-methods survey with 335 software developers and in literature on expertise and expert performance. Our theory currently focuses on programming, but already provides valuable insights for researchers, developers, and employers. The theory describes important properties of software development expertise and which factors foster or hinder its formation, including how developers' performance may decline over time. Moreover, our quantitative results show that developers' expertise self-assessments are context-dependent and that experience is not necessarily related to expertise.</p>
What Affects Developer Experience in Software Platforms?
<p>this study aims to investigate and characterize the factors that affect Developer Experience (DX) in software platforms. To do so, we reviewed the existing literature on scientific databases and digital libraries to map and analyze the state-of-the-art of DX in development on software platforms. As the main contribution, we provide a set of DX factors as a reference guide to support researchers and practitioners in improving the development processes of the products and services on software platforms.</p>
Underrepresented Groups in Open Source Software Development
<p>This repository contains the artifacts generated when researching minority groups in open source software development, which aimed to analyze knowledge about minority groups in OSS projects. This set of artifacts consists of two main components:</p> <p><strong>Research Protocol (PDF):</strong></p> <p>The protocol in PDF format provides a detailed overview of the research design, methodology, and objectives of the study. It describes the scope of the research, research questions, and data collection approach. This protocol is a fundamental reference for researchers interested in understanding how the study was designed.</p> <p><strong>Search Data (CSV):</strong></p> <p>The CSV file contains the raw data collected during the research. The data includes results returned by each database, articles considered in each phase of the study, and the set of seed articles. The XLSX spreadsheet is a source for analyzing the data used in the research.</p> <p>This repository aims to promote a more transparent understanding of the process that guided this research. Researchers and the open source developer community can utilize this dataset for academic studies, replications, and informed decision-making to promote equity and representation in open source projects.</p>
Using social media and personality traits to assess software developers' emotions
<p>Companion DATA</p> <p>Title:<br> Using social media and personality traits to assess software developers' emotions</p> <p>Authors: <br> Leo Moreira Silva<br> Marília Gurgel Castro<br> Miriam Bernardino Silva<br> Milena Nestor Santos<br> Uirá Kulesza<br> Margarida Lima<br> Henrique Madeira</p> <p>Journal:<br> PeerJ Computer Science</p> <p>Github:<br> <a href="https://github.com/leosilva/peerj_computer_science_2022">https://github.com/leosilva/peerj_computer_science_2022</a></p> <p>------------------------------------------------------------<br> The folders contain:</p> <p>Experiment_Protocol.pdf: document that present the protocol regarding recruitment protocol, data collection of public posts from Twitter, criteria for manual analysis, and the assessment of Big Five factors from participants and psychologists. English version.</p> <p><br> /analysis<br> analyzed_tweets_by_psychologists.csv: file containing the manual analysis done by psychologists<br> analyzed_tweets_by_participants.csv: file containing the manual analysis done by participants<br> analyzed_tweets_by_psychologists_solved_divergencies.csv: file containing the manual analysis done by psychologists over 51 divergent tweets' classifications</p> <p><br> /dataset<br> alldata.json: contains the dataset used in the paper</p> <p>/ethics_committee<br> committee_response_english_version.pdf: contains the acceptance response of Research Ethics and Deontology Committee of the Faculty of Psychology and Educational Sciences of the University of Coimbra. English version.<br> committee_response_original_portuguese_version: contains the acceptance response of Research Ethics and Deontology Committee of the Faculty of Psychology and Educational Sciences of the University of Coimbra. Portuguese version.<br> committee_submission_form_english_version.pdf: the project submitted to the committee. English version.<br> committee_submission_form_original_portuguese_version.pdf: the project submitted to the committee. Portuguese version.<br> consent_form_english_version.pdf: declaration of free and informed consent fulfilled by participants. English version.<br> consent_form_original_portuguese_version.pdf: declaration of free and informed consent fulfilled by participants. Portuguese version.<br> data_protection_declaration_english_version.pdf: personal data and privacy declaration, according to European Union General Data Protection Regulation. English version.<br> data_protection_declaration_original_portuguese_version.pdf: personal data and privacy declaration, according to European Union General Data Protection Regulation. Portuguese version.</p> <p>/notebooks<br> General - Charts.ipynb: notebook file containing all charts produced in the study, including those in the paper<br> Statistics - Lexicons and Ensembles.ipynb: notebook file with the statistics for the five lexicons and ensembles used in the study<br> Statistics - Linear Regression.ipynb: notebook file with the multiple linear regression results<br> Statistics - Polynomial Regression.ipynb: notebook file with the polynomial regression results<br> Statistics - Psychologists versus Participants.ipynb: notebook file with the statistics between the psychologists and participants manual analysis<br> Statistics - Working x Non-working.ipynb: notebook file containing the statistical analysis for the tweets posted during work period and those posted outside of working period</p> <p><br> /surveys<br> Demographic_Survey_english_version.pdf: survey inviting participants to enroll in the study. We collect demographic data and participants' authorization to access their public Tweet posts. English version.<br> Demographic_Survey_portuguese_version.pdf: survey inviting participants to enroll in the study. We collect demographic data and participants' authorization to access their public Tweet posts. Portuguese version.<br> Demographic_Survey_answers.xlsx: participants' demographic survey answers<br> ibf_pt_br.doc: the Portuguese version of the Big Five Inventory (BFI) instrument to infer participants' Big Five polarity traits.<br> ibf_en.doc: translation in English of the Portuguese version of the Big Five Inventory (BFI) instrument to infer participants' Big Five polarity traits.<br> ibf_answers.xlsx: participantes' and psychologists' answers for BFI</p> <p><br> ------------------------------------------------------------</p> <p>We have removed from dataset any sensible data to protect participants' privacy and anonymity.<br> We have removed from demographic survey answers any sensible data to protect participants' privacy and anonymity.</p>
"STILL AROUND": Experiences and Survival Strategies of Veteran Women Software Developers (Supplementary Material)
<p>The intersection of ageism and sexism can create a hostile environment for veteran software developers belonging to marginalized genders. In this study, we conducted 14 interviews to examine the experiences of people at this intersection, primarily women, in order to discover the strategies they employed in order to successfully remain in the field. We identified 283 codes, which fell into three main categories: <em>Strategies</em>, <em>Experiences</em>, and <em>Perception</em>. Several strategies we identified, such as <em>(Deliberately) Not Trying to Look Younger</em>, were not previously described in the software engineering literature. We found that, in some companies, older women developers are recognized as having particular value, further strengthening the known benefits of diversity in the workforce. Based on the experiences and strategies, we suggest organizations employing software developers to consider the benefits of hiring veteran women software developers. For example, companies can draw upon the life experiences of older women developers in order to better understand the needs of customers from a similar demographic. While we recognize that many of the strategies employed by our study participants are a response to systemic issues, we still consider that, in the short-term, there is benefit in describing these strategies for developers who are experiencing such issues today.</p>
Using social media and personality traits to assess software developers' emotional polarity
<p>Companion DATA</p> <p>Title:<br> Using social media and personality traits to assess software developers' emotional polarity</p> <p>Authors: <br> Leo Moreira Silva<br> Marília Gurgel Castro<br> Miriam Bernardino Silva<br> Milena Santos<br> Uirá Kulesza<br> Margarida Lima<br> Henrique Madeira</p> <p>Journal:<br> PeerJ Computer Science</p> <p>Github:<br> <a href="https://github.com/leosilva/peerj_computer_science_2022">https://github.com/leosilva/peerj_computer_science_2022</a></p> <p>------------------------------------------------------------<br> The folders contain:</p> <p>Experiment_Protocol.pdf: document that present the protocol regarding recruitment protocol, data collection of public posts from Twitter, criteria for manual analysis, and the assessment of Big Five factors from participants and psychologists. English version.</p> <p><br> /analysis<br> analyzed_tweets_by_psychologists.csv: file containing the manual analysis done by psychologists<br> analyzed_tweets_by_participants.csv: file containing the manual analysis done by participants<br> analyzed_tweets_by_psychologists_solved_divergencies.csv: file containing the manual analysis done by psychologists over 51 divergent tweets' classifications</p> <p><br> /dataset<br> alldata.json: contains the dataset used in the paper</p> <p>/ethics_committee<br> committee_response_english_version.pdf: contains the acceptance response of Research Ethics and Deontology Committee of the Faculty of Psychology and Educational Sciences of the University of Coimbra. English version.<br> committee_response_original_portuguese_version: contains the acceptance response of Research Ethics and Deontology Committee of the Faculty of Psychology and Educational Sciences of the University of Coimbra. Portuguese version.<br> committee_submission_form_english_version.pdf: the project submitted to the committee. English version.<br> committee_submission_form_original_portuguese_version.pdf: the project submitted to the committee. Portuguese version.<br> consent_form_english_version.pdf: declaration of free and informed consent fulfilled by participants. English version.<br> consent_form_original_portuguese_version.pdf: declaration of free and informed consent fulfilled by participants. Portuguese version.<br> data_protection_declaration_english_version.pdf: personal data and privacy declaration, according to European Union General Data Protection Regulation. English version.<br> data_protection_declaration_original_portuguese_version.pdf: personal data and privacy declaration, according to European Union General Data Protection Regulation. Portuguese version.</p> <p>/notebooks<br> General - Charts.ipynb: notebook file containing all charts produced in the study, including those in the paper<br> Statistics - Lexicons and Ensembles.ipynb: notebook file with the statistics for the five lexicons and ensembles used in the study<br> Statistics - Linear Regression.ipynb: notebook file with the multiple linear regression results<br> Statistics - Polynomial Regression.ipynb: notebook file with the polynomial regression results<br> Statistics - Psychologists versus Participants.ipynb: notebook file with the statistics between the psychologists and participants manual analysis<br> Statistics - Working x Non-working.ipynb: notebook file containing the statistical analysis for the tweets posted during work period and those posted outside of working period</p> <p><br> /surveys<br> Demographic_Survey_english_version.pdf: survey inviting participants to enroll in the study. We collect demographic data and participants' authorization to access their public Tweet posts. English version.<br> Demographic_Survey_portuguese_version.pdf: survey inviting participants to enroll in the study. We collect demographic data and participants' authorization to access their public Tweet posts. Portuguese version.<br> Demographic_Survey_answers.xlsx: participants' demographic survey answers<br> ibf_pt_br.doc: the Portuguese version of the Big Five Inventory (BFI) instrument to infer participants' Big Five polarity traits.<br> ibf_en.doc: translation in English of the Portuguese version of the Big Five Inventory (BFI) instrument to infer participants' Big Five polarity traits.<br> ibf_answers.xlsx: participantes' and psychologists' answers for BFI</p> <p><br> ------------------------------------------------------------</p> <p>We have removed from dataset any sensible data to protect participants' privacy and anonymity.<br> We have removed from demographic survey answers any sensible data to protect participants' privacy and anonymity.</p>
Reproduction package for "Revisiting the reproducibility of empirical software engineering studies based on data retrieved from development repositories"
<p>Reproduction package for "Revisiting the reproducibility of empirical software engineering studies based on data retrieved from development repositories", published in Information and Software Technology, Volume 164, December 2023. DOI: <a title="Persistent link using digital object identifier" href="https://doi.org/10.1016/j.infsof.2023.107318" target="_blank" rel="noreferrer noopener"><span><span>https://doi.org/10.1016/j.infsof.2023.107318</span></span></a></p>
Supplementary material of the study "Help! I need somebody. A Mapping Study about Expert Identification in Software Development"
<p><strong>Supplementary Material</strong></p> <p><em><strong>Context</strong></em>: Software development is a knowledge-intensive activity, and its success in an organization relies deeply on knowledge sharing. Knowledge management challenges are often increased in agile environments, which involve a lot of tacit knowledge, commonly acquired through experiences and hard to be made explicit. Therefore, knowledge sharing among practitioners is crucial. However, identifying suitable experts to share specific knowledge is not trivial. It involves not only discovering the individuals with the desired knowledge but also considering other factors that may improve the expert responsiveness, such as social connections and availability. <em><strong>Objective</strong></em>: Considering the important role experts play in knowledge sharing, we decided to investigate approaches that help identify experts that can share knowledge in software development. Our goal is to provide a panorama of the existing approaches and shine a light on research opportunities. <em><strong>Method</strong></em>: We carried out a systematic literature mapping and analyzed 17 publications. <em><strong>Results</strong></em>: The results show that most approaches have relied on code repositories as a source of evidence for identifying experts and, consequently, focus on supporting developers and aiding in the codification activity. Additionally, expert identification has been mostly automated, and factors beyond possessing the desired knowledge have often been disregarded. <em><strong>Conclusion</strong></em>: Although there are several expert identification approaches, there has been a lack of concern with factors that influence reaching the most suitable expert for a specific situation (e.g., considering the characteristics of the person seeking knowledge). Moreover, there is a need for deeper reflection on how to better explore different artifacts as sources of expert evidence and how to combine them to improve expert identification.</p> <p>This package contains supplementary material of the study performed to investigate approaches that help identify experts that can share knowledge in software development. It contains:</p> <ul> <li>A spreadsheet containing raw data (research protocol, considered and selected publications, and research questions answers).</li> </ul>
Evolution of Teamwork Quality Instruments in Agile Software Development: A Systematic Literature Review
<p>Suplemmentary Material of the article: Evolution of Teamwork Quality Instruments in Agile Software Development: A Systematic Literature Review</p>
Hypermedia-based software architecture enables test-driven development
<p><em>Objectives: </em></p> <p>Using agile software development practices, develop and evaluate a software architecture and implementation for reliable management of bioinformatic data that is stored in the cloud.</p> <p><em>Materials and Methods: </em></p> <p>CORE (Comprehensive Oncology Research Environment) Browser is a new open-source web application for cancer researchers to manage sequencing data organized in a flexible format in Amazon Simple Storage Service (S3) buckets. It has a microservices- and hypermedia-based architecture, which we integrated with Test-Driven Development (TDD), the iterative writing of computable specifications for how software should work prior to development. Optimal testing completeness is a tradeoff between code coverage and software development costs. We hypothesized this architecture would permit developing tests that can be executed repeatedly for all microservices, maximizing code coverage while minimizing effort.</p> <p><em>Results: </em></p> <p>After one-and-a-half years of development, the CORE Browser backend had 121 tests designed for repeated execution and 875 custom tests that were executed 3,031 times, providing 78% code coverage.</p> <p><em>Discussion: </em></p> <p>Hypermedia architecture's repeating pattern, links, permits CORE Browser to implement tests that can be executed repeatedly by every microservice to achieve high code coverage. Code coverage correlates with software reliability. Other benefits of this architecture include permitting access to bucket data from outside the application and separating management of bioinformatic data from analysis.</p> <p><em>Conclusion: </em></p> <p>Architectural choices are important enablers of modern software development practices, such as TDD. Updating software architecture may be a critical next step in agile transformation after an engineering team implements the structural changes on which most such transformations focus.</p> <p><em>Keywords: </em></p> <p>High-throughput nucleotide sequencing, software, data management, cloud computing.</p>
Development of Software to Provide the SpeechVive Device Via the Internet
ClinicalTrials.gov study NCT02744911. IPD Sharing: YES. Countries: 1. Publications: 5.
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.