Experience of Industry Case Studies: A Comparison of Multi-Case and Embedded Case Study Methods

J. Bass, Sarah Beecham, J. Noll
{"title":"Experience of Industry Case Studies: A Comparison of Multi-Case and Embedded Case Study Methods","authors":"J. Bass, Sarah Beecham, J. Noll","doi":"10.1145/3193965.3193967","DOIUrl":null,"url":null,"abstract":"Context: Case studies are a useful approach for conducting empirical studies of software engineering, in part because they allow a phenomenon to be studied in its real-world context. However, given that there are several kinds of case studies, each with its own strengths and weaknesses, researchers need to know how to choose which kind to employ for a specific research study. Aim: The objective of this research is to compare two case study approaches: embedded, longitudinal case studies, and multi-case studies. Approach: We compared two actual software engineering case studies: a multi-case study involving interviews with 46 practitioners at 9 international companies engaged in offshoring and outsourcing, and a single case, participant observation embedded case study lasting 13 months in a mid-sized Irish software company. Both case studies were exploring similar problems of understanding the activities performed by members of scrum development teams. Results: We found that both multi-case and embedded case studies are suitable for exploratory research (hypothesis development) but that embedded research may also be more suitable for explanatory research (hypothesis testing). We also found that longitudinal case studies offer better confirmability, while multi-case studies offer better transferability. Conclusion: We propose a set of illustrative research questions to assist with the selection of the appropriate case study method.","PeriodicalId":237556,"journal":{"name":"2018 IEEE/ACM 6th International Workshop on Conducting Empirical Studies in Industry (CESI)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2018-05-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"17","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2018 IEEE/ACM 6th International Workshop on Conducting Empirical Studies in Industry (CESI)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3193965.3193967","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 17

Abstract

Context: Case studies are a useful approach for conducting empirical studies of software engineering, in part because they allow a phenomenon to be studied in its real-world context. However, given that there are several kinds of case studies, each with its own strengths and weaknesses, researchers need to know how to choose which kind to employ for a specific research study. Aim: The objective of this research is to compare two case study approaches: embedded, longitudinal case studies, and multi-case studies. Approach: We compared two actual software engineering case studies: a multi-case study involving interviews with 46 practitioners at 9 international companies engaged in offshoring and outsourcing, and a single case, participant observation embedded case study lasting 13 months in a mid-sized Irish software company. Both case studies were exploring similar problems of understanding the activities performed by members of scrum development teams. Results: We found that both multi-case and embedded case studies are suitable for exploratory research (hypothesis development) but that embedded research may also be more suitable for explanatory research (hypothesis testing). We also found that longitudinal case studies offer better confirmability, while multi-case studies offer better transferability. Conclusion: We propose a set of illustrative research questions to assist with the selection of the appropriate case study method.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
行业案例研究的经验:多案例与嵌入式案例研究方法的比较
环境:案例研究是进行软件工程经验研究的有用方法,部分原因是它们允许在现实环境中研究现象。然而,考虑到有几种案例研究,每种都有自己的优点和缺点,研究人员需要知道如何选择哪一种用于特定的研究。目的:本研究的目的是比较两种案例研究方法:嵌入式纵向案例研究和多案例研究。方法:我们比较了两个实际的软件工程案例研究:一个多案例研究涉及对从事离岸和外包的9家国际公司的46名从业人员的访谈,以及一个在一家中型爱尔兰软件公司持续13个月的单一案例,参与者观察嵌入式案例研究。这两个案例研究都在探索类似的问题,即如何理解scrum开发团队成员执行的活动。结果:我们发现多案例研究和嵌入式案例研究都适合探索性研究(假设发展),但嵌入式研究也可能更适合解释性研究(假设检验)。我们还发现纵向案例研究提供了更好的确认性,而多案例研究提供了更好的可转移性。结论:我们提出了一套说明性研究问题,以协助选择适当的案例研究方法。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
A Preliminary Checklist for Capturing Baseline Situations in Studying the Impacts of Agile Practices Introduction Comparing Reliability Levels of Software Releases Experience of Industry Case Studies: A Comparison of Multi-Case and Embedded Case Study Methods Experiences in Using Practitioner's Checklists to Evaluate the Industrial Relevance of Requirements Engineering Experiments Towards an Experiment Line on Software Inspection with Human Computation
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1