The DOI matches its Crossref record; 21 of the 21 references it cites were found in a registry or an index.
A Map of Threats to Validity of Systematic Literature Reviews in Software Engineering
Abstract
Context: The assessment of Threats to Validity (TTVs) is critical to secure the quality of empirical studies in Software Engineering (SE). In the recent decade, Systematic Literature Review (SLR) was becoming an increasingly important empirical research method in SE. One of the mechanisms of insuring the level of scientific value in the findings of an SLR is to rigorously assess its validity. Hence, it is necessary to realize the status quo and issues of TTVs of SLRs in SE. Objective: This study aims to investigate the-state-of-the-practice of TTVs of the SLRs published in SE, and further support SE researchers to improve the assessment and strategies against TTVs in order to increase the quality of SLRs in SE. Method: We conducted a tertiary study by reviewing the SLRs in SE that report the assessment of TTVs. Results: We identified 316 SLRs published from 2004 to the first half of 2015, in which TTVs are discussed. The issues associated to TTVs were also summarized and categorized. Conclusion: The common TTVs related to SLR research, such as internal validity and reliability, were thoroughly discussed in most SLRs. The threats to construct validity and external validity drew less attention. Moreover, there are few strategies and tactics being reported to cope with the various TTVs.
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
(2004) · Cited by 5,198
Noblit, G., & Hare, R. (1988) · doi:10.4135/9781412985000 · Cited by 2,723
Recommended Steps for Thematic Synthesis in Software Engineering
Cruzes, D. S., & Dyba, T. (2011) · 2011 International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2011.36 · Cited by 960
Systematic Review in Software Engineering
Biolchini, J. C. D. A., & Mian, P. G. (2005) · Cited by 561
Identifying relevant studies in software engineering
Zhang, H., Babar, M. A., & Tell, P. (2011) · Information and Software Technology · doi:10.1016/j.infsof.2010.12.010 · Cited by 557
Self-citationEvidence-based software engineering for practitioners
Dyba, T., Kitchenham, B. A., & Jorgensen, M. (2005) · IEEE Software · doi:10.1109/ms.2005.6 · Cited by 463
Evidence-based software engineering
Kitchenham, B. A., Dyba, T., & Jorgensen, M. (2004) · Proceedings. 26th International Conference on Software Engineering · doi:10.1109/icse.2004.1317449 · Cited by 455
Systematic review in software engineering: where we are and where we should be going
Kitchenham, B. A. (2012) · Proceedings of the 2nd international workshop on Evidential assessment of software technologies · doi:10.1145/2372233.2372235 · Cited by 198
A systematic literature review of stakeholder identification methods in requirements elicitation
Pacheco, C., & García, I. (2012) · Journal of Systems and Software · doi:10.1016/j.jss.2012.04.075 · Cited by 168
Views on Internal and External Validity in Empirical Software Engineering
Siegmund, J., Siegmund, N., & Apel, S. (2015) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2015.24 · Cited by 164
Research works printed but not linked: 2
- montagud, 2009, Gathering current knowledge about quality evaluation in software product lines, Proceedings of the 13th International Software Product Line Conference (SPLC'09), 91
- kitchenham, 2007, Guidelines for performing systematic literature reviews in software engineering, Technical Report Keele University and University of Durham
Cited by
Namoun, A., & Alshanqiti, A. (2020) · Applied Sciences · doi:10.3390/app11010237 · Cited by 473
Ampatzoglou, A., Bibi, S., Avgeriou, P., Verbeek, M., & Chatzigeorgiou, A. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.10.006 · Cited by 305
Li, J., & Kassem, M. (2021) · Automation in Construction · doi:10.1016/j.autcon.2021.103955 · Cited by 287
Challenges and solutions when adopting DevSecOps: A systematic review
Rajapakse, R. N., Zahedi, M., Babar, M. A., & Shen, H. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2021.106700 · Cited by 235
SEGRESS: Software Engineering Guidelines for REporting Secondary Studies
Kitchenham, B., Madeyski, L., & Budgen, D. (2023) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2022.3174092 · Cited by 219
Metadata
- Authors
- Zhou, X., Jin, Y., Zhang, H., Li, S., & Huang, X.
- Venue
- 2016 23rd Asia-Pacific Software Engineering Conference (APSEC)
- Publisher
- IEEE
- Published
- 2016
- Pages
- 153-160
- ISSN
- 1530-1362 (ISSN-L)
- OpenAlex
- W2600366513
- Cited by
- 260
- References
- 21
- FWCI
- 2.84
- Type
- journal article
- Language
- en
- Open access
- closed
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: A Map of Threats to Validity of Systematic Literature Reviews in Software Engineering. https://app.cochat.ai/papers/10.1109/apsec.2016.031
- The paper
- Zhou, X., Jin, Y., Zhang, H., Li, S., & Huang, X. (2016). A Map of Threats to Validity of Systematic Literature Reviews in Software Engineering. 2016 23rd Asia-Pacific Software Engineering Conference (APSEC). https://doi.org/10.1109/apsec.2016.031
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.