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.
138
datasets available to search
ShareScore release 0.7.1
Dataset results
138 results for “Requirement Specification”
Four Essential Components for FAIR Data: Capability & Category-Specific Requirements
<p>Adapted from Bailo (2019) and Peng (2023), this diagram illustrates FAIR requirements specific to data, metadata, and infrastructure, aligned with the definitions of individual FAIR principles. It highlights the critical role of enterprise capabilities—including processes, systems, standards, tools, and skills—in supporting FAIR data. These four components are essential for systematically enhancing the overall FAIRness of an organization's scientific data collection</p> <p> </p>
IMAGS II Requirements Specification
<p>This repository contains the IMAGS II requirements specificiation described in "Din, C. Y., & Rine, D. C. (2013). Requirements Statements Content Goodness and Complexity Measurement. International Journal of Next-Generation Computing, 4(1)."</p>
Supplementary Material for Documentation artifacts for conversation-related requirements specification in chatbots: a systematic review and a meta-model proposal
<p>This is a supplementary data of the tertiary systematic literature review conducted in the paper "Conversation-related requirements specification in chatbots: a systematic review and a meta-model proposal".</p> <p>Context: Chatbots are complex applications due to their capacity to engage and maintain a conversation with humans. However, the conversational-related requirements of chatbots are hard to elicit, document, and test. Another challenge is the documentation since there are not so many directions on how to register and test subjective requirements.</p> <p>Methods: We followed systematic literature review (SLR) guidelines and identified 42 relevant papers that address the artifacts used by practitioners to document conversational-related requirements in literature. We also investigated what conversational requirements are addressed in requirements documentation.</p> <p>Results: The main results indicate that UML diagrams, prototypes, tables of requirements, conversational flows, and scenarios are present in most chatbot documentation. Except for UML diagrams, those artifacts are used to document standard requirements or conversational requirements. In those artifacts, context-dependent behavior, assertivity, error handling, and human-like attitude are the most approached conversational requirements in the studies. In sequence, based on our findings, we propose the conversational integrated map, a meta-model solution as documentation of conversational requirements.</p>
VReqST - Requirement Specification Tool Support for Virtual Reality Products
<p>Virtual Reality (VR) Environments are challenging to build with discrete and incremental requirements. VR practitioners often need human assistance to achieve product completeness, as most VR requirements are either abstract or under specified. The slightest change to these requirement specifications tends to drastically impact the overall control-flow of the product. It exponentially increases the development cost. To address the completeness of specifying VR product requirements, we introduce VReqST, a tool for specifying requirements for VR software products. We use role base model template of bare-minimum VR Software to auto-provision all dimensions of VR as a domain on specifying VR product requirements. This tool avoids ambiguity while specifying requirements and provides seamless VR product development.</p>
Artifacts: An Approach for Reviewing Security Related Apects in Agile Requirements Specifications of Web Applications
<p>Abstract—Defects in requirements specifications can have severe consequences during the software development lifecycle. Some of them result in overall project failure due to incorrect or missing quality characteristics. Security is one of those uality characteristics that need to be considered in early phases. There are several concerns that make security difficult to deal with; for instance, (1) when stakeholders discuss general requirements in (review) meetings, they are often not aware that they should also discuss security-related topics, and in the rather rare cases they are aware (2), they typically do not have sufficient security expertise. This picture is even more challenging in agile development contexts, where lightweight documentation are typically involved. To address these issues, we designed an approach that considers user stories and security specifications as input and relates those user stories to security properties via Natural Language Processing (NLP) techniques. Based on the related security properties, our approach then identifies high-level security requirements from the Open Web Application Security Project (OWASP) to be verified afterwards. In a last step, the verification of the generated security requirements is then conducted via a focused reading technique. We finally validate our approach via a controlled experiment comparing the effectiveness and efficiency of novice inspectors (we used two different groups of students) verifying security aspects in agile requirements using our generated reading techniques against using the complete list of OWASP high level security requirements and a the same list of defect types embedded in our technique. The (statistically significant) results indicate that using the reading technique has a positive impact (with large effect size) on the performance of inspectors in terms of effectiveness and efficiency. </p> <p>This repository also contains:</p> <p>Artifacts used and results of the experimental study of the paper entitled "An Approach for Reviewing Security Related Apects in Agile Requirements Specifications of Web Applications".</p>
Software Requirements Specifications from the RE@UTS Group
<p>This repository contains a list of requirements specifications procured by the requirements engineering laboratory at the University of Technology Sydney (RE@UTS) for reuse in research. These artifacts represent a diverse set of domains and formats, offering a heterogeneous benchmark for studies in requirements engineering.</p>
Early Requirements Traceability with Domain-Specific Taxonomies - A Pilot Experiment
<p>Experiment instrumentation (code), raw data, and R analysis scripts.</p> <p>Github repository: https://github.com/munterkalmsteiner/inception/tree/CoClassRecommender</p>
Controlled Experiment in Crosscutting Concerns Identification from Software Requirements Specification
<p>The concern is a group of requirements with the same purpose, which are known as crosscutting concerns when they are scattered and tangled in the system. Identifying and separating these concerns is a matter of huge importance to software maintainability and evolution. For this, some approaches are proposed. There are few experimental studies comparing and analyzing these approaches in detail. In this paper, our aim is to provide empirical evidence about two approaches in this context. We conducted a controlled experiment to compare the effectiveness of two approaches, which identify crosscutting concerns in the requirements specification, followed by an assessment of its perceived utility and ease of use. Our results indicate that, in this given context and planned scenario, there are significant differences between the effectiveness of ObasCId and Theme/Doc approaches.</p>
Deccan region, Madras, India. Genus Vandeleuria is masculine, so widely used specific name oleracea has been changed for gender agreement. Vandeleuria oleraceusis possibly a composite of species. Polytypic, but subspecific taxonomy requires reassessment. Distribution. Widespread in S Asia (India, Nepal, Bhutan, Bangladesh, and Sri Lan-ka), S China (W & S Yunnan), and mainland SE Asia N of the Isthmus of Kra. Descriptive notes. Head-body 68 mm, tail 105 mm, ear 13 mm, hindfoot 17 mm; weight 10 g. The Indomalayan Long-tailed Climbing Mouse is small, with flat nail on outer finger and outertoe; tail is slender, brown, twice as long as head-body length, and lacks distal tuft. Dorsal pelageis silky and salmon in color; venter is white, with fulvous hues. Habitat. Tall cane and tangled vines in primary and secondary forest such as bamboo forest, moist deciduous forest, temperate forests, montane wet zone, and disturbed secondary forests, and perhaps agricultural areas at elevations of 150-1500 m. Food and Feeding. Indomalayan [Long-tailed Climbing Mice eat fruits, buds, and flowers. Breeding. Litters of the Indomalayan Long-tailed Climbing Mouse have 3-6 young. Activity patterns. Indomalayan Long-tailed Climbing Mice are arboreal and nocturnal, although one individual was caught duringthe day. Movements, Home range and Social organization. Indomalayan Long-tailed Climbing Mice build nests in tall bushes or cane to rear their young. Status and Conservation. Classified as Least Concern on The IUCN Red Last (as V. olacea). The Indomalayan Long-tailed Climbing Mouse occurs in several habitats and a wide distribution that includes national parks. Further taxonomical studies are required to assess conservation status ofthis potentially diverse species complex. Bibliography. Corbet & Hill (1992), Dang Huy Huynh et al. (1994), Ellerman (1941), Marshall (1977b), Musser & Carleton (2005), Osgood (1932), Phillips (1980), Wang Yingxiang (2003). in Muridae
Deccan region, Madras, India. Genus Vandeleuria is masculine, so widely used specific name oleracea has been changed for gender agreement. Vandeleuria oleraceusis possibly a composite of species. Polytypic, but subspecific taxonomy requires reassessment. Distribution. Widespread in S Asia (India, Nepal, Bhutan, Bangladesh, and Sri Lan-ka), S China (W & S Yunnan), and mainland SE Asia N of the Isthmus of Kra. Descriptive notes. Head-body 68 mm, tail 105 mm, ear 13 mm, hindfoot 17 mm; weight 10 g. The Indomalayan Long-tailed Climbing Mouse is small, with flat nail on outer finger and outertoe; tail is slender, brown, twice as long as head-body length, and lacks distal tuft. Dorsal pelageis silky and salmon in color; venter is white, with fulvous hues. Habitat. Tall cane and tangled vines in primary and secondary forest such as bamboo forest, moist deciduous forest, temperate forests, montane wet zone, and disturbed secondary forests, and perhaps agricultural areas at elevations of 150-1500 m. Food and Feeding. Indomalayan [Long-tailed Climbing Mice eat fruits, buds, and flowers. Breeding. Litters of the Indomalayan Long-tailed Climbing Mouse have 3-6 young. Activity patterns. Indomalayan Long-tailed Climbing Mice are arboreal and nocturnal, although one individual was caught duringthe day. Movements, Home range and Social organization. Indomalayan Long-tailed Climbing Mice build nests in tall bushes or cane to rear their young. Status and Conservation. Classified as Least Concern on The IUCN Red Last (as V. olacea). The Indomalayan Long-tailed Climbing Mouse occurs in several habitats and a wide distribution that includes national parks. Further taxonomical studies are required to assess conservation status ofthis potentially diverse species complex. Bibliography. Corbet & Hill (1992), Dang Huy Huynh et al. (1994), Ellerman (1941), Marshall (1977b), Musser & Carleton (2005), Osgood (1932), Phillips (1980), Wang Yingxiang (2003).
A Model-driven and Template-based Approach for Requirements Specification : Case studies
<p>This dataset includes the requirements specified using our templates as part of our case studies :</p> <ol> <li>ARINC-653 case study : Time management requirements.</li> <li>ARINC-653 case study : Intra-partition communication requirements.</li> <li>AUTOSAR case study : Crypto service manager requirements.</li> <li>Traditional software case study : Requirements from Kaggle.</li> </ol>
Artifacts: An Efficient Approach for Reviewing Security-Related Aspects in Agile Requirements Specifications of Web Applications
<p><strong>Abstract:</strong> Defects in requirements specifications can have severe consequences during the software development lifecycle. Some of them result in time and cost overruns due to incorrect or missing quality characteristics, such as security. This characteristic requires special attention in web applications because they have become a target for manipulating sensible data. Several concerns make security difficult to deal with. For instance, (1) when stakeholders discuss general requirements they are often unaware that they should also discuss security-related aspects, because (2) they typically do not have enough expertise in security. This often leads to unspecified or ill-defined security requirements. These concerns become even more challenging in agile contexts, where lightweight documentation is typically produced. To tackle this problem, we designed an approach for reviewing security-related aspects in agile requirements specifications of web applications. Our proposal considers user stories and security specifications as inputs and relates those user stories to security properties via Natural Language Processing. Based on the related security properties, our approach identifies high-level security requirements from the Open Web Application Security Project (OWASP) to be verified, and generates a reading technique to support reviewers in detecting defects. We evaluate our approach via three experiment trials conducted with 56 novice software engineers, measuring effectiveness, efficiency, usefulness, and ease of use. We compare our approach against using: (1) the OWASP high-level security requirements, and (2) a perspective-based approach as proposed in contemporary state of the art. The results strengthen our confidence that using our approach has a positive impact (with large effect size) on the performance of inspectors in terms of effectiveness and efficiency.</p> <p>The files below contains the following data:</p> <p><strong>1) Consent form.docx</strong>: This document provides to the research subjects information to decide whether to participate in a research study or not based on an explanation of the proposed research and the nature of the participation that is requested of them.</p> <p><strong>2) Characterization_Questionnaire.docx:</strong> This document shows the questions used to characterize the working experience and knowledge of the participants of the controlled experiment. The answers obtained through this questionnaire allowed us to identify some key characteristics about three knowledge areas: Agile Software Development, Software Security and Software Inspection.</p> <p><strong>3) Experiment_Results.xlsx: </strong>This Excel document shows a summary of the results of the experiments by participant ID, trial and technique. It also synthesizes the defects found by the reviewers and the characterization, follow up and TAM questionnaire. </p> <p><strong>4) FollowUp_Questionnaire_AdHoc_Technique.docx: </strong>This document shows the questions used to acquire information about the review conducted by inspectors who used the ad hoc technique.</p> <p><strong>5) FollowUp_Questionnaire_Reading_Technique.docx: </strong>This document shows the questions used to acquire information about the review conducted by inspectors who used the proposed reading technique. </p> <p><strong>6) Repository of Keywords.docx: </strong>This document shows the keywords used by our proposed approach and that indicate some security concern. </p> <p><strong>7) Task_description_AdHoc_A.docx: </strong>This document shows textual instructions on how to follow the ad hoc review for a set of user stories. </p> <p><strong>8) Task_description_AdHoc_B.docx: </strong>This document shows textual instructions on how to follow the ad hoc review for another set of user stories.</p> <p><strong>9) Task_description_RT_A.docx: </strong>This document shows textual instructions on how to follow the proposed reading technique for a set of user stories.</p> <p><strong>10) Task_description_RT_B.docx: </strong>This document shows textual instructions on how to follow the proposed reading technique for another set of user stories.<strong> </strong></p> <p><strong>11) Training_Experiment.pptx: </strong>This document contains the material used to explain the topics involved in the experiment. It was used to train the subjects. </p>
Data from: High specificity in circulating tumor cell identification is required for accurate evaluation of programmed death-ligand 1
Background: Expression of programmed-death ligand 1 (PD-L1) in non-small cell lung cancer (NSCLC) is typically evaluated through invasive biopsies; however, recent advances in the identification of circulating tumor cells (CTCs) may be a less invasive method to assay tumor cells for these purposes. These liquid biopsies rely on accurate identification of CTCs from the diverse populations in the blood, where some tumor cells share characteristics with normal blood cells. While many blood cells can be excluded by their high expression of CD45, neutrophils and other immature myeloid subsets have low to absent expression of CD45 and also express PD-L1. Furthermore, cytokeratin is typically used to identify CTCs, but neutrophils may stain non-specifically for intracellular antibodies, including cytokeratin, thus preventing accurate evaluation of PD-L1 expression on tumor cells. This holds even greater significance when evaluating PD-L1 in epithelial cell adhesion molecule (EpCAM) positive and EpCAM negative CTCs (as in epithelial-mesenchymal transition (EMT)). Methods: To evaluate the impact of CTC misidentification on PD-L1 evaluation, we utilized CD11b to identify myeloid cells. CTCs were isolated from patients with metastatic NSCLC using EpCAM, MUC1 or Vimentin capture antibodies and exclusion-based sample preparation (ESP) technology. Results: Large populations of CD11b+CD45lo cells were identified in buffy coats and stained non-specifically for intracellular antibodies including cytokeratin. The amount of CD11b+ cells misidentified as CTCs varied among patients; accounting for 33–100% of traditionally identified CTCs. Cells captured with vimentin had a higher frequency of CD11b+ cells at 41%, compared to 20% and 18% with MUC1 or EpCAM, respectively. Cells misidentified as CTCs ultimately skewed PD-L1 expression to varying degrees across patient samples. Conclusions: Interfering myeloid populations can be differentiated from true CTCs with additional staining criteria, thus improving the specificity of CTC identification and the accuracy of biomarker evaluation.
Supplementary material 3 from: Nelufule T, Robertson MP, Wilson JRU, Faulkner KT (2022) Native-alien populations—an apparent oxymoron that requires specific conservation attention. NeoBiota 74: 57-74. https://doi.org/10.3897/neobiota.74.81671
File S3
Supplementary material 2 from: Nelufule T, Robertson MP, Wilson JRU, Faulkner KT (2022) Native-alien populations—an apparent oxymoron that requires specific conservation attention. NeoBiota 74: 57-74. https://doi.org/10.3897/neobiota.74.81671
File S2
Supplementary material 1 from: Nelufule T, Robertson MP, Wilson JRU, Faulkner KT (2022) Native-alien populations—an apparent oxymoron that requires specific conservation attention. NeoBiota 74: 57-74. https://doi.org/10.3897/neobiota.74.81671
File S1
Data for: Aggregation in an heterospecific population of blowfly larvae: social behaviour is impacted by species-specific thermal requirements and settlement order
<p><span>Larvae of several blow fly species grow on carcasses and actively aggregate together. They face harsh developmental conditions resulting in a strong pressure to reduce development time: this is achieved either through thermoregulation or aggregation. We investigate how these two developmental strategies are modulated within heterospecific groups. In the first experiment, larvae of two species with different thermal requirements were deposited simultaneously on a thermal gradient. This resulted in the formation of two monospecific groups, each located at the species-specific thermal preferendum. However, when <em>Calliphora</em> <em>vomitoria</em> (Linnaeus) larvae were placed first, the later coming <em>Lucilia</em> <em>sericata</em> (Meigen) larvae attracted the whole group to its own thermal preferendum. In the reverse experiment, a half of the replicates resulted in single dense heterospecific groups observed at temperatures ranging from <em>C. vicina</em> to <em>L. sericata</em> preferendum. The other half of the replicates resulted in loose groups spread out on the thermal gradient. These results highlight the emergence of collective decisions ranging from thermal optimization to heterospecific aggregation at suboptimal temperatures. They demonstrate that species settlement order strongly affects self-organization processes and mixed-species group formation. We conclude that thermal optimization and heterospecific niche construction are two developmental strategies of carrion fly larvae.</span></p>
Data from: FOXP2 exhibits neuron class specific expression, but is not required for multiple aspects of cortical histogenesis
Open the record for dataset details and reuse information.
Data from: High specificity in circulating tumor cell identification is required for accurate evaluation of programmed death-ligand 1
Open the record for dataset details and reuse information.
Data for: Aggregation in an heterospecific population of blowfly larvae: social behaviour is impacted by species-specific thermal requirements and settlement order
Open the record for dataset details and reuse information.
A pioneer protein encoded by required to maintain repression2 facilitates locus-specific paramutation in Zea mays
GEO Series GSE37204. Zea mays. 2 samples. Type: Non-coding RNA profiling by high throughput sequencing.
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.