Guidelines for conducting and reporting case study research in software engineering
By Per Runeson, Martin Höst. Empirical Software Engineering, 2009
4,277 citations recorded by the source corpus.
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.
Subfields: Computer Science Applications, Information Systems
View Paper: https://www.semanticscholar.org/paper/27e57cc2f22c1921d2a1c3954d5062e3fe391553
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computer Science Applications
- Margaret M. Burnett
- Claes Wohlin
- Emelie Engström
- Mats Skoglund
- Thomas D. Latoza
- Amy J. Ko
- Roel J. Wieringa
- Per Runeson
In Information Systems
- Claes Wohlin
- Margaret M. Burnett
- Amy J. Ko
- Thomas D. Latoza
- Michele Tufano
- Tony Gorschek
- Per Runeson
- Pearl Brereton
Citations in the corpus
- Recommendation Systems in Software Engineering (2014, methodology): “Natural language can contain important information about related bug severity [37], bug reports [58, 64], affected code [34, 55], etc.”
- A systematic review on regression test selection techniques (2010, methodology): “Jedlitschka and Pfahl [24]for experiments and Runeson and Höst [52] for case studies.”
- A practical guide to controlled experiments of software engineering tools with human participants (2013, methodology): “Readers are encouraged to consult the many high quality introductions to case studies and other methods (Runeson and Höst 2009; Dybå et al. 2011; Dittrich 2007) and empirical software engineering more broadly (Wohlin et al. 2000; Juristo and Moreno 2001; Shull et al. 2006).”
- Deep learning code fragments for code clone detection (2016, background): “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.”
- Design Science Methodology for Information Systems and Software Engineering (2014, background): “12], Robson [9, Part III], and Denscombe [4].”
- Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review (2012, background): “They were however included in the review as they provided data points relevant to the other research questions.”
- A systematic review of systematic review process research in software engineering (2013, background): “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 2”
- Experimentation in Software Engineering (2012, background): “4, we discuss specific data collection methods, where we have found interviews, observations, archival data and metrics being applicable to software engineering case studies [22, 146, 180].”
- Educational Data Mining and Learning Analytics in Programming: Literature Review and Case Studies (2015, methodology): “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.”
- A Systematic Review of Empirical Studies on Learning Analytics Dashboards: A Self-Regulated Learning Perspective (2020, background): “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].”
- Context in industrial software engineering research (2009, neutral): “Facets SR(8) SP(4) QA(7) SC(2) UML(2) RM(1) RES(1) AE(1) CS(1) Total(27)”
- Sampling in software engineering research: a critical review and guidelines (2020, background): “Important methodological works in software engineering merely explain how research should be conducted or summarize works from reference disciplines that explained how research should conducted (e.g. Kitchenham and Charters, 2007; Stol et al., 2016; Ralph, 2019; Wohlin et al., 2012; Kitchenham et al”
- Exploring the Integration of Large Language Models in Industrial Test Maintenance Processes (2024, methodology): “Our case study follows the guidelines from Runeson and Höst [95].”