Cited by 169Software Engineering Techniques and PracticesAdvanced Software Engineering MethodologiesSystems Engineering Methodologies and Applications

The DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.

Requirements engineering: A systematic mapping study in agile software development

Curcio, Karina, Navarro, Tiago, Malucelli, Andreia, Reinehr, Sheila·2018·Journal of Systems and Software

Overview

Integrity signals

Registry

Crossref · 10.1016/j.jss.2018.01.036

Cites

4 of 4 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

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?

Citations

Cites

Flagged first, then by citations

Research works printed but not linked: 11

  1. Dingsøyr, 2012, A decade of agile methodologies: Towards explaining agile software development, J. Syst. Softw., 85, 1213, 10.1016/j.jss.2012.02.033 · DOI
  2. Inayat, 2015, A systematic literature review on agile requirements engineering practices and challenges, Comput. Hum. Behav., 51, 10.1016/j.chb.2014.10.046 · DOI
  3. Eghariani, 2016, Review on Agile requirements engineering challenges, 507
  4. Heck, 2016, A systematic literature review on quality criteria for agile requirements specifications
  5. Silva, 2011, User-centered design and agile methods: a systematic review, 2011, 77
  6. Wang, 2012, “Leagile” software development: an experience report analysis of the application of lean approaches in agile software development, J. Syst. Softw., 85, 1287, 10.1016/j.jss.2012.01.061 · DOI
  7. Wohlin, 2013, On the reliability of mapping studies in software engineering, J. Syst. Softw., 86, 2594, 10.1016/j.jss.2013.04.076 · DOI
  8. Landis, 1977, The measurement of observer agreement for categorical data, Biometrics, 33, 159, 10.2307/2529310 · DOI · Paper page
  9. ISO/IEC/IEEE, ISO/IEC/IEEE 29148:2011 Systems and software engineering – life cycle processes – requirements engineering, 2011.
  10. Wieringa, 2006, Requirements engineering paper classification and evaluation criteria: a proposal and a discussion, Requir. Eng., 11, 102, 10.1007/s00766-005-0021-6 · DOI · Paper page
  11. Cao, 2008, Agile requirements engineering practices: an empirical study, IEEE Softw., 25, 60, 10.1109/MS.2008.1 · DOI

Cited by

Sorted by citations

Metadata

Authors
Curcio, K., Navarro, T., Malucelli, A., & Reinehr, S.
Affiliations
Pontifícia Universidade Católica do Paraná (BR)
Corresponding author
Reinehr, Sheila
Venue
Journal of Systems and Software
Publisher
Elsevier BV
Published
2018-05
Volume
139
Pages
32-50
ISSN
0164-1212 (ISSN-L)
OpenAlex
W2793921910
Cited by
169
References
4
Citations by year
2026: 7 · 2025: 17 · 2024: 18 · 2023: 19 · 2022: 28 · 2021: 30 · 2020: 25 · 2019: 18 · 2018: 7
FWCI
22.32
Type
journal article
Language
en
Open access
closed
Locations
Journal of Systems and Software (publishedVersion)
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
requirements engineering, agile software development, requirements analysis, requirements change management, SWEBOK, research gaps

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