The DOI matches its Crossref record.
A multi-case study of agile requirements engineering and the use of test cases as requirements
Open accessOverview
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.
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
This complexity in managing quality requirements has also been observed in the context of another agile RE practice, namely the one of using test cases as requirements.
“This complexity in managing quality requirements has also been observed in the context of another agile RE practice, namely the one of using test cases as requirements (Bjarnason et al. 2016).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bjarnason et al. 2016
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
No references could be resolved yet.
Research works printed but not linked: 24
- Bjarnason, 2014, Challenges and practices in aligning requirements with verification and validation: a case study of six companies, Empir. Softw. Eng., 19, 1809, 10.1007/s10664-013-9263-y · DOI
- Bjarnason, 2015, The role of distances in requirements communication: a case study, Requirements Eng. J., 10.1007/s00766-015-0233-3 · DOI
- Causevic, 2011, Factors limiting industrial adoption of test driven development: a systematic review, 337
- Eisenhardt, 2007, Theory building from cases: opportunities and challenges, Acad. Manage. J., 50, 25, 10.5465/AMJ.2007.24160888 · DOI · Paper page
- George, 2004, A structured experiment of test-driven development, Inf. Softw. Technol., 46, 337, 10.1016/j.infsof.2003.09.011 · DOI
- Haugset, 2008, Automated acceptance testing: a literature review and an industrial case study, 27
- Heitmeyer, 1996, Automated consistency checking of requirements specifications, ACM Trans. Softw. Eng. Methodol., 5, 231, 10.1145/234426.234431 · DOI
- Hsia, 1997, Software requirements and acceptance testing, Ann. Softw. Eng., 3, 291, 10.1023/A:1018938021528 · DOI
- Latorre, 2014, A successful application of a test-driven development strategy in the industrial environment, Empirical Softw. Eng., 19, 753, 10.1007/s10664-013-9281-9 · DOI
- Lawson, 1994, A survey of concurrent engineering, Concurrent Eng., 2, 10.1177/1063293X9400200101 · DOI
- Layman, 2006, Motivations and measurements in an agile case study, J. Syst. Archit., 52, 654, 10.1016/j.sysarc.2006.06.009 · DOI
- Lethbridge, 2003, How software engineers use documentation: the state of the practice, IEEE Softw., 20, 35, 10.1109/MS.2003.1241364 · DOI
- Martin, 2008, Tests and requirements, requirements and tests: a Möbius strip, IEEE Softw., 25, 54, 10.1109/MS.2008.24 · DOI
- Miller, 2012, A case study in model-based testing of specifications and implementations, Softw. Test. Verification Reliability, 22, 33, 10.1002/stvr.431 · DOI
- Morris, 2001, Software component certification, Computer, 34, 30, 10.1109/2.947086 · DOI
- Mugridge, 2008, Managing agile project requirements with storytest-driven development, IEEE Softw., 25, 68, 10.1109/MS.2008.11 · DOI
- Park, 2010, A literature review on story test driven development, 208
- Ramesh, 2010, Agile requirements engineering practices and challenges: an empirical study, Inf. Syst. J., 20, 449, 10.1111/j.1365-2575.2007.00259.x · DOI
- Runeson, 2006, A survey of unit testing practices, IEEE Softw., 23, 22, 10.1109/MS.2006.91 · DOI
- Sommerville, 2005, Integrated requirements engineering: a tutorial, IEEE Softw., 22, 16, 10.1109/MS.2005.13 · DOI
- Stapel, 2014, Managing knowledge on communication and information flow in global software projects, Expert Syst., 31, 234, 10.1111/exsy.649 · DOI
- Whittaker, 2000, What is software testing? And why is it so hard?, IEEE Softw., 17, 70, 10.1109/52.819971 · DOI
- Unterkalmsteiner, 2014, A taxonomy for requirements engineering and software test alignment, ACM Trans. Softw. Eng. Methodol. (TOSEM), 23, 16, 10.1145/2523088 · DOI
- Unterkalmsteiner, 2015, Large-scale information retrieval in software engineering – an experience report from industrial application, Empirical Softw. Eng., 1
Cited by
Sorted by citations
An empirically based model of software prototyping: a mapping study and a multi-case study
Bjarnason, E., Lang, F., & Mjöberg, A. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10331-w · Cited by 75
Self-citation
Metadata
- Authors
- Bjarnason, E., Unterkalmsteiner, M., Borg, M., & Engström, E.
- Affiliations
- Lund University (SE)
- Blekinge Institute of Technology (SE)
- Corresponding author
- Bjarnason, Elizabeth
- Venue
- Information and Software Technology
- Publisher
- Elsevier BV
- Published
- 2016-09
- Volume
- 77
- Pages
- 61-79
- ISSN
- 0950-5849 (ISSN-L)
- OpenAlex
- W2331721881
- Cited by
- 84
- References
- 0
- Citations by year
- 2026: 6 · 2025: 5 · 2024: 9 · 2023: 7 · 2022: 9 · 2021: 10 · 2020: 5 · 2019: 9 · 2018: 10 · 2017: 7 · 2016: 3
- FWCI
- 13.72
- Type
- journal article
- Language
- en
- Open access
- green
- arxiv.org
- Licence
- cc-by-nc-sa
- www.elsevier.com/tdm/userlicense/1.0/ (tdm)
- Locations
- Information and Software Technology (publishedVersion)
- arXiv (Cornell University) (submittedVersion, cc-by-nc-sa)
- Lund University Publications (Lund University) (submittedVersion, other-oa)
- KTH Publication Database DiVA (KTH Royal Institute of Technology) (submittedVersion, other-oa)
- arXiv (Cornell University)
- Funders
- EASE
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Control and Systems Engineering › Systems Engineering Methodologies and Applications
- Keywords
- agile requirements engineering, requirements analysis, requirements validation, requirements verification, requirements management, behavior-driven development, requirements documentation, requirements communication
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
