Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

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 access
Runeson, Per, Höst, Martin · 2009 · Empirical Software Engineering

Abstract

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.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1007/s10664-008-9102-8

Cites

75 of 75 references verified0 citation errors · 0 not checkable

Statistics

Figures

Fig. 1 Holistic case study ( left ) and embedded case study ( right )
Fig. 1 Holistic case study ( left ) and embedded case study ( right )CC-BY-NC · From the PDF
Image 2
CC-BY-NC · From the PDF
Image 3
CC-BY-NC · From the PDF
Image 4
CC-BY-NC · From the PDF
Image 5
CC-BY-NC · From the PDF
Image 6
CC-BY-NC · From the PDF

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.

A few free checks a day · papers already verified open instantly · results are public

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?

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

Show all 75 references

Research works printed but not linked: 1

  1. Shull F, Singer J, Sjøberg D (eds) (2008) Guide to Advanced Empirical Software Engineering. Springer-Verlag: London · DOI · Paper page

Cited by

See all 3,862

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
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.