System disruptions
We are currently experiencing disruptions on the search portals due to high traffic. We are working to resolve the issue, you may temporarily encounter an error message.
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Requirements quality research artifacts: Recovery, analysis, and management guideline
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-3995-6125
University of Hamburg, Germany.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0002-0679-4361
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-4118-0952
Show others and affiliations
2024 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 216, article id 112120Article in journal (Refereed) Published
Abstract [en]

Requirements quality research, which is dedicated to assessing and improving the quality of requirements specifications, is dependent on research artifacts like data sets (containing information about quality defects) and implementations (automatically detecting and removing these defects). However, recent research exposed that the majority of these research artifacts have become unavailable or have never been disclosed, which inhibits progress in the research domain. In this work, we aim to improve the availability of research artifacts in requirements quality research. To this end, we (1) extend an artifact recovery initiative, (2) empirically evaluate the reasons for artifact unavailability using Bayesian data analysis, and (3) compile a concise guideline for open science artifact disclosure. Our results include 10 recovered data sets and 7 recovered implementations, empirical support for artifact availability improving over time and the positive effect of public hosting services, and a pragmatic artifact management guideline open for community comments. With this work, we hope to encourage and support adherence to open science principles and improve the availability of research artifacts for the requirements research quality community. © 2024 The Author(s)

Place, publisher, year, edition, pages
Elsevier, 2024. Vol. 216, article id 112120
Keywords [en]
Artifact, Availability, Bayesian data analysis, Guideline, Requirements engineering, Data handling, Defects, Engineering research, Quality control, Recovery, Artifact management, Artifact recovery, Data set, Open science, Recovery management, Requirement engineering, Research artefacts, Information analysis
National Category
Computer Sciences
Identifiers
URN: urn:nbn:se:bth-26537DOI: 10.1016/j.jss.2024.112120ISI: 001253392200001Scopus ID: 2-s2.0-85195572538OAI: oai:DiVA.org:bth-26537DiVA, id: diva2:1876182
Part of project
SERT- Software Engineering ReThought, Knowledge Foundation
Funder
Knowledge Foundation, 20180010Available from: 2024-06-24 Created: 2024-06-24 Last updated: 2025-01-16Bibliographically approved
In thesis
1. Good-Enough Requirements Engineering
Open this publication in new window or tab >>Good-Enough Requirements Engineering
2025 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

Background: High-quality requirements are considered crucial for successful software development endeavors as the requirements' purpose is to inform subsequent activities like implementation or testing. Requirements quality defects have been shown to incur significant costs for remediation, scaling up even to project failure. At the same time, the effort to improve the quality of requirements must be justified. Organizations developing software, therefore, need to understand when their requirements artifacts are of "good enough'' quality, i.e., they need to be able to identify the optimum between over- and under-engineering.

Problem: The body of knowledge in requirements quality does not yet offer solutions that would allow organizations to identify that optimum due to three shortcomings: (1) there is no generally accepted, theoretical foundation to describe requirements quality that can serve as a basis to coordinate distributed research efforts and the synthesis of evidence in the field, (2) the scientific practice currently applied in the field is of limited rigor to draw reliable conclusions from existing empirical contributions, and (3) the field lacks empirical evidence that can be aggregated to form a holistic view of requirements quality. These are potential causes for the lack of adoption of requirements quality research in practice.

Goal: In this cumulative, publication-based thesis, we address these three shortcomings and aim to contribute to a more evidence-based approach to requirements quality research grounded in scientific theory.

Method: First, we develop a theoretical foundation by adopting and integrating existing software engineering theories. Second, we evaluate the state of the art of data analysis and open science in the field and provide guidelines to improve these practices. Third, we demonstrate the application of these guidelines and conduct a controlled experiment to contribute additional empirical evidence to the field.

Results: The resulting set of analytical theories specifies requirements quality and provides a structure for future empirical contributions. Our evaluation of the state of the art shows both the need for a common theoretical foundation as well as support for applying rigorous research practices. Our empirical studies contribute to these needs and illustrate the complexity of the impact that requirements quality defects have on subsequent activities. Finally, we develop a method for the effective aggregation of empirical results.

Conclusion: Our theoretical, methodological, and empirical contributions help to coordinate a productive and constructive research agenda on requirements quality that is based on evidence and grounded in theory. This allows for rigorous and practically relevant research that ultimately informs organizations on how to engineer good-enough requirements.

Place, publisher, year, edition, pages
Karlskrona: Blekinge Tekniska Högskola, 2025. p. 257
Series
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 2025:03
Keywords
Requirements Engineering, Requirements Artifacts, Requirements Quality
National Category
Software Engineering
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-27382 (URN)978-91-7295-496-0 (ISBN)
Public defence
2025-02-28, J1630, Karlskrona, 13:00 (English)
Opponent
Supervisors
Available from: 2025-01-17 Created: 2025-01-16 Last updated: 2025-02-06Bibliographically approved

Open Access in DiVA

fulltext(1276 kB)85 downloads
File information
File name FULLTEXT01.pdfFile size 1276 kBChecksum SHA-512
bbd3e3d99226530f3d41fcdc3f0e5153ea71e0013bfc2d4f57acfa40d6f48af3320c467050bdb9c563104a15243548a49f86dbc9926cbd2fb29f8daebbf65702
Type fulltextMimetype application/pdf

Other links

Publisher's full textScopus

Authority records

Frattini, JulianFucci, DavideUnterkalmsteiner, MichaelMendez, Daniel

Search in DiVA

By author/editor
Frattini, JulianFucci, DavideUnterkalmsteiner, MichaelMendez, Daniel
By organisation
Department of Software Engineering
In the same journal
Journal of Systems and Software
Computer Sciences

Search outside of DiVA

GoogleGoogle Scholar
Total: 87 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 491 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf