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.
37
datasets available to search
ShareScore release 0.7.1
Dataset results
37 results for “Requirements Engineering”
Appendices: Requirements Engineering forSoftware-Enabled Art
<p>Interview guides for paper Requirements Engineering forSoftware-Enabled Art</p>
Emergent Solutions on Requirement Engineering for Agile Software Development: A tertiary study (Auxiliary Documentation in PDF)
<p><strong>[Context and motivation]</strong> Agile Software Development (ASD) is a new trend in software development and has become popular. Its advocates claim that ASD is well suited to solving traditional software development problems by valuing human factors over technical ones. However, one of the most critical phases in software development, Requirements Engineering (RE), can be overwhelming for ASD values.<br> <strong>[Question/problem]</strong> Trying to work with RE in a traditional way for ASD can limit ASD's potential. Therefore, it is necessary to investigate what academia and industry have done in RE to exploit all of the capabilities of ASD beyond traditional RE. <br> <strong>[Principal ideas/results]</strong> This work presents an overview of the state-of-the-art Requirement Engineering (RE) for Agile Software Development (ASD). We conducted a Tertiary Study in secondary studies published from 1st January 2015 to 30th June 2021, looking for solutions for RE-ASD using the Systematic Literature Review (SLR) protocol described by Kitchenham and Charters (2007). After executing the SLR protocol, we accepted 37 out of 169 studies and encountered 136 solutions used by academia and industry for RE-ASD. We considered only a few solutions that could be classified as emergent for RE-ASD, 24 out of 106. Furthermore, we cataloged the challenges presented by the emergent solutions (e.g., a steep learning curve due to the lack of experience, process, or culture) that should be addressed. Finally, we identified a possible gap between academia and industry regarding these emerging solutions that need further investigation. <br> <strong>[Contribution]</strong> By highlighting emerging Requirements Engineering (RE) solutions for Agile Software Development (ASD), we made our contribution to help researchers who need to propose new solutions to some of the problems that remain unsolved by pointing out the recent trends for RE for ASD.</p> <p>The repository contains the following:</p> <ul> <li>Auxiliary Documentation in PDF;</li> <li>Dataset from the Tertiary Study - compressed file (refsq2023Complement.zip): <ul> <li> <p><strong>REFSQ2023-ALL-ARTICLES.csv:</strong> is a comma-separated file with all 198 (including the duplicates) found in our search in the digital libraries with their respective status (accepted, rejected, or duplicated).</p> </li> <li> <p><strong>REFSQ2023-DISTINCT-SOLUTIONS.csv:</strong> is a comma-separated file with all the distinct solutions we found in our research. They are classified according to our classification method, explained in the article.</p> </li> <li> <p><strong>REFSQ2023-GOOGLE-TRENDS-RESULTS.csv:</strong> is a comma-separated file with all results of our query in the Google Trends tool. It also brings the used search terms and the code and classification of each solution.</p> </li> </ul> </li> </ul>
Understanding Requirements Engineering Debt: Study Material
<p>This upload contains additional material for the study titled "An initial Theory to Understand and Manage Requirements Engineering Debt in Practice." In detail, the upload contains</p> <ol> <li>the interview protocol as well as the codebook used for coding the interview transcripts,</li> <li>the survey protocol including all survey questions, and</li> <li>an initial attempt at visualizing the resulting theory.</li> </ol> <p>Note that any sensitive data (interview transcripts, survey responses) could not be disclosed.</p>
Assessment of companies' safety processes maturity in requirements engineering with Uni-REPM SCS
<p>Video presentation of the paper "<em>Assessment of companies’ safety processes maturity in requirements engineering with Uni-REPM SCS</em>" to appear at<strong> the Industry Track </strong>of CBSOFT 2020.</p> <p><strong>Abstract.</strong> Safety is an important quality attribute in the development of safety-critical systems (SCS). This attribute can be achieved by improving safety processes maturity to reduce accidents and safety incidents. In this work, we present a safety module called Uni-REPM SCS for the Uni-REPM maturity model. We describe the methodology used to develop the module, how we built and validated it and further research and possibilities of collaboration.</p>
What do LinkedIn Brazilian Ads ask of Requirements Engineers? - Supplementary Material
Open the record for dataset details and reuse information.
Status Quo and Problems of Requirements Engineering for Machine Learning: Results from an International Survey
<p>This folder contains the current data used in the paper named 'Status Quo and Problems of Requirements Engineering for Machine Learning: Results from an International Survey'. We make available a ZIP file containing the survey used, the data collected from it and the Jupyter Notebooks used to build our analysis.</p>
Supplementary Materials of the Tutorial: "Promotion of Open Science in Requirements Engineering: Leveraging the ORKG and ORKG Ask for FAIR Scientific Information"
<h1>Summary</h1> <p>This collection contains all the supplementary materials of the second tutorial titled "<a href="https://conf.researchr.org/details/RE-2025/RE-2025-tutorials/1/Promotion-of-Open-Science-in-Requirements-Engineering-Leveraging-the-ORKG-and-ORKG-A" target="_blank" rel="noopener">Promotion of Open Science in Requirements Engineering: Leveraging the ORKG and ORKG Ask for FAIR Scientific Information</a>", accepted at the <a href="https://conf.researchr.org/home/RE-2025" target="_blank" rel="noopener">33rd IEEE International Requirements Engineering Conference 2025</a>.</p> <p>The materials complement the tutorial sessions and provide participants with resources to enhance their understanding and application of open science principles in the field of Requirements Engineering (RE) by leveraging the <a href="https://orkg.org/" target="_blank" rel="noopener">Open Research Knowledge Graph (ORKG)</a> and <a href="https://ask.orkg.org/" target="_blank" rel="noopener">ORKG Ask</a> for FAIR scientific information. These materials contain all the presentation slides and exercise materials so that everyone can repeat the theoretical presentations independently and carry out the practical exercises themselves at any time.</p> <h1>Contents</h1> <h2>1. Slides - All slides used in the tutorial.</h2> <table> <tbody> <tr> <td><strong>Files</strong></td> <td><strong>Description</strong></td> </tr> <tr> <td>0. RE25 Tutorial - All Sessions.pdf</td> <td>The complete set of all slides used in the tutorial, which are also provided individually for each session of the tutorial.</td> </tr> <tr> <td>1. RE25 Tutorial - Welcome.pdf</td> <td>The welcome with an overview of the content of the tutorial.</td> </tr> <tr> <td>2. RE 25 Tutorial - Introduction to Open Science in RE.pdf</td> <td>The theoretical introduction to open science regarding its importance, benefits, and incentives for researchers themselves and the wider RE community.</td> </tr> <tr> <td>3. RE25 Tutorial - Introduction to ORKG and ORKG Ask.pdf</td> <td>The theoretical introduction to the Open Research Knowledge Graph (ORKG) and ORKG Ask.</td> </tr> <tr> <td>4. RE25 Tutorial - Using SciKGTeX.pdf</td> <td>The practical exercise, with detailed step-by-step instructions on how to use the LaTeX package <a href="https://github.com/Christof93/SciKGTeX" target="_blank" rel="noopener">SciKGTeX</a> to create a FAIR-annotated publication and import it into the ORKG.</td> </tr> <tr> <td>5. RE25 Tutorial - Using the ORKG.pdf</td> <td>The practical exercise, with detailed step-by-step instructions on how to use the <a href="https://orkg.org/" target="_blank" rel="noopener">ORKG </a>to describe publications regarding their scientific information and use these descriptions to create and publish an ORKG comparison.</td> </tr> <tr> <td>6. RE25 Tutorial - Using the ORKG Ask and ORKG CSV Import.pdf</td> <td>The practical exercise, with detailed step-by-step instructions on how to use <a href="https://ask.orkg.org/" target="_blank" rel="noopener">ORKG Ask</a> and the <a href="https://orkg.org/" target="_blank" rel="noopener">ORKG</a> CSV Import to describe publications regarding their scientific information and use these descriptions to create and publish an ORKG comparison.</td> </tr> <tr> <td>7. RE25 Tutorial - Reflection and Closing.pdf</td> <td>The summary, reflection, and closing of the tutorial with an outlook to the future of <a href="https://gitlab.com/TIBHannover/orkg/ExtracTable" target="_blank" rel="noopener">ExtracTable</a>.</td> </tr> </tbody> </table> <h2>2. Exercise Materials - All exercise materials used in the tutorial.</h2> <h3>2.1 SciKGTeX Materials</h3> <table> <tbody> <tr> <td><strong>Folder</strong></td> <td><strong>Description</strong></td> </tr> <tr> <td>SciKGTeX_Example</td> <td> <p>The folder contains an example publication and all required SciKGTeX files for annotating the scientific information.</p> <p>Files:</p> <ol> <li>example.tex : LaTeX file of the example publication.</li> <li>scikgtex.lua : Required LaTeX package file for using SciKGTeX.</li> <li>scikgtex.sty : Required LaTeX package file for using SciKGTeX.</li> <li>project.zip : Zip file containing all above files for uploading as a project in Overleaf.</li> </ol> <p><em>Remark:</em> SciKGTeX is constantly being further developed. For the latest version of the required files, please refer to the corresponding <a href="https://github.com/Christof93/SciKGTeX" target="_blank" rel="noopener">GitHub project</a>.</p> </td> </tr> <tr> <td>SciKGTeX_Solution</td> <td> <p>The folder contains an Overleaf project with the solution for a possible annotation of the example publication provided.</p> <p>Files:</p> <ol> <li>example.pdf : PDF with annotations embedded into the PDF's XMP metadata.</li> <li>example.tex : LaTeX file of the example publication with annotations.</li> <li>output.xmp_metadata.xml : XMP file generated by SciKGTeX to check the annotations created.</li> <li>scikgtex.lua : Required LaTeX package file for using SciKGTeX.</li> <li>scikgtex.sty : Required LaTeX package file for using SciKGTeX.</li> <li>project.zip : Zip file containing all above files for uploading as a project in Overleaf.</li> </ol> <p><em>Remark:</em> SciKGTeX is constantly being further developed. For the latest version of the required files, please refer to the corresponding <a href="https://github.com/Christof93/SciKGTeX" target="_blank" rel="noopener">GitHub project</a>.</p> </td> </tr> </tbody> </table> <h3>2.2 ORKG Materials</h3> <table> <tbody> <tr> <td><strong>Folder</strong></td> <td><strong>Description</strong></td> </tr> <tr> <td>ORKG_Exemplary_Comparison</td> <td> <p>The folder contains a created ORKG comparison as a PDF and PNG file, consisting of 4 exemplary publications that were described with the ORKG template provided for the tutorial.</p> </td> </tr> <tr> <td>ORKG_Exemplary_Publications</td> <td> <p>The folder contains 20 PDF files with short summaries of scientific findings on empirical research practices from 20 different publications of the IEEE International Requirements Engineering Conference. The participants have received these PDFs to enter them in the ORKG and then create an ORKG Comparison.</p> <p><em>Remark:</em> We have provided the short summaries instead of the full publications to simplify the extraction process due to time constraints.</p> </td> </tr> <tr> <td>ORKG_Template</td> <td> <p>The folder contains an overview of the ORKG template used in the tutorial as a PNG file and an N3 file of its RDF structure.</p> </td> </tr> </tbody> </table> <h3>2.3 ORKG Ask & ORKG CSV Import Materials</h3> <table> <tbody> <tr> <td><strong>File</strong></td> <td><strong>Description</strong></td> </tr> <tr> <td>empty_orkg_csv_file_for_orkg_csv_import.csv</td> <td> <p>The file contains an empty template for creating an ORKG CSV file for the ORKG CSV Import with own content.</p> </td> </tr> <tr> <td>empty_orkg_csv_file_for_orkg_csv_import.xlsx</td> <td> <p> </p> The file contains an empty template for creating an ORKG CSV file for the ORKG CSV Import with own content. <p> </p> </td> </tr> <tr> <td>orkg_ask_synthesized_answer_and_link_to search.txt</td> <td>The file contains the synthesized answer with references from ORKG Ask for the question "What is the state of the art in empirical research applied in requirements engineering?" with a link to the associated saved search.</td> </tr> <tr> <td>original_orkg_ask_export_for_orkg_csv_import.csv</td> <td> <p>The file contains the original content of an exported ORKG Ask result table that is revised in the tutorial to create an ORKG Comparison using the ORKG CSV Import.</p> </td> </tr> <tr> <td>original_orkg_ask_export_for_orkg_csv_import.xlsx</td> <td> <p>The file contains the original content of an exported ORKG Ask result table that is revised in the tutorial to create an ORKG Comparison using the ORKG CSV Import.</p> </td> </tr> <tr> <td>revised_orkg_ask_export_for_orkg_csv_import.csv</td> <td> <p>The file contains the revised content of an exported ORKG Ask result table that is used in the tutorial to create an ORKG Comparison using the ORKG CSV Import.</p> </td> </tr> <tr> <td>revised_orkg_ask_export_for_orkg_csv_import.xlsx</td> <td> <p>The file contains the revised content of an exported ORKG Ask result table that is used in the tutorial to create an ORKG Comparison using the ORKG CSV Import.</p> </td> </tr> </tbody> </table> <h1>Usage Notes</h1> <p>These materials are intended for use by the participants of the tutorial, the broader RE community, and everyone interested in open science. They are provided to support the long-term transition towards FAIR scientific information and to empower researchers to integrate open science infrastructures into their work.</p> <h1>License</h1> <p>The materials are released under <a href="https://creativecommons.org/licenses/by/4.0/" target="_blank" rel="noopener">Creative Commons Attribution 4.0 International (CC BY 4.0) license</a>, allowing for reuse and distribution in accordance with open science practices.</p>
Engineering the thermotolerant industrial yeast Kluyveromyces marxianus for anaerobic growth ssing sterol requirements enables anaerobic growth of the thermotolerant yeast Kluyveromyces marxianus
GEO Series GSE164344. Kluyveromyces marxianus; Saccharomyces cerevisiae. 18 samples. Type: Expression profiling by high throughput sequencing.
Engineered mammalian RNAi can elicit antiviral protection that negates the requirement for the interferon response
GEO Series GSE73698. Mus musculus. 12 samples. Type: Expression profiling by high throughput sequencing.
Engineering epigenetic memory requires co-targeting of histone methylatransferases and DNA methylatransferases [Methylation]
GEO Series GSE123830. Homo sapiens. 8 samples. Type: Methylation profiling by array.
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>
Minimal requirements for the epigenetic inheritance of engineered silent chromatin domains
GEO Series GSE236173. Saccharomyces cerevisiae. 21 samples. Type: Genome binding/occupancy profiling by high throughput sequencing.
Engineering epigenetic memory requires co-targeting of histone methylatransferases and DNA methylatransferases
GEO Series GSE123885. Homo sapiens. 15 samples. Type: Methylation profiling by array; Genome binding/occupancy profiling by high throughput sequencing.
Raw Data for the Literature Review on the Requirements Engineering tools
Open the record for dataset details and reuse information.
Who Uses Personas in Requirements Engineering: The Practitioners' Perspective
<p>Include interview and survey questions and ethic approval.</p>
Engineering epigenetic memory requires co-targeting of histone methylatransferases and DNA methylatransferases [ChIP-seq]
GEO Series GSE123882. Homo sapiens. 7 samples. Type: Genome binding/occupancy profiling by high throughput sequencing.
Towards Requirements in Systems Engineering for Aerospace IVHM Design
Health management (HM) technologies have been employed for safety critical system for decades, but a coherent systematic process to integrate HM into the system design is not yet clear. Consequently, in most cases, health management resorts to be an after-thought or ‘band-aid’ solution. Moreover, limited guidance exists for carrying out systems engineering (SE) on the subject of writing requirements for designs with integrated vehicle health management (IVHM). It is well accepted that requirements are key to developing a successful IVHM system right from the concept stage to development, verification, utilization, and support. However, writing requirements for systems with IVHM capability have unique challenges that require the designers to look beyond their own domains and consider the constraints and specifications of other interlinked systems. In this paper we look at various stages in the SE process and identify activities specific to IVHM design and development. More importantly, several relevant questions are posed that system engineers must address at various design and development stages. Addressing these questions should provide some guidance to systems engineers towards writing IVHM related requirements to ensure that appropriate IVHM functions are built into the system design
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.