The DOI matches its Crossref record; 25 of the 25 references it cites were found in a registry or an index.
Improving agile requirements: the Quality User Story framework and tool
Open accessAbstract
User stories are a widely adopted requirements notation in agile development. Yet, user stories are too often poorly written in practice and exhibit inherent quality defects. Triggered by this observation, we propose the Quality User Story (QUS) framework, a set of 13 quality criteria that user story writers should strive to conform to. Based on QUS, we present the Automatic Quality User Story Artisan (AQUSA) software tool. Relying on natural language processing (NLP) techniques, AQUSA detects quality defects and suggest possible remedies. We describe the architecture of AQUSA, its implementation, and we report on an evaluation that analyzes 1023 user stories obtained from 18 software companies. Our tool does not yet reach the ambitious 100 % recall that Daniel Berry and colleagues require NLP tools for RE to achieve. However, we obtain promising results and we identify some improvements that will substantially improve recall and precision.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
WordNet: a lexical database for English
Miller, G. A. (1995) · Communications of the ACM · doi:10.1145/219717.219748 · Cited by 14,015 · cited 1×
“AQUSA could implement each of the similarity measures that we outlined in [35] using the WordNet lexical database [40] to detect semantic similarity.”
MethodExtreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,902
The Inmates are Running the Asylum
Cooper, A. (1999) · Berichte des German Chapter of the ACM · doi:10.1007/978-3-322-99786-9_1 · Cited by 1,855
User Stories Applied: For Agile Software Development
Cohn, M. (2004) · Cited by 1,092
Understanding quality in conceptual modeling
Lindland, O. I., Sindre, G., & Solvberg, A. (1994) · IEEE Software · doi:10.1109/52.268955 · Cited by 873
Four dark corners of requirements engineering
Zave, P., & Jackson, M. (1997) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/237432.237434 · Cited by 734
Beck, K. L., & Fowler, M. (2000) · CERN Document Server (European Organization for Nuclear Research) · Cited by 486
Jeffries, R., Anderson, A., & Hendrickson, C. (2000) · Cited by 416
Agile Requirements Engineering Practices: An Empirical Study
Cao, L., & Ramesh, B. (2008) · IEEE Software · doi:10.1109/ms.2008.1 · Cited by 414
System Requirements Engineering
(2020) · System Requirements Engineering · doi:10.1002/9781119751557.ch4 · Cited by 306
Metadata
- Authors
- Lucassen, G., Dalpiaz, F., van der Werf, J. M. E. M., & Brinkkemper, S.
- Venue
- Requirements Engineering
- Published
- 2016-04-01
- Volume
- 21
- Issue
- 3
- Pages
- 383-403
- ISSN
- 0947-3602 (ISSN-L)
- 1432-010X
- OpenAlex
- W2334498876
- Cited by
- 257
- References
- 25
- FWCI
- 41.62
- Type
- journal article
- Language
- en
- Open access
- hybrid
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Improving agile requirements: the Quality User Story framework and tool. https://app.cochat.ai/papers/10.1007/s00766-016-0250-x
- The paper
- Lucassen, G., Dalpiaz, F., van der Werf, J. M. E. M., & Brinkkemper, S. (2016). Improving agile requirements: the Quality User Story framework and tool. Requirements Engineering. https://doi.org/10.1007/s00766-016-0250-x
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.