Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Case Study Research in Software Engineering: It is a Case, and it is a Study, but is it a Case Study?
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-0460-5253
2021 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 133, article id 106514Article in journal (Refereed) Published
Abstract [en]

Background: Case studies are regularly published in the software engineering literature, and guidelines for conducting case studies are available. Based on a perception that the label “case study” is assigned to studies that are not case studies, an investigation has been conducted. Objective: The aim was to investigate whether or not the label “case study” is correctly used in software engineering research. Method: To address the objective, 100 recent articles found through Scopus when searching for case studies in software engineering have been investigated and classified. Results: Unfortunately, the perception of misuse of the label “case study” is correct. Close to 50% of the articles investigated were judged as not being case studies according to the definition of a case study. Conclusions: We either need to ensure correct use of the label “case study”, or we need another label for its definition. Given that “case study” is a well-established label, it is probably impossible to change the label. Thus, we introduce an alternative definition of case study emphasising its real-life context, and urge researchers to carefully follow the definition of different research methods when presenting their research. © 2021 The Author

Place, publisher, year, edition, pages
Elsevier B.V. , 2021. Vol. 133, article id 106514
Keywords [en]
Case study, Empirical, Misuse, Software engineering, Case study research, Case-studies, Real-life contexts
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-21057DOI: 10.1016/j.infsof.2021.106514ISI: 000620932900006Scopus ID: 2-s2.0-85100091468OAI: oai:DiVA.org:bth-21057DiVA, id: diva2:1527888
Note

open access

Available from: 2021-02-12 Created: 2021-02-12 Last updated: 2021-03-18Bibliographically approved

Open Access in DiVA

fulltext(363 kB)1920 downloads
File information
File name FULLTEXT01.pdfFile size 363 kBChecksum SHA-512
8c0c61d57e39c397adf56ac7be0418a76b70e52130fc7bbb7c5a1a8a8e586cf8b97e3549c0e085c9c8ce1f60b104ebd3aabf9c93b8bfdae464545a6023b8a48e
Type fulltextMimetype application/pdf

Other links

Publisher's full textScopus

Authority records

Wohlin, Claes

Search in DiVA

By author/editor
Wohlin, Claes
By organisation
Department of Software Engineering
In the same journal
Information and Software Technology
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 1920 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 830 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf