Skip to content

Guidelines for conducting and reporting case study research in software engineering

Per Runeson, Martin Höst

Empirical Software Engineering · 2008 · 4,310 citationsOpen access

No retraction on record in OpenAlex.Check Crossref now

Cite this paper

Runeson, P., & Höst, M. (2008). Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering, 14(2), 131–164. https://doi.org/10.1007/s10664-008-9102-8

In text: (Runeson & Höst, 2008)

Ask a question about this research

One question, free, no account. Anchorcite finds the papers, checks each against Crossref and links every sentence of the answer to the passage it comes from.

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.

  1. A Design Science Research Methodology for Information Systems Research2007
  2. A metrics suite for object oriented design1994
  3. A spiral model of software development and enhancement1986
  4. On the criteria to be used in decomposing systems into modules1972
  5. The interdisciplinary study of coordination1994

Metadata from OpenAlex (CC0). Citations are generated from the published record.