The DOI matches its Crossref record; 75 of the 75 references it cites were found in a registry or an index.
Guidelines for conducting and reporting case study research in software engineering
Open accessAbstract
Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors’ own experience from conducting and reading case studies. The terminology and guidelines are compiled from different methodology handbooks in other research domains, in particular social science and information systems, and adapted to the needs in software engineering. We present recommended practices for software engineering case studies as well as empirically derived and evaluated checklists for researchers and readers of case study research.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Figures
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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?
In the citing paper
“it is common to include construct validity, reliability, internal validity, and external validity, according to the guideline proposed in other works [222,255], which we adopted in the following.”
From Sustainability in computing education: A systematic literature review (2024) · cites this paper as [222]
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
(1984) · Cited by 81,983
Case Study Research: Design and Methods
Chaiklin, H. (1991) · The Journal of Nervous and Mental Disease · doi:10.1097/00005053-199102000-00025 · Cited by 39,535
Basics of Qualitative Research
Ozanne, J. L., Strauss, A., & Corbin, J. (1992) · Journal of Marketing Research · doi:10.1177/002224379202900312 · Cited by 17,866
Basics of Qualitative Research
Ozanne, J. L., Strauss, A., & Corbin, J. (1992) · Journal of Marketing Research · doi:10.2307/3172751 · Cited by 17,850
Building Theories from Case Study Research
Eisenhardt, K. M. (1989) · The Academy of Management Review · doi:10.2307/258557 · Cited by 17,455
The Art of Case Study Research
Johnson, K. E., & Stake, R. E. (1996) · The Modern Language Journal · doi:10.2307/329758 · Cited by 15,826 · cited 4×
“Four different types of triangulation may be applied ( Stake 1995 ):”
BackgroundMethodInfluentialHartley, J. (2004) · Essential Guide to Qualitative Methods in Organizational Research · doi:10.4135/9781446280119.n26 · Cited by 15,461
Five misunderstandings about case-study research
Flyvbjerg, B. (2006) · Qualitative Inquiry · doi:10.1177/1077800405284363 · Cited by 14,266 · cited 4×
“2 Case study methodology was originally used primarily for exploratory purposes, and some researchers still limit case studies for this purpose, as discussed by Flyvbjerg (2007).”
BackgroundMethodInfluentialAn Experimental Application of the DELPHI Method to the Use of Experts
Dalkey, N., & Helmer, O. (1963) · Management Science · doi:10.1287/mnsc.9.3.458 · Cited by 6,061
A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems1
Klein, H. K., & Myers, M. D. (1999) · MIS Quarterly · doi:10.2307/249410 · Cited by 5,263 · cited 7×
“We prefer to consider ethnographic studies as a specialized type of case studies with focus on cultural practices (Easterbrook et al. 2008) or long duration studies with large amounts of participant-observer data (Klein and Myers 1999).”
BackgroundMethodInfluential
Research works printed but not linked: 1
- Shull F, Singer J, Sjøberg D (eds) (2008) Guide to Advanced Empirical Software Engineering. Springer-Verlag: London · DOI · Paper page
Cited by
A systematic review of systematic review process research in software engineering
Kitchenham, B., & Brereton, P. (2013) · Information and Software Technology · doi:10.1016/j.infsof.2013.07.010 · Cited by 1,094
“ESEM P41 S36 (a,b) Kitchenham, B.A., Brereton, P., Turner, M., Niazi, M.K., Linkman, S., Pretorius, R., Budgen, D. 2010 Refining the systematic literature review process-two participantobserver case studies Empirical Software Engineering 15, 618–653 P42 S37 Kitchenham, B.A., Andrew J. Burn, Zhi Li 2009 A Quality Check…”
BackgroundInfluentialDigital twins in smart farming
Verdouw, C., Tekinerdogan, B., Beulens, A., & Wolfert, S. (2021) · Agricultural Systems · doi:10.1016/j.agsy.2020.103046 · Cited by 711
Deep learning code fragments for code clone detection
White, M., Tufano, M., Vendome, C., & Poshyvanyk, D. (2016) · Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/2970276.2970326 · Cited by 558
“Judging code clones is inherently difficult (even among experts [102,104,107]) because of imperfect definitions [10,106] and the lack of oracles [107], so we developed a research instrument [109] to support consistent evaluations and control construct threats.”
BackgroundMatcha, W., Uzir, N. A., Gasevic, D., & Pardo, A. (2020) · IEEE Transactions on Learning Technologies · doi:10.1109/tlt.2019.2916802 · Cited by 399
“We particularly refer to some technology-related fields such as empirical software engineering from which empirical research on user-centered learning analytics systems can learn and which have guidelines how results should be reported and threats to validity discussed [99], [100].”
BackgroundEducational Data Mining and Learning Analytics in Programming: Literature Review and Case Studies
Ihantola, P., Vihavainen, A., Ahadi, A., Butler, M., Börstler, J., Edwards, S. H., Isohanni, E., Korhonen, A., Petersen, A., Rivers, K., et al. (2015) · Proceedings of the 2015 ITiCSE on Working Group Reports · doi:10.1145/2858796.2858798 · Cited by 332
“For this purpose, we adapted the quality criteria for research proposed by Downs & Black [34] and Runeson & H¨ost [94] and added them to the data extraction form.”
MethodInfluential
Metadata
- Authors
- Runeson, P., & Höst, M.
- Affiliations
- Lund University (SE)
- Corresponding author
- Runeson, Per
- Venue
- Empirical Software Engineering
- Published
- 2008-12-19
- Volume
- 14
- Issue
- 2
- Pages
- 131-164
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- OpenAlex
- W2162739315
- Cited by
- 3,862
- References
- 75
- Citations by year
- 2026: 204 · 2025: 225 · 2024: 244 · 2023: 241 · 2022: 246 · 2021: 299 · 2020: 312 · 2019: 268 · 2018: 280 · 2017: 237 · 2016: 260 · 2015: 263 · 2014: 252 · 2013: 198 · 2012: 151
- FWCI
- 186.23
- Type
- journal article
- Language
- en
- Open access
- hybrid
- doi.org
- Licence
- cc-by-nc
- Locations
- Empirical Software Engineering (publishedVersion, cc-by-nc)
- Lund University Publications (Lund University) (submittedVersion, other-oa)
- Funders
- Vetenskapsrådet
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Sociology and Political Science › Qualitative Comparative Analysis Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Keywords
- case study method, software engineering research, reporting guidelines, research quality, naturalistic study, qualitative research practice
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: Guidelines for conducting and reporting case study research in software engineering. https://app.cochat.ai/papers/10.1007/s10664-008-9102-8
- The paper
- Runeson, P., & Höst, M. (2009). Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering. https://doi.org/10.1007/s10664-008-9102-8
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.





