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.
3,947
datasets available to search
ShareScore release 0.9.0
Dataset results
3,947 results for “Requirement”
The Lack of Shared Understanding of Non-Functional Requirements in Continuous Software Engineering: Accidental or Essential?
<p>Study Information</p> <p>We conducted a case study of three small organizations scaling up continuous software engineering to further understand and identify factors that contribute to lack of shared understanding of non-functional requirements (NFRs), and its relationship to rework. To conceptualize lack of shared understanding of NFRs we traced it to rework development tasks. Seeking to shed light on the complex relationship between shared understanding, rework, and CSE, our study examined forty-one NFR-related development tasks identified as rework and was driven by the following research questions:</p> <ol> <li>What contributes to lack of shared understanding of NFRs?</li> <li>Which NFRs are most associated with a lack of shared understanding?</li> <li>What amount of a lack of shared understanding of NFRs is accidental versus essential?</li> </ol> <p>To answer our research questions, we conducted a multi-case study using a mixed-methods approach in collaboration with three independent organizations using qualitative and immersive techniques. For this study our organizations are referred to as Alpha, Beta, and Gamma. We performed a preliminary study of each organization to build a context for each organization. We then collected data from project task management repositories and analyzed the tasks to uncover 41 NFR-related software development tasks as rework due to a lack of shared understanding of NFRs.</p> <p>Data Analysis</p> <p>We performed qualitative analysis through focus groups at each organization. We used an open-coding [1] approach to develop a purely inductive codebook, which minimizes a coder's ability to force a bias of any particular hypothesis. In the initial coding phase, a transcript was independently coded by two coders, after which an agreement session was held to discuss the codes, consolidate the codebook, and to calculate Cohen's kappa coefficient (using sklearn.metrics cohen_kappa_score). We continued coding in pairs until our inter-rater reliability met substantial agreement. After which we individually coded the remaining transcripts followed by an expert rater reviewer.</p> <p>This data represents two artifacts from our research in evaluating the complex relationship between shared understanding, non-functional requirements, continuous software engineering, and rework. It includes the resulting thematic synthesis codebook and inter-rater kappa values.</p> <p>Artifact Descriptions</p> <p>Our replication package contains two artifacts:<br> 1. Codebook.csv: The codebook itself contains a row for each code used (48 in total), including the code name, a brief description of the code, which round of coding that code was introduced, the total number of tasks that code appeared in (at least once), the number of tasks that code appeared in for each organization (Alpha, Beta, and Gamma), the total number of occurrences across all tasks, the number of occurrences across across each organization (Alpha, Beta, and Gamma), and the number of occurrences for each task.</p> <p>For example, the code 'BusinessContext' was used when 'Talking about information from the business side of the organization' and appeared in the first transcript we coded (1). The 'BusinessContext' code appeared in 19/41 tasks (10 at Alpha, 8 at Beta, and 1 at Gamma). Furthermore, the 'BusinessContext' code was used a total of 72 times (43 at Alpha, 22 at Beta, and 7 at Gamma). The remaining 41 columns represent the number of occurrences for each task, e.g. it appeared 3 times in task A-2 (Alpha's second task).</p> <p>2. kappa-values.csv: Contains the interview rounds (in order of coding) and the associated kappa values calculated for our inter-rater coding agreement.</p> <p>Usefulness</p> <p>While we recognize that the value and usefulness of our replication package is yet to-be-determined, in the interest of transparency of open science we published our artifacts. In light of this, we hope that these artifacts are useful to either replicate our findings or to further analyze to produce other enlightening results.</p> <p>References</p> <ol> <li>J. M. Corbin and A. Strauss, “Grounded theory research: Procedures, canons, and evaluative criteria,”Qualitative sociology, vol. 13, no. 1,pp. 3–21, 1990.</li> </ol>
Plasmodium berghei Gamete Egress Protein is required for fertility of both genders
<p>Gamete Egress Protein (GEP) is a protein recently characterised in Plasmodium berghei. It plays a role in the egress of the gametes from the red blood cell and, consequently, in the transmission of the parasite to the mosquito.</p>
Data set for "Determining the minimum energy requirement of an LNG process: New insights into the impact of the vapour liquid equilibrium"
<p>Accompanying information for Xuan et al, 2020, "Determining the minimum energy requirement of an LNG process: New insights into the impact of the vapour liquid equilibrium", Energy, Paper number 117785, <a href="https://doi.org/10.1016/j.energy.2020.117785">https://doi.org/10.1016/j.energy.2020.117785</a></p>
Data analysis on the design requirements of the app for communication bridging as part of Co-design Activity 1
<p>This dataset includes the analyses of the participants' statements and drawing toward the design requirements of the app for communication bridging.</p>
Automatic Requirements Testability Analysis Dataset
<p>This repository contains the data and results from the paper “<a href="https://link.springer.com/article/10.1007/s00521-024-09730-x" target="_blank" rel="noopener">Requirement testability measurement based on requirement smells</a>”. We announce a public dataset of software requirements along with their quality issues to facilitate the development and evaluation of software requirement quality tools. The Automatic Requirement Testability Analyzer (ARTA) is a web application to measure requirement testability based on the requirement smells. It facilitates the requirement engineering quality assurance process and allows requirement engineers to manage the requirements of their projects.</p> <p>ARTA dataset is a collection of requirements along with their smells and degree of testability of each requirement. It has been used in the initial evaluation of ARTA testability measurement algorithms. To the best of our knowledge, there is no public dataset for developing and evaluating the requirements smell detector tools.</p> <p><strong>Dataset Structure</strong></p> <p>ARTA dataset contains 4752 software requirements extracted from 24 project documentation (in English). The ARTA dataset (release 1.0.0) is available as a collection of Microsoft Excel files. The <em>Datasets</em> directory contains five Excel files, described as follows:</p> <ol> <li><strong>DS1.xlsx:</strong> This file contains 985 requirements from 6 projects and nine types of smells manually labeled for each requirement.</li> <li><strong>DS2.xlsx:</strong> This file contains 1092 requirements from 8 projects and nine types of smells manually labeled for each requirement.</li> <li><strong>DS3.xlsx:</strong> This file contains 1522 requirements from 6 projects and nine types of smells manually labeled for each requirement.</li> <li><strong>DS4.xlsx:</strong> This file contains 1153 requirements from 4 projects and nine types of smells manually labeled for each requirement.</li> <li><strong>SmellyWordsDictionary.xlsx:</strong> This file contains 1000 most frequent words in computer science domains, which is sorted based on their similarity. Four types of requirement smells are detected based on the words in the smelly words dictionary. For each word, the type of smell has been determined manually by experts.</li> </ol> <p>The <em>DS1_Evaluation </em>directory contains the result of different smell detection and testability measurement algorithms, described as follows:</p> <ol> <li><strong>001_dataset1kv1.xlsx (primary dataset):</strong> The same DS1 in the Datasets directory. This file contains 985 requirements from 6 projects and nine types of smells manually labeled for each requirement.</li> <li><strong>002_dataset1kv1_smell_frequency_with_testability.xlsx:</strong> This file contains the number of words of each requirement, the number of smelly words, number of smelly words according to the type of smell, degree of cleanness, and testability of each requirement, which has been computed based on “001_dataset1kv1.xlsx”. The requirements are in the same order in “001_dataset1kv1.xlsx”.</li> <li><strong>003_dataset1kv1_ARTA_result.xlsx: </strong>This file contains the result of automatically detected smells by <em>ARTA</em>, our proposed smell detector tool. The requirements are in the same order in “001_dataset1kv1.xlsx”.</li> <li><strong>004_dataset1kv1_ARTA_result_smell_frequency_with_testability.xlsx:</strong> This file contains the number of words of each requirement, the number of smelly words, number of smelly words according to the type of smell, degree of cleanness, and testability of each requirement, which has been computed based on “003_dataset1kv1_ARTA_result.xlsx”. The requirements are in the same order in “001_dataset1kv1.xlsx”.</li> <li><strong>005_dataset1kv1_Smella_result.xlsx:</strong> This file contains the result of automatically detected smells by <em>Smella</em>, another smell detector tool. The requirements are in the same order in “001_dataset1kv1.xlsx”.</li> <li><strong>006_dataset1kv1_Smella_result_smell_frequency_with_testability.xlsx:</strong> This file contains the number of words of each requirement, the number of smelly words, number of smelly words according to the type of smell, degree of cleanness, and testability of each requirement, which has been computed based on “005_dataset1kv1_Smella_result.xlsx”. The requirements are in the same order in “001_dataset1kv1.xlsx”.</li> </ol> <p> </p>
Data from: Pleistocene sea level fluctuation and host plant habitat requirement influenced the historical phylogeography of the invasive species Amphiareus obscuriceps (Hemiptera: Anthocoridae) in its native range
Background: On account of repeated exposure and submergence of the East China Sea (ECS) land bridge, sea level fluctuation played an important role in shaping the population structure of many temperate species across the ECS during the glacial period. The flower bug Amphiareus obscuriceps (Poppius, 1909) (Hemiptera: Anthocoridae) is an invasive species native to the Sino-Japanese Region (SJR) of East Asia. We tested the hypothesis of the ECS land bridge acting as a dispersal corridor or filter for A. obscuriceps during the glacial period. Specifically, we tested whether and the extent to which dispersal ability and host plant habitat requirement influenced the genetic structure of A. obscuriceps during the exposure of the ECS land bridge. Results: Phylogenetic and network analyses indicated that A. obscuriceps is composed of two major lineages, i.e., China and Japan. Divergence time on both sides of the ECS was estimated to be approximately 1.07 (0.79-1.32) Ma, which was about the same period that the sea level increased. No significant Isolation by Distance (IBD) relationship was found between Фst and Euclidean distances in the Mantel tests, which is consistent with the hypothesis that this species has a good dispersal ability. Our Last Glacial Maximum (LGM) niche modeling of plants that constitute preferred habitats for A. obscuriceps exhibited a similar habitat gap on the exposed ECS continental shelf between China and Japan, but showed a continuous distribution across the Taiwan Strait. Conclusion: Our results suggest that ecological properties (habitat requirement and dispersal ability), together with sea level fluctuation during the Pleistocene across the ECS, have shaped the genetic structure and demographic history of A. obscuriceps in its native area. The host plant habitat requirement could also be a key to the colonization of the A. obscuriceps species during the exposure of the ECS land bridge. Our findings will shed light on the potential role of habitat requirement in the process of biological invasion in future studies.
Data from: Serotonin depletion-induced maladaptive aggression requires the presence of androgens
The sex hormone testosterone and the neurotransmitter serotonin exert opposite effects on several aspects of behavior including territorial aggression. It is however not settled if testosterone exerts its pro-aggressive effects by reducing serotonin transmission and/or if the anti-aggressive effect of serotonin requires the presence of the androgen. Using the resident intruder test, we now show that administration of the serotonin synthesis inhibitor para-chlorophenylalanine (300 mg/kg x 3 days) increases the total time of attack as well as the percentage amount of social behavior spent on attack but not that spent on threat – i.e. that it induces a pattern of unrestricted, maladaptive aggression – in gonadectomized C57Bl/6 male mice receiving testosterone replacement; in contrast, it failed to reinstate aggression in those not given testosterone. Whereas these results suggest the pro-aggressive effect of testosterone to be independent of serotonin, and not caused by an inhibition of serotonergic activity, the pCPA-induced induction of maladaptive aggression appears to require the presence of the hormone. In line with these findings, pCPA enhanced the total time of attack as well the relative time spent on attacks but not threats also in wild-type gonadally intact male C57Bl/6 mice, but failed to reinstate aggression in mice rendered hypo-aggressive by early knock-out of androgen receptors in the brain (ARNesDel mice). We conclude that androgenic deficiency does not dampen aggression by unleashing an anti-aggressive serotonergic influence; instead serotonin seems to modulate aggressive behavior by exerting a parallel-coupled inhibitory role on androgen-driven aggression, which is irrelevant in the absence of the hormone, and the arresting of which leads to enhanced maladaptive aggression.
Data from: Trophoblast survival signaling during human placentation requires HSP70 activation of MMP2-mediated HBEGF shedding
Survival of trophoblast cells in the low oxygen environment of human placentation requires metalloproteinase-mediated shedding of HBEGF and downstream signaling. A matrix metalloproteinase (MMP) antibody array and quantitative RT-PCR revealed upregulation of MMP2 post-transcriptionally in human first trimester HTR-8/SVneo trophoblast cells and placental villous explants exposed to 2% O2. Specific MMP inhibitors established the requirement for MMP2 in HBEGF shedding and upregulation. Because α-amanitin inhibited the upregulation of HBEGF, differentially expressed genes were identified by next-generation sequencing of RNA from trophoblast cells cultured at 2% O2 for 0, 1, 2 and 4 h. Nine genes, all containing HIF-response elements, were upregulated at 1 h, but only HSPA6 (HSP70B') remained elevated at 2–4 h. The HSP70 chaperone inhibitor VER 155008 blocked upregulation of both MMP2 and HBEGF at 2% O2, and increased apoptosis. However, both HBEGF upregulation and apoptosis were rescued by exogenous MMP2. Proximity ligation assays demonstrated interactions between HSP70 and MMP2, and between MMP2 and HBEGF, supporting the concept that MMP2-mediated shedding of HBEGF, initiated by HSP70, contributes to trophoblast survival at the low O2 concentrations encountered during the first trimester, and is essential for successful pregnancy outcomes. Trophoblast survival during human placentation, when oxygenation is minimal, required HSP70 activity, which mediated MMP2 accumulation and the transactivation of anti-apoptotic ERBB signaling by HBEGF shedding.
UTL: A Unified Requirements Templates Language for Safety Critical Systems
<p>This repository stores the data of our evaluation of the UTL language. The repository includes:</p> <ul> <li><strong>The requirement files of Rupp's template</strong> : The files generated by JFIO while specifying Rupp's template using UTL and JFIO. </li> <li><strong>The requirement files of EARS templates</strong> : The files generated by JFIO while specifying EARS templates using UTL and JFIO. </li> <li><strong>The material of the user study</strong> : The presentations, pre-study form, and post-study forms used in our user study.</li> </ul>
Supplementary data: "Speed of technological transformations required in Europe to achieve different climate goals"
<p>This repository includes results discussed in the paper "<a href="https://arxiv.org/abs/2109.09563">Speed of technological transformations required in Europe to achieve different climate goals</a>"</p> <p>In the paper, we used the open energy modelling framework <a href="https://pypsa.org/">PyPSA</a>, the model <a href="https://github.com/PyPSA/pypsa-eur-sec">PyPSA-Eur-Sec v0.5.0</a> and the cost and technology assumptions included in the repository <a href="https://github.com/PyPSA/technology-data">technology-data v0.2.0</a></p> <p>The directory 'version-baseline' includes the network objects obtained as an outcome of the optimization for the different years and carbon budgets in the baseline scenario.</p> <p>This dataset is released under the <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International Licence</a> (CC BY 4.0).</p>
Preprocessed dataset required to reproduce Supplementary Figure S6PQR
<p>These files are required to reproduce the supplementary figure S6PQR of the paper.</p> <p>The DataOverview_SF6PQR provides AnimalIDs, fiber side, protocol and recording dates.</p> <p>For each AnimalID in the DataOverview this dataset contains:</p> <p>1) The pre-processed photometry data of the CoT sound-on-return (SOR) session (filename: mouseID_date_smoothed_signal.npy) </p> <p>2) A dataframe containing all relevant behavioural events and time stamps of the CoT sound-on-return session (filename: mouseID_date_restructured_data.pkl)</p> <p>Please note, in this modified version of the CoT task, the sound-on-return (cue) was played during the return from the side to the center port to indicate that the subsequent trial is a contralateral trial. Ipsilateral trials were not affected and the cue was played upon poke in in the center port. </p>
Preprocessed dataset required to reproduce Supplementary Figure S5FG
<h2>Description</h2> <div> <p>These files are required to reproduce the supplementary figure S5FG of the paper.</p> <p>The DataOverview_SF5FG provides AnimalIDs and recording dates.</p> <p>For each AnimalID in the DataOverview this dataset contains:</p> <p>1) The pre-processed photometry data of the CoT session (filename: mouseID_date_smoothed_signal.npy) </p> <p>2) A dataframe containing all relevant behavioural events and time stamps of the CoT session (filename: mouseID_date_restructured_data.pkl)</p> <p>The CoT session was recorded after the threat experiment.</p> </div>
GENERAL REQUIREMENTS FOR THE DEFENDER OF THE FATHERLAND
<p><em><span>This article describes the general and special requirements that admired the future Defender of the Fatherland. In order to create a system for training the defender of the fatherland and increase its effectiveness, it is important to know the goals and objectives of military-patriotic education and in protecting one of the complex qualities of a person, such as shaylik. Fatherland.In the structure of shaylik such qualities as Homeland protection, spiritual, moral, spiritual, military-technical and physical education are usually distinguished</span></em></p>
Requirements data sets (user stories)
<p>A collection of 22 data set of 50+ requirements each, expressed as user stories. </p> <p>The dataset has been created by gathering data from web sources and we are not aware of license agreements or intellectual property rights on the requirements / user stories. The curator took utmost diligence in minimizing the risks of copyright infringement by using non-recent data that is less likely to be critical, by sampling a subset of the original requirements collection, and by qualitatively analyzing the requirements. In case of copyright infringement, please contact the dataset curator (Fabiano Dalpiaz, f.dalpiaz@uu.nl) to discuss the possibility of removal of that dataset [see <a href="https://support.zenodo.org/help/en-gb/13-policies/140-what-is-your-take-down-procedure" target="_blank" rel="noopener">Zenodo's policies</a>]</p> <p>The data sets have been originally used to conduct experiments about ambiguity detection with the REVV-Light tool: https://github.com/RELabUU/revv-light</p> <p>This collection has been originally published in Mendeley data: https://data.mendeley.com/datasets/7zbk8zsd8y/1</p> <h2>Overview of the datasets [data and links added in December 2024]</h2> <p>The following text provides a description of the datasets, including links to the systems and websites, when available. The datasets are organized by macro-category and then by identifier.</p> <h3>Public administration and transparency</h3> <p><code>g02-federalspending.txt</code> (2018) originates from early data in the Federal Spending Transparency project, which pertain to the website that is used to share publicly the spending data for the U.S. government. The website was created because of the Digital Accountability and Transparency Act of 2014 (DATA Act). The specific dataset pertains a system called DAIMS or Data Broker, which stands for DATA Act Information Model Schema. The sample that was gathered refers to a sub-project related to allowing the government to act as a data broker, thereby providing data to third parties. The data for the Data Broker project is currently not available online, although the backend seems to be hosted in <a href="https://github.com/fedspendingtransparency/data-act-broker-backend" target="_blank" rel="noopener">GitHub</a> under a CC0 1.0 Universal license. Current and recent snapshots of federal spending related websites, including many more projects than the one described in the shared collection, can be found <a href="https://federal-spending-transparency.atlassian.net/jira/" target="_blank" rel="noopener">here</a>.</p> <p><code>g03-loudoun.txt</code> (2018) is a set of extracted requirements from a document, by the Loudoun County Virginia, that describes the to-be user stories and use cases about a system for land management readiness assessment called Loudoun County LandMARC. The source document can be found <a href="https://www.loudoun.gov/DocumentCenter/View/131287/APPENDIX-A-3---Future-State-To-Be-Business-User-Stories-and-Use-Cases?bidId=" target="_blank" rel="noopener">here</a> and it is part of the <a href="https://www.loudoun.gov/bids.aspx?bidID=459" target="_blank" rel="noopener">Electronic Land Management System and EPlan Review Project - RFP RFQ</a> issued in March 2018. More information about the overall LandMARC system and services can be found <a href="https://www.loudoun.gov/5823/LandMARC-Land-Management-Applications-Re" target="_blank" rel="noopener">here</a>.</p> <p><code>g04-recycling.txt</code>(2017) concerns a web application where recycling and waste disposal facilities can be searched and located. The application operates through the visualization of a map that the user can interact with. The dataset has obtained from a <a href="https://github.com/rafaellichen/Recycling-System/wiki/User-Stories" target="_blank" rel="noopener">GitHub website</a> and it is at the basis of a students' project on web site design; the <a href="https://github.com/rafaellichen/Recycling-System" target="_blank" rel="noopener">code is available</a> (no license).</p> <p><code>g05-openspending.txt</code> (2018) is about the OpenSpending project (<a href="https://www.openspending.org/" target="_blank" rel="noopener">www</a>), a project of the Open Knowledge foundation which aims at transparency about how local governments spend money. At the time of the collection, the data was retrieved from a Trello board that is currently unavailable. The sample focuses on publishing, importing and editing datasets, and how the data should be presented. Currently, OpenSpending is managed via a <a href="https://github.com/os-data" target="_blank" rel="noopener">GitHub repository</a> which contains multiple sub-projects with unknown license.</p> <p><code>g11-nsf.txt</code> (2018) refers to a collection of user stories referring to the NSF Site Redesign & Content Discovery project, which originates from a publicly accessible <a href="https://github.com/nsf-open/nsf" target="_blank" rel="noopener">GitHub repository</a> (GPL 2.0 license). In particular, the user stories refer to an early version of the NSF's website. The user stories can be found as <a href="https://github.com/nsf-open/nsf/issues?q=is%3Aissue+is%3Aclosed" target="_blank" rel="noopener">closed Issues</a>. </p> <h3>(Research) data and meta-data management</h3> <p><code>g08-frictionless.txt</code> (2016) regards the Frictionless Data project, which offers an open source dataset for building data infrastructures, to be used by researchers, data scientists, and data engineers. Links to the many projects within the Frictionless Data project are on <a href="https://github.com/frictionlessdata" target="_blank" rel="noopener">GitHub</a> (with a mix of Unlicense and MIT license) and <a href="https://frictionlessdata.io/" target="_blank" rel="noopener">web</a>. The specific set of user stories has been collected in 2016 by GitHub user @danfowler and are stored in a <a href="https://trello.com/b/MGC4RpTZ/frictionless-data-user-stories" target="_blank" rel="noopener">Trello board</a>.</p> <p><code>g14-datahub.txt</code> (2013) concerns the open source project <a href="https://datahubproject.io/" target="_blank" rel="noopener">DataHub</a>, which is currently developed via a <a href="https://github.com/datahub-project/datahub" target="_blank" rel="noopener">GitHub repository</a> (the code has Apache License 2.0). DataHub is a data discovery platform which has been developed over multiple years. The specific data set is an <a href="https://datahub.io/docs/dms/datahub/developers/user-stories#stories" target="_blank" rel="noopener">initial set of user stories</a>, which we can date back to 2013 thanks to a comment therein.</p> <p><code>g16-mis.txt</code> (2015) is a collection of user stories that pertains a repository for researchers and archivists. The source of the dataset is a public <a href="https://trello.com/b/hrulGmdz/repository-user-stories" target="_blank" rel="noopener">Trello repository</a>. Although the user stories do not have explicit links to projects, it can be inferred that the stories originate from some project related to the library of Duke University.</p> <p><code>g17-cask.txt</code> (2016) refers to the Cask Data Application Platform (CDAP). CDAP is an open source application platform (<a href="https://github.com/cdapio/cdap" target="_blank" rel="noopener">GitHub</a>, under Apache License 2.0) that can be used to develop applications within the Apache Hadoop ecosystem, an open-source framework which can be used for distributed processing of large datasets. The user stories are extracted from a document that includes requirements regarding dataset management for Cask 4.0, which includes the scenarios, user stories and a design for the implementation of these user stories. The raw data is available in the following <a href="https://cdap.atlassian.net/wiki/spaces/CE/pages/1595181111/Dataset+Management+User+Stories" target="_blank" rel="noopener">environment</a>.</p> <p><code>g18-neurohub.txt</code> (2012) is concerned with the <a href="https://neurohub.ca/" target="_blank" rel="noopener">NeuroHub platform</a>, a neuroscience data management, analysis and collaboration platform for researchers in neuroscience to collect, store, and share data with colleagues or with the research community. The user stories were collected at a time NeuroHub was still a research project sponsored by the UK Joint Information Systems Committee (JISC). For information about the research project from which the requirements were collected, see the following <a href="https://ora.ox.ac.uk/objects/uuid:df65547e-184a-4a21-b701-9e2a5bc240f4" target="_blank" rel="noopener">record</a>.</p> <p><code>g22-rdadmp.txt</code> (2018) is a collection of user stories from the Research Data Alliance's <a href="https://www.rd-alliance.org/groups/dmp-common-standards-wg/members/all-members/" target="_blank" rel="noopener">working group on DMP Common Standards</a>. Their <a href="https://github.com/RDA-DMP-Common" target="_blank" rel="noopener">GitHub repository</a> contains a collection of user stories that were created by asking the community to suggest functionality that should part of a website that manages data management plans. Each user story is stored as an <a href="https://github.com/RDA-DMP-Common/user-stories/issues" target="_blank" rel="noopener">issue on the GitHub's page</a>. </p> <p><code>g23-archivesspace.txt</code> (2012-2013) refers to ArchivesSpace: an open source, web application for managing archives information. The application is designed to support core functions in archives administration such as accessioning; description and arrangement of processed materials including analog, hybrid, and<br>born digital content; management of authorities and rights; and reference service. The application supports collection management through collection management records, tracking of events, and a growing number of administrative reports. ArchivesSpace is open source and its development is hosted in <a href="https://github.com/archivesspace/archivesspace" target="_blank" rel="noopener">GitHub</a> (Educational Community License, Version 2.0), with existing issues in a <a href="https://archivesspace.atlassian.net/jira/dashboards/last-visited" target="_blank" rel="noopener">board</a>, but the dataset only includes older user stories (not available any more in the board) between August 28, 2012 (the starting date of the community) until February 28, 2013.</p> <p><code>g24-unibath.txt</code> (2013) concerns the development of an institutional data repository for the University of Bath. This need was driven by changes in funder and publisher policy, as well as responses from the recent Research360 data management survey sent out to all University of Bath researchers. The purpose of this would be to provide a long-term archive of our research data, with the following benefits: Ensure long-term availability of data to our researchers; fulfil funder and publisher requirements; enable and track increased impact of our research through data re-use and citation by the wider community; encourage new collaborations and deepen existing relationships with industry; enable new types of research, both within the university and the wider sector. The requirements were identified in 2013 and the original document can be found <a href="https://purehost.bath.ac.uk/ws/portalfiles/portal/230431280/IDR_User_Stories_v1.0.pdf" target="_blank" rel="noopener">online</a>.</p> <p><code>g25-duraspace.txt</code> (2012) is a collection that originates from the development of the Data Dictionary Supplement component of the Data asset management system (DAMS) by DuraSpace (<a href="https://wiki.lyrasis.org/display/FF/Design+-+Audit+Service?preview=%2F68060244%2F68354291%2Fuser-stories.pdf" target="_blank" rel="noopener">original document</a>). DuraSpace, or DSpace, is an active project that can be found <a href="https://dspace.org/" target="_blank" rel="noopener">online</a> and is developed as an <a href="https://github.com/DSpace/DSpace" target="_blank" rel="noopener">open source project</a> (BSD 3.0). DSpace stores, preserves and disseminates digital cultural heritage content by supporting ingestion of digital objects and their metadata; management and curation of digital objects; easy access to the digital objects, by both listing and searching; long-term preservation of the digital objects.</p> <p><code>g26-racdam.txt</code> (2015) refers to a collection of requirements that were found in an online <a href="https://trello.com/b/Ou3OzOjR/rac-dam-user-stories" target="_blank" rel="noopener">Trello board</a> for a so-called RAC DAM system. Very limited information exists about the system, but the stories are organized into multiple epics: rights management, asset management, use, discovery, user management, reporting, curation, description, and preservation. It is possible to infer that the collection refers to an archiving system to be used by archivists and researchers. The online identity of the issue contributors makes us hypothesize this has to do with the Rockefeller Archive Center in New York City.</p> <p><code>g27-culrepo.txt</code> (2014-2015) is an extract of a document constructed by RepoExec, a group who manages multiple repositories and the overall repositories policy of the Cornell University Library (CUL). The document was publicly displayed and was accessible on their <a href="https://confluence.cornell.edu/display/culpublic/Charge" target="_blank" rel="noopener">Confuence website</a> as a <a href="https://confluence.cornell.edu/display/culpublic/IR+User+Stories+Working+Group?preview=/326381875/327639271/Repository_User_Stories_20150114.pdf" target="_blank" rel="noopener">PDF attachment</a>. The user stories in the document focus on a subset of the CUL’s institutional repository (IR) systems. </p> <p><code>g28-zooniverse.txt</code> (2014) originates from MICO – Media In Context - an EU-funded research project to develop an integrated platform for cross-media analysis, metadata publishing, querying and recommendation. The set of US describe in particular two main showcases within the MICO project, with the first one being Zooniverse, a citizen science platform (US27-59). The second showcase that is described by the user stories is InsideOut10. InsideOut10 is a start-up and consulting firm from Italy with extensive experience on media delivery platforms and web publishing (US1-US26). The projects are based on volunteers who have access to the platform and contribute by classifying data such as images, audio and video by performing recognition tasks that cannot easily be performed by a computer. The data has been extracted from a deliverable of the MICO project that is currently available <a href="https://www.mico-project.eu/wp-content/uploads/2016/04/CompendiumUseCaseRequirementsAnalysisDeliverable.pdf" target="_blank" rel="noopener">online</a>.</p> <h3>Information systems for specific domains</h3> <p><code>g12-camperplus.txt</code> (2017) concerns a software application called Camper+ (<a href="https://github.com/Notabela/Camper-Plus" target="_blank" rel="noopener">GitHub</a>, MIT License), which aims to support camp administrators, camp counselors, and parents in the context of camps organized for children. The collection of user stories is retrieved from the project's <a href="https://github.com/Notabela/Camper-Plus/wiki" target="_blank" rel="noopener">wiki</a>, which contains the <a href="https://github.com/Notabela/Camper-Plus/wiki/5.-User-Stories" target="_blank" rel="noopener">user stories</a> and organizes the roles into <a href="https://github.com/Notabela/Camper-Plus/wiki/4.-Personas" target="_blank" rel="noopener">personas</a>.</p> <p><code>g19-alfred.txt</code> (2015) describes a set of requirements from a European project called ALFRED (<a href="https://cordis.europa.eu/docs/projects/cnect/8/611218/080/deliverables/001-D23UserStoriesReportv15.pdf" target="_blank" rel="noopener">Deliverable 2.3</a>), which is about a system that provides support for older people; a “Personal Interactive Assistant for Independent Living and Active Ageing”. One of the main system objectives is to support older people to actively participate in society and act independently. The outputs of this project led to a <a href="https://github.com/ALFREDProject" target="_blank" rel="noopener">GitHub repository</a> (unspecified license).</p> <p><code>g21-badcamp.txt</code> (~2017) is a set of user stories that originates from a <a href="https://github.com/badcamp" target="_blank" rel="noopener">GitHub repository</a> (GPL 2.0 and unspecified licenses) of the <a href="https://www.badcamp.org/" target="_blank" rel="noopener">BADCamp event's website</a>, an annual conference that celebrates Drupal open source websites. The website gives general information about the event. Moreover, it is used as a supportive tool for all attendees. All sorts of features have been added over time to support all attendees of the event. While the original user stories are not available, the <a href="https://github.com/badcamp/camp_distro/issues" target="_blank" rel="noopener">current backlog of the website is accessible</a>.</p> <h3>Examples: first-version websites</h3> <p><code>g10-scrumalliance.txt</code>(2004) is a collection taken from a <a href="https://www.mountaingoatsoftware.com/agile/scrum/scrum-tools/product-backlog/example" target="_blank" rel="noopener">product backlog example</a> that is currently published on the Mountain Goat Software website. As stated on that website, these stories were written to describe the functionality of an early version of the <a href="https://www.scrumalliance.org/" target="_blank" rel="noopener">Scrum Alliance website</a>.</p> <p><code>g13-planningpoker.txt</code> (2010, estimated via the Internet Archive Wayback Machine) is an example -- like <code>g10-scrumalliance.txt</code> -- of a product backlog that is available on the Mountain Goat Software <a href="https://www.mountaingoatsoftware.com/agile/scrum/scrum-tools/product-backlog/example" target="_blank" rel="noopener">website</a>. This refers to the first version of the <a href="https://www.planningpoker.com/" target="_blank" rel="noopener">Planning Poker</a> website, which allows estimators in different locations to estimate collaboratively.</p> <p> </p>
Raw MRI imaging for "In Vivo Neuroprotection in Ischemic Stroke by Activated Protein C Requires β-Arrestin 2"
<p><span>The protease, activated protein C (APC) and its variants provide pharmacological benefits in many murine preclinical injury models, including neuroprotection for ischemic stroke and mortality reduction for sepsis.<span> </span>The <em>in vivo</em> mechanism of action for APC in ischemic stroke and sepsis injury models, similar to extensive in vitro studies using cultured cells, involves protease activated receptor (PAR) 1-mediated biased signaling. Cell culture studies showed that APC/PAR1 signaling requires β-Arrestin 2, an intracellular scaffold protein, and that β-Arrestin 2-dependent, APC-initiated signaling can distinctly alter a wide variety of intracellular signaling pathways.<span> </span>It is unclear whether <em>in vitro</em> studies can be extrapolated to <em>in vivo</em> mechanisms of action.<span> </span>This study employed a proximal transient Middle Cerebral Artery Occlusion model to study the neuroprotective actions of the signaling-selective APC variant, 3K3A-APC, in β-arrestin 2 deficient (<em>Arrb2</em><sup>-/-</sup>) mice. Based on the size and shape of brain injury areas, 3K3A-APC significantly limited brain injury in control mice to a relatively small, localized area whereas these protective effects were lost in <em>Arrb2<sup>-/-</sup></em> mice. Thus, these data indicate that the major <em>in vitro</em> mechanism of action that requires β-arrestin 2 for APC/PAR1 biased signaling is central to the <em>in vivo</em> mechanism of action for APC’s neuroprotection. </span></p>
Data from: Ant-plant mutualism: a dietary by-product of a tropical ant's macronutrient requirements
Many arboreal ants depend on myrmecophytic plants for both food and shelter; in return, these ants defend their host plants against herbivores, which are often insects. Ant-plant and other mutualisms do not necessarily involve the exchange of costly rewards or services; they may instead result from by-product benefits, or positive outcomes that do not entail a cost for one or both partners. Here, we examined whether the plant-ant Allomerus octoarticulatus pays a short-term cost to defend their host plants against herbivores, or whether plant defense is a by-product benefit of ant foraging for insect prey. Because the food offered by ant-plants is usually nitrogen-poor, arboreal ants may balance their diets by consuming insect prey or associating with microbial symbionts to acquire nitrogen, potentially shifting the costs and benefits of plant defense for the ant partner. To determine the effect of ant diet on an ant-plant mutualism, we compared the behavior, morphology, fitness, stable isotope signatures, and gaster microbiomes of A. octoarticulatus ants nesting in Cordia nodosa trees maintained for nearly a year with or without insect herbivores. At the end of the experiment, ants from herbivore exclosures preferred protein-rich baits more than ants in the control (i.e., herbivores-present) treatment. Furthermore, workers in the control treatment were heavier than in the herbivore-exclusion treatment, and worker mass predicted reproductive output, suggesting that foraging for insect prey directly increased ant colony fitness. The gaster microbiome of ants was not significantly affected by the herbivore exclusion treatment. We conclude that the defensive behavior of some phytoecious ants is a by-product of their need for external protein sources; thus, the consumption of insect herbivores by ants benefits both the ant colony and the host plant.
Figure 2 from: Wetzel F, Hoffmann A, Häuser C, Vohland K (2016) 1st EU BON Stakeholder Roundtable (Brussels, Belgium): Biodiversity and Requirements for Policy. Research Ideas and Outcomes 2: e8600. https://doi.org/10.3897/rio.2.e8600
Figure 2 - Discussing policy relevance of biodiversity data at a European scale (credits: MfN).
The dataset of the paper titled "Human Value Requirements in AI Systems: Empirical Analysis of Amazon Alexa"
<p>This package includes the dataset (user reviews) of Amazon Alexa and the corresponding labels of human values used in this paper which was submitted to EmpiRE 2023. It also includes the details of the results with some visualizations.</p>
data for: Inconsistencies Detection in Natural Language Requirements using ChatGPT: a Preliminary Evaluation
<p>Supplementary material for the paper: Inconsistencies Detection in Natural Language Requirements using ChatGPT: a Preliminary Evaluation</p> <p>In the "gold" sheets there are the requirements: originals requirements are marked with "1" in the third column, mutants are marked with "0". </p>
Mobile Health Requirements for Occupational Health Assessment of Health Care Professionals: Delphi Study
<p>Database of answers received in each Delphi Round of our study.</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.