Case Study Research in Software Engineering: Guidelines and Examples

Case Study Research in Software Engineering: Guidelines and Examples

Volumn , Issue , 2012, Pages

  Runeson, Per ^a   Höst, Martin ^a   Rainer, Austen ^b   Regnell, Björn ^a  

^a LUND UNIVERSITY   (Sweden)

^b UNIVERSITY OF HERTFORDSHIRE   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84887475109     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1002/9781118181034     Document Type: Book

References (205)

1. ISO/IEC 15939: Software Engineering-Software Measurement Process. Technical Report, International Organization for Standardization, 2001.
2. L. M. Abdullah and J. M. Verner. Outsourced strategic it systems development risk. In Proceedings of the Third International Conference on Research Challenges in Information Science, 2009, pp. 275-286.
3. H. Alexander and B. Potter. Case study: the use of formal specification and rapid prototyping to establish product feasibility. Information and Software Technology, 29(7): 388-394, 1987.
4. J. W. Anastas and M. L. MacDonald. Research Design for the Social Work and the Human Services. Lexington, New York, 1994.
5. C. Andersson. A replicated empirical study of a selection method for software reliability growth models. Empirical Software Engineering, 12(2):161-182, 2007.
6. C. Andersson and P. Runeson. A replicated quantitative analysis of fault distributions in complex software systems. IEEE Transactions on Software Engineering, 33(5):273-286, 2007.
7. C. Andersson and P. Runeson. A spiral process model for case studies on software quality monitoring-method and metrics. Software Process: Improvement and Practice, 12(2):125-140, 2007.
8. A. A. Andrews and A. S. Pradhan. Ethical issues in empirical software engineering: the limits of policy. Empirical Software Engineering, 6(2):105-110, 2001.
9. A. Aurum, H. Petersson, and C. Wohlin. State-of-the-art: software inspections after 25 years. Software Testing, Verification and Reliability, 12(3):1099-1689, 2001.
10. D. Avison, R. Baskerville, and M. Myers. Controlling action research projects. Information Technology & People, 14(1):28-45, 2001.
11. N. Baddoo and T. Hall. Motivators of software process improvement: an analysis of practitioners' views. Journal of Systems and Software, 62(2):85-96, 2002.
12. N. Baddoo and T. Hall. De-motivators of software process improvement: an analysis of practitioners' views. Journal of Systems and Software, 66(1):23-22, 2003.
13. V. R. Basili and F. Shull. Evolving defect "folklore": a cross-study analysis of software defect behavior. In M. Li, B. Boehm, and L. Osterweil, editors, Software Process Workshop, Number 3840 in LNCS. Springer-Verlag, 2005, pp. 1-9.
14. V. R. Basili, F. Shull, and F. Lanubile. Building knowledge through families of experiments. IEEE Transactions on Software Engineering, 25(4):456-473, 1999.
15. V. R. Basili and D. M. Weiss. A methodology for collecting valid software engineering data. IEEE Transactions on Software Engineering, 10(6):728-737, 1984.
16. R. L. Baskerville and A. T. Wood-Harper. A critical perspective on action research as a method for information systems research. Journal of Information Technology, 11(3):235-246, 1996.
17. K. Beck. Embracing change with extreme programming. Computer, 32(10):70-77, 1999.
18. U. Becker-Kornstaedt. Descriptive software process modeling-how to deal with sensitive process information. Empirical Software Engineering, 6:353-367, 2001.
19. I. Benbasat, D. K. Goldstein, and M. Mead. The case research strategy in studies of information systems. MIS Quarterly, 11(3):369, .
20. T. Berling, C. Andersson, M. Höst, and C. Nyberg. Adaptation of a system dynamics model template for code development and testing to an industrial project. In Proceedings of the Software Process Simulation Modeling Workshop, Portland, OR, USA, 2003.
21. E. Bjarnason, K. Wnuk, and B. Regnell. Overscoping: reasons and consequences-a case study on decision making in software product management. In 4th International Workshop on Software Product Management. IEEE, Sydney, Australia, September 2010.
22. B. W. Boehm. A spiral model of software development and enhancement. Computer, 21(5):61-72, 1988.
23. B. W. Boehm and R. Ross. Theory-w software project management: a case study. In Proceedings of the 10th International Conference on Software Engineering, 1988, pp. 30-40.
24. H. Bouwman and E. Faber. Case Study Protocol B4U. Technical Report TI/RS/2003/008, Telematica Instituut, Technische Universiteit Delft, February 2003.
25. M. G. Bradac, D. E. Perry, and L. G. Votta. Prototyping a process monitoring experiment. In Proceedings of the 15th International Conference on Software Engineering. IEEE Computer Society Press, 1993, pp. 155-165.
26. M. G. Bradac, D. E. Perry, and L. G. Votta. Prototyping a process monitoring experiment. IEEE Transactions on Software Engineering, 20(10):774-784, 1994.
27. L. Bratthall and M. Jørgensen. Can you trust a single data source exploratory software engineering case study? Empirical Software Engineering, 7(1):9-26, 2002.
28. P. Brereton, B. A. Kitchenham, and D. Budgen. Using a protocol template for case study planning. In Proceedings of the 12th International Conference on Evaluation and Assessment in Software Engineering, University of Bari, Italy, 2008.
29. P. Brereton, B. A. Kitchenham, D. Budgen, M. Turner, and M. Khalil. Lessons from applying the systematic literature review process within the software engineering domain. Journal of Systems and Software, 80(4):571-583, 2007.
30. L. C. Briand, J. Wüst, S. V. Ikonomovski, and H. Lounis. Investigating quality factors in object-oriented designs: an industrial case study. In Proceedings of the 21st International Conference on Software Engineering. IEEE Computer Society, 1999, p. 345.
31. J. P. Campbell, R. L. Daft, and C. L. Hulin. What to study: generating and developing research questions, 1st edition. Sage, 1982.
32. T. D. Cook and D. T. Campbell. Quasi-Experimentation. Design & Analysis Issues for Field Studies. Houghton Mifflin Company, 1979.
33. R. G. Cooper. Winning at New Products: Accelerating the Process from Idea to Launch, 3rd edition. Perseus, 2001.
34. J. Corbin and C. Strauss. Basics of Qualitative Research, 3rd edition. Sage, 2008.
35. P. B. Corcoran. Case studies, make-your-case studies, and case stories: a critique of case-study methodology in sustainability in higher education. Environmental Education Research, 10(1):7-21, 2004.
36. D. S. Cruzes and T. Dybå. Research synthesis in software engineering: a tertiary study. Information and Software Technology, 53(5):440-455, 2011.
37. B. Curtis, H. Krasner, and N. Iscoe. A field study of the software design process for large systems. Communications of the ACM, 31(11):1268-1287, 1988.
38. N. Dalkey and O. Helmer. An experimental application of the delphi method to the use of experts. Management Science, 9(3):458-467, 1963.
39. D. Damian and J. Chisan. An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management. IEEE Transactions on Software Engineering, 32(7):433-453, 2006.
40. K. Deng and S. G. MacDonell. Maximizing data retention from the ISBSG repository. In Proceedings of the 12th International Conference on Evaluation and Assessment in Software Engineering, University of Bari, Italy, 2008.
41. O. Dieste, A. Grimán, and N. Juristo. Developing search strategies for detecting relevant experiments. Empirical Software Engineering, 14:513-539, 2009.
42. T. Dingsøyr and N. B. Moe. The impact of employee participation on the use of an electronic process guide: a longitudinal case study. IEEE Transactions on Software Engineering, 34(2):212-225, 2008.
43. Y. Dittrich, M. John, J. Singer, and B. Tessem. For the special issue on qualitative software engineering research. Information and Software Technology, 49(6):531-539, 2007.
44. Y. Dittrich, K. Rönkkö, J. Eriksson, C. Hansson, and O. Lindeberg. Cooperative method development. Empirical Software Engineering, 13(3):231-260, 2007.
45. M. Dixon-Woods, A. Booth, and A. J. Sutton. Synthesizing qualitative research: a review of published reports. Qualitative Research, 7(3):375-422, 2007.
46. T. Dybå and T. Dingsøyr. Empirical studies of agile software development: a systematic review. Information and Software Technology, 50(9-10):833-859, 2008.
47. S. Easterbrook, J. Singer, M.-A. Storey, and D. Damian. Selecting empirical methods for software engineering research. In F. Shull, J. Singer, and D. I. Sjøberg, editors, Guide to Advanced Empirical Software Engineering. Springer-Verlag, London, 2008.
48. K. M. Eisenhardt. Building theories from case study research. The Academy of Management Review, 14(4):532, .
49. K. El-Emam. Ethics and open source. Empirical Software Engineering, 6:291-292, 2001.
50. E. Engström and P. Runeson. Software product line testing-a systematic mapping study. Information and Software Technology, 53(1):2-13, 2011.
51. E. Engström, P. Runeson, and M. Skoglund. A systematic review on regression test selection techniques. Information and Software Technology, 52(1):14-30, 2010.
52. L. Esterhuizen. Doing Case Studies for the Refugee Sector; A DIY Handbook for Agencies and Practitioners. Technical Report, The Information Centre about Asylum and Refugees in the UK (ICAR), International Policy Institute, King's College London, 2004.
53. N. Fenton and N. Ohlsson. Quantitative analysis of faults and failures in a complex software system. IEEE Transactions on Software Engineering, 26(8):797-814, 2000.
54. N. Fenton and S. L. Pfleeger. Software Metrics: A Rigorous and Practical Approach, 2nd (revised printing) edition. PWS Publishing Company, London, 1997.
55. B. Flynn. Empirical research methods in operations management. Journal of Operations Management, 9(2):250-284, 1990.
56. B. Flyvbjerg. Five misunderstandings about case-study research. In Qualitative Research Practice, concise paperback edition. Sage, 2007, pp. 390-404.
57. S. Freudenberg and H. Sharp. The top 10 burning research questions from practitioners. IEEE Software, 27(5):8-9, 2010.
58. B. G. Glaser and A. Strauss. Discovery of Grounded Theory. Strategies for Qualitative Research. Sociology Press, 1967.
59. R. L. Glass, V. Ramesh, and I. Vessey. An analysis of research in computing disciplines. Communications of the ACM, 47(6):89-94, 2004.
60. R. L. Glass, I. Vessey, and S. A. Conger. Software tasks: intellectual or clerical? Information and Management, 23(4):183-191, 1992.
61. R. L. Glass, I. Vessey, and V. Ramesh. Research in software engineering: an analysis of the literature. Information and Software Technology, 44:491-506, 2001.
62. M.W. Godfrey and Q. Tu. Evolution in open source software: a case study. In Proceedings on the International Conference on Software Maintenance, 2000, pp. 131-142.
63. O. S. Gómez, N. Juristo, and S. Vegas. Replications types in experimental disciplines. In Proceeding of the 4th International Symposium on Empirical Software Engineering and Measurement, 2010.
64. T. Gorschek, P. Garre, S. Larsson, and C. Wohlin. A model for technology transfer in practice. IEEE Software, 23(6):88-95, 2006.
65. D. Gotterbarn. Ethics in qualitative studies of commercial software enterprises ethical analysis. Empirical Software Engineering, 6:301-304, 2001. 10.1023/ A:1011970531432.
66. T. Hall and V. Flynn. Ethical issues in software engineering research: a survey of current practice. Empirical Software Engineering, 6:305-317, 2001.
67. T. Hall, A. W. Rainer, N. Baddoo, and S. Beecham. An empirical study of maintenance issues within process improvement programmes in the software industry. In Proceedings of the IEEE International Conference on Software Maintenance, 2001, pp. 422-430.
68. J. Hannay, D. Sjøberg, and T. Dybå. A systematic review of theory use in software engineering experiments. IEEE Transactions on Software Engineering, 33(2):87-107, 2007.
69. W. Hayes. Research synthesis in software engineering: a case for meta-analysis. In Proceedings of the 6th International Software Metrics Symposium, 1999, pp. 143-151.
70. P. Herceg. Defining Useful Technology Evaluations. Technical Report MTR070061R1, MITRE Corporation, September 2007.
71. A. R. Hevner, S. T. March, J. Park, and S. Ram. Design science in information systems research. MIS Quarterly, 28(1):75-105, 2004.
72. N. E. Holt. A systematic review of case studies in software engineering. Master's thesis, University of Oslo, Department of Informatics, May 2006.
73. M. Höst and P. Runeson. Checklists for software engineering case study research. In Proceedings of the 1st International Symposium on Empirical Software Engineering and Measurement, 2007, pp. 479-481.
74. S. Hove and B. Anda. Experiences from conducting semi-structured interviews in empirical software engineering research. In Proceedings of the 11th IEEE International Software Metrics Symposium, 2005, pp. 1-10.
75. J. H. Iversen, L. Mathiassen, and P. A. Nielsen. Managing risk in software process improvement: an action research approach. MIS Quarterly, 28(3):395-433, 2004.
76. A. S. Jadhav and R. M. Sonar. Evaluating and selecting software packages: a review. Information and Software Technology, 51:555-563, 2009.
77. A. Jedlitschka and D. Pfahl. Reporting guidelines for controlled experiments in software engineering. In Proceedings of the International Symposium on Empirical Software Engineering, 2005.
78. P. M. Johnson, H. Kou, M. Paulding, Q. Zhang, A. Kagawa, and T. Yamashita. Improving software development management through software project telemetry. IEEE Software, 22(4):76-85, 2005.
79. N. Juristo and S. Vegas. Using differences among replications of software engineering experiments to gain knowledge. In Proceeding of the 3rd International Symposium on Empirical Software Engineering and Measurement, 2009, pp. 356-366.
80. S. H. Kan. Metrics and Models in Software Quality Engineering. AddisonWesley, 2003.
81. A. Karahasanović, B. Anda, E. Arisholm, S. E. Hove, M. Jørgensen, D. Sjøberg, and R. Welland. Collecting feedback during software engineering experiments. Empirical Software Engineering, 10(2):113-147, 2005.
82. L. Karlsson, B. Regnell, and T. Thelin. Case studies in process improvement through retrospective analysis of release planning decisions. International Journal of Software Engineering and Knowledge Engineering (IJSEKE), 16(6):885-916, 2006.
83. D. Karlström. Integrating management and engineering processes in software product development. PhD thesis, Lund University, 2004.
84. D. Karlström and P. Runeson. Decision support for extreme programming introduction and practice selection. In Proceedings of the 14th International Conference on Software Engineering and Knowledge Engineering, 2002, pp. 835-841.
85. D. Karlström and P. Runeson. Combining agile methods with stage-gate project management. IEEE Software, 22(3):43-49, 2005.
86. D. Karlström and P. Runeson. Integrating agile software development into stage-gate managed product development. Empirical Software Engineering, 11(2):203-225, 2006.
87. J. Kasurinen, O. Taipale, and K. Smolander. Test case selection and prioritization: riskbased or design-based? In Proceedings of the 4th International Symposium on Empirical Software Engineering and Measurement, ESEM '10, 2010, pp. 10:1-10:10.
88. I. M. Kellner, J. R. Madachy, and M. D. Raffo. Software process simulation modeling: why? what? how? Journal of Systems and Software, 46(2-3):91-105, 1999.
89. B. A. Kitchenham. DESMET: A Method for Evaluating Software Engineering Methods and Tools. Technical Report TR96-09, Keele University, UK, August 1996.
90. B. A. Kitchenham. Evaluating software engineering methods and tools, part 1: the evaluation context and evaluation methods. SIGSOFT Software Engineering Notes, 21(1): 11-14, 1996.
91. B. A. Kitchenham. Evaluating software engineering methods and tools, part 2: selecting an appropriate evaluation method-technical criteria. SIGSOFT Software Engineering Notes, 21(2):11-15, 1996.
92. B. A. Kitchenham. Evaluating software engineering methods and tools, part 3: selecting an appropriate evaluation method-practical issues. SIGSOFT Software Engineering Notes, 21(4):9-12, 1996.
93. B. A. Kitchenham. Evaluating software engineering methods and tools, part 7: planning feature analysis evaluation. SIGSOFT Software Engineering Notes, 22(4):21-24, 1997.
94. B. A. Kitchenham. The role of replications in empirical software engineering-a word of warning. Empirical Software Engineering, 13:219-221, 2008. 10.1007/s10664-008-9061-0.
95. B. A. Kitchenham, H. Al-Khilidar, M. A. Babar, M. Berry, K. Cox, J. Keung, F. Kurniawati, M. Staples, H. Zhang, and L. Zhu. Evaluating guidelines for reporting empirical software engineering studies. Empirical Software Engineering, 13(1):97-121, 2007.
96. B. A. Kitchenham, D. Budgen, and P. Brereton. Using mapping studies as the basis for further research-a participant-observer case study. Information and Software Technology, 53(6):638-651, 2011.
97. B. A. Kitchenham and S. Charters. Guidelines for Performing Systematic Literature Reviews in Software Engineering (version 2.3). Technical Report EBSE, Technical Report EBSE-2007-01, Keele University and Durham University, July 2007.
98. B. A. Kitchenham, T. Dybå, and M. Jørgensen. Evidence-based software engineering. In Proceedings of the 26th International Conference on Software Engineering. Edinburgh, Scotland, UK, 2004, pp. 273-281.
99. B. A. Kitchenham, R. T. Hughes, and S. G. Linkman. Modeling software measurement data. IEEE Transactions on Software Engineering, 27(9):788-804, 2001.
100. B. A. Kitchenham, D. R. Jeffery, and C. Connaughton. Misleading metrics and unsound analyses. IEEE Software, 24:73-78, 2007.
101. B. A. Kitchenham and L. Jones. Evaluating software engineering methods and tools, part 5: the influence of human factors. SIGSOFT Software Engineering Notes, 22(1):13-15, 1997.
102. B. A. Kitchenham and L. Jones. Evaluating software engineering methods and tools, part 6: identifying and scoring features. SIGSOFT Software Engineering Notes, 22(2):16-18, 1997.
103. B. A. Kitchenham and L. Jones. Evaluating software engineering methods and tools, part 8: analysing a feature analysis evaluation. SIGSOFT Software Engineering Notes, 22(5):10-12, 1997.
104. B. A. Kitchenham, S. G. Linkman, and D. Law. DESMET: a methodology for evaluating software engineering methods and tools. Computing and Control Engineering Journal, 8(3):120-126, 1997.
105. B. A. Kitchenham, S. L. Pfleeger, L. M. Pickard, P. W. Jones, D. Hoaglin, K. El Emam, and J. Rosenberg. Preliminary guidelines for empirical research in software engineering. IEEE Transactions on Software Engineering, 28(8):721-734, 2002.
106. B. A. Kitchenham and L. M. Pickard. Evaluating software engineering methods and tools, part 10: designing and running a quantitative case study. SIGSOFT Software Engineering Notes, 23(3):20-22, 1998.
107. B. A. Kitchenham and L. M. Pickard. Evaluating software engineering methods and tools, part 11: analysing quantitative case studies. SIGSOFT Software Engineering Notes, 23(4):18-20, 1998.
108. B. A. Kitchenham and L. M. Pickard. Evaluating software engineering methods and tools, part 9: quantitative case study methodology. SIGSOFT Software Engineering Notes, 23(1):24-26, 1998.
109. B. A. Kitchenham, L. M. Pickard, and S. Pfleeger. Case studies for method and tool evaluation. IEEE Software, 12(4):52-62, 1995.
110. B. A. Kitchenham, R. Pretorius, D. Budgen, P. Brereton, M. Turner, M. Niazi, and S. Linkman. Systematic literature reviews in software engineering-a tertiary study. Information and Software Technology, 52(8):792-805, 2010.
111. H. K. Klein and M. D. Myers. A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Quarterly, 23(1):67, .
112. J. Kontio, J. Bragge, and L. Lehtola. The focus group method as an empirical tool in software engineering. In F. Shull, J. Singer, and D. Sjøberg, editors, Guide to Advanced Empirical Software Engineering. Springer, 2008.
113. R. Kyburz-Graber. Does case-study methodology lack rigour? The need for quality criteria for sound case-study research, as illustrated by a recent case in secondary and higher education. Environmental Education Research, 10(1):53-65, 2004.
114. R. Larsson. Case survey methodology: Quantitative analysis of patterns across case studies. The Academy of Management Journal, 36(6):1515-1546, 1993.
115. A. S. Lee. A scientific methodology for MIS case studies. MIS Quarterly, 13(1):33, .
116. L. Lehtola, M. Kauppinen, and S. Kujala. Requirements prioritization challenges in practice. In Product Focused Software Process Improvement, Number 3009 in LNCS, Springer-Verlag, 2004, pp. 497-508.
117. T. C. Lethbridge. Mixing software engineering research and development-what needs ethical review and what does not? Empirical Software Engineering, 6:319-321, 2001.
118. T. C. Lethbridge, S. E. Sim, and J. Singer. Studying software engineers: data collection techniques for software field studies. Empirical Software Engineering, 10:311-341, 2005.
119. K. Lewin. Action research and minority problems. Journal of Social Issues, 2:34-2:36, 1946.
120. J. Li, N. B. Moe, and T. Dybå. Transition from a plan-driven process to scrum: a longitudinal case study on software quality. In Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM '10. ACM, New York, NY, USA, 2010, pp. 1-13.
121. M. Lindvall, D. Muthig, A. Dagnino, C. Wallin, M. Stupperich, D. Kiefer, J. May, and T. Kahkonen. Agile software development in large organizations. Computer, 37(12): 26-34, 2004.
122. J. Lonchamp. A structured conceptual and terminological framework for software process engineering. In Proceedings of 2nd International Conference on Software Process: Continuous Software Process Improvement. IEEE Computer Society Press, Berlin, Germany, 1993, pp. 41-53.
123. W. A. Lucas. The Case Survey Method: Aggregating Case Experience. Technical Report R-1515-RC, The Rand Corporation, Santa Monica, CA, 1974.
124. D. Martin, J. Rooksby, M. Rouncefield, and I. Sommerville. 'Good' organisational reasons for 'bad' software testing: an ethnographic study of testing in a small software company. In Proceedings of the 29th International Conference on Software Engineering, 2007, pp. 602-611.
125. R. Matulevičius. Validating an evaluation framework for requirements engineering tools. In Information Modeling Methods and Methodologies, Idea Group Publishing, 2005, pp. 148-174.
126. L. McLeod, S. MacDonell, and B. Doolin. Qualitative research on software development: a longitudinal case study methodology. Empirical Software Engineering, 16(4):430-459, 2011.
127. J. Miller. Applying meta-analytical procedures to software engineering experiments. Journal of Systems and Software, 54(1):29-39, 2000.
128. J. Miller. Statistical significance testing: a panacea for software technology experiments? Journal of Systems and Software, 73:183-192, October 2004.
129. J. Miller. Replicating software engineering experiments: a poisoned chalice or the holy grail. Information and Software Technology, 47(4):233-244, 2005.
130. D. C. Montgomery. Design and Analysis of Experiments, 3rd edition. Wiley, 1991.
131. W. J. Orlikowski. Case tools as organizational change: investigating incremental and radical changes in systems development. MIS Quarterly, 17(3):309-340, 1993.
132. A. Oručević-Alagić and M. Höst. Analysis of software transition from proprietary to open source. In Proceedings of OSS 2010-International Conference on Open Source Systems, 2010.
133. S. Owen, P. Brereton, and D. Budgen. Protocol analysis: a neglected practice. Communications of the ACM, 49(2):117-122, 2006.
134. D. E. Perry, S. E. Sim, and S. Easterbrook. Case studies for software engineers. In 29th Annual IEEE/NASA Software EngineeringWorkshop-Tutorial Notes, 2005, pp. 96-159.
135. G. Pervan and H. Maimbo. Designing a case study protocol for application in is research. In Proceedings of the 9th Pacific Conference on Information Systems, 2005, pp. 1281-1292.
136. K. Petersen, R. Feldt, S. Mujtaba, and M. Mattsson. Systematic mapping studies in software engineering. In Proceeding of the 12th International Conference on Evaluation and Assessment in Software Engineering, University of Bari, Italy, 2008.
137. K. Petersen and C. Wohlin. A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case. Journal of Systems and Software, 82(9):1479-1490, 2009.
138. K. Petersen and C. Wohlin. Context in industrial software engineering research. In Proceeding of the 3rd International Symposium on Empirical Software Engineering and Measurement, 2009, pp. 401-404.
139. S. L. Pfleeger. Understanding and improving technology transfer in software engineering. Journal of Systems and Software, 47:111-124, 1999.
140. L. Pickard, B. A. Kitchenham, and P. Jones. Combining empirical results in software engineering. Information and Software Technology, 40(14):811-821, 1998.
141. F. Pino, F. García, and M. Piattini. Software process improvement in small and medium software enterprises: a systematic review. Software Quality Journal, 16:237-261, 2008.
142. H. Post, C. Sinz, F. Merz, T. Gorges, and T. Kropf. Linking functional requirements and software verification. In 17th IEEE International Conference on Requirements Engineering. IEEE Computer Society, 2009, pp. 295-302.
143. A. Rainer, T. Hall and N. Baddoo, Persuading Developers to 'Buy into' Software Process Improvement: Local Opinion and Empirical Evidence, International Symposium on Empirical Software Engineering, 2003, pp. 326-335.
144. A. W. Rainer. An Empirical Investigation of Software Project Schedule Behaviour. Doctoral thesis, Bournemouth University, 1999.
145. A. W. Rainer. An empirical investigation of software project schedule behaviour. Empirical Software Engineering, 5(1):75-77, 2000.
146. A. W. Rainer. Representing the behaviour of software projects using multi-dimensional timelines. Information and Software Technology, 52(11):1217-1228, 2010.
147. A. W. Rainer. The longitudinal, chronological case study research strategy: a definition and an example from IBM Hursley Park. Information and Software Technology, 53(7):730-746, 2011.
148. A. W. Rainer and S. Beecham. A follow-up empirical evaluation of evidence based software engineering by undergraduate students. In Proceeding of the 12th International Conference on Evaluation and Assessment in Software Engineering, University of Bari, Italy, 2008.
149. A. W. Rainer, S. Beecham, and C. Sanderson. An assessment of published evaluations of requirements management tools. In Proceedings of the 13th International Conference on Evaluation and Assessment in Software Engineering, Durham, UK, 2009.
150. A. W. Rainer and S. Gale. Evaluating the quality and quantity of data on open source software projects. In Proceedings of the 1st International Conference on Open Source Systems, Genova, Italy, 2005.
151. A. W. Rainer and T. Hall. An analysis of some 'core studies' of software process improvement. Software Process: Improvement and Practice, 6(4):169-187, 2001.
152. A. W. Rainer and T. Hall. Identifying the causes of poor progress in software projects. In Proceedings of the 10th International Symposium on Software Metrics, 2004.
153. A. W. Rainer, T. Hall, N. Baddoo, and D. Wilson. An overview of the practitioners, processes and products project. In Proceedings of the 6th Annual Conference of the U.K. Academy of Information Sciences, Portsmouth, UK, 2001.
154. A. W. Rainer and M. J. Shepperd. Investigating software project schedule behaviour. In Proceedings of the 2nd International Conference on Empirical Assessment and Evaluation in Software Engineering, Keele, UK, 1998.
155. A. W. Rainer and M. J. Shepperd. Re-planning for a successful project. In Proceedings of the 6th International Software Metrics Symposium, Boca Raton, Florida, 1999.
156. B. Regnell, P. Beremark, and O. Eklundh. A market-driven requirements engineering process-results from an industrial improvement programme. Requirements Engineering, 3(2):121-129, 1998.
157. B. Regnell, R. Berntsson Svensson, and K. Wnuk. Can we beat the complexity of very large-scale requirements engineering? In B. Paech and C. Rolland, editors, Requirements Engineering: Foundation for Software Quality, Volume 5025 of Lecture Notes in Computer Science. Springer, Berlin/Heidelberg, 2008, pp. 123-128.
158. B. Regnell, M. Höst, J. Nattoch Dag, P. Beremark, and T. Hjelm. An industrial case study on distributed prioritisation in Market-Driven requirements engineering for packaged software. Requirements Engineering, 6(1):51-62, 2001.
159. B. Regnell, M. Höst, F. Nilsson, and H. Bengtsson. A measurement framework for team level assessment of innovation capability in early requirements engineering. In W. Aalst, J. Mylopoulos, N. M. Sadeh, M. J. Shaw, C. Szyperski, F. Bomarius, M. Oivo, P. Jaring, and P. Abrahamsson, editors, Product-Focused Software Process Improvement, Volume 32 of Lecture Notes in Business Information Processing. Springer, Berlin/Heidelberg, 2009, pp. 71-86.
160. C. K. Riemenschneider, B. C. Hardgrave, and F. D. Davis. Explaining software developer acceptance of methodologies: a comparison of five theoretical models. IEEE Transactions on Software Engineering, 28(12):1135-1145, 2002.
161. H. Robinson, J. Segal, and H. Sharp. Ethnographically-informed empirical studies of software practice. Information and Software Technology, 49(6):540-551, 2007.
162. C. Robson. Real world research 2nd edition. Blackwell, 2002.
163. M. Rodgers, A. Sowden, M. Petticrew, L. Arai, H. Roberts, N. Britten, and J. Popay. Testing methodological guidance on the conduct of narrative synthesis in systematic reviews: effectiveness of interventions to promote smoke alarm ownership and function. Evaluation, 15(1):49-73, 2009.
164. M. Rosemann and I. Vessey. Linking theory and practice: performing a reality check on a model of is success. In Proceedings of the European Conference on Information Systems, 2005, pp. 854-865.
165. M. Rosemann and I. Vessey. Toward improving the relevance of information systems research to practice: the role of applicability checks. MIS Quarterly, 32(1):1-22, 2008.
166. W. W. Royce. Managing the development of large software systems. In Proceedings of IEEE WESCON 26, 1970, pp. 1-9.
167. P. Runeson. A survey of unit testing practices. IEEE Software, 23(4):22-29, 2006.
168. P. Runeson, C. Andersson, T. Thelin, A. A. Andrews, and T. Berling. What do we know about defect detection methods? IEEE Software, 23(3):82-90, 2006.
169. P. Runeson, P. Beremark, B. Larsson, and B. Lundh. Spin-syd-a non-profit exchange network. In 1st International Workshop on Software Engineering Networking Experiences, Joensuu, Finland, 2006.
170. P. Runeson and M. Höst. Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering, 14(2):131-164, 2009.
171. P. Runeson and M. Skoglund. Reference-based search strategies on systematic literature reviews. In Proceedings of the International Conference on Evaluation and Assessment in Software Engineering, Durham, UK, 2009.
172. G. Sabaliauskaite, A. Loconsole, E. Engström, M. Unterkalmsteiner, B. Regnell, P. Runeson, T. Gorschek, and R. Feldt. Challenges in aligning requirements engineering and verification in a large-scale industrial context. In Proceedings of the 16th InternationalWorking Conference Requirements Engineering: Foundation for Software Quality, 2010, pp. 128-142.
173. C. Sadler and B. A. Kitchenham. Evaluating software engineering methods and tool, part 4: the influence of human factors. SIGSOFT Software Engineering Notes, 21(5):11-13, 1996.
174. O. Salo and P. Abrahamsson. Empirical evaluation of agile software development: The controlled case study approach. In F. Bomarius and H. Iida, editors, Proceedings of the 5th International Conference Product Focused Software Process Improvement, Number 3009 in LNCS, Springer-Verlag, 2004, pp. 408-423.
175. C. Sanderson. A DESMET-based evaluation of commercial requirements management tools in an industrial setting. Master's project, University of Hertfordshire, School of Computer Science, 2009.
176. C. B. Seaman. Qualitative methods in empirical studies of software engineering. IEEE Transactions on Software Engineering, 25(4):557-572, 1999.
177. C. B. Seaman. Ethics in qualitative studies of commercial software enterprises: case description. Empirical Software Engineering, 6:299-300, 2001.
178. C. B. Seaman and V. R. Basili. Communication and organization: an empirical study of discussion in inspection meetings. IEEE Transactions on Software Engineering, 24(7):559-572, 1998.
179. G. Shanks. Guidelines for conducting positivist case study research in information systems. Australasian Journal of Information Systems, 10(1):76-85, 2002.
180. H. Sharp and H. Robinson. An ethnographic study of XP practice. Empirical Software Engineering, 9(4):353-375, 2004.
181. A. J. Shenhar, D. Dvir, O. Levy, and A. C. Maltz. Project success: A multidimensional strategic concept. Long Range Planning, 34(6):699-725, 2001.
182. F. Shull, V. R. Basili, J. Carver, J. C. Maldonado, G. H. Travassos, M. Mendonca, and S. Fabbri. Replicating software engineering experiments: addressing the tacit knowledge problem. In Proceedings of the International Symposium Empirical Software Engineering, 2002, pp. 7-16.
183. F. Shull, J. Carver, S. Vegas, and N. Juristo. The role of replications in empirical software engineering. Empirical Software Engineering, 13:211-218, 2008.
184. F. Shull and R. L. Feldman. Building theories from multiple evidence sources. In F. Shull, J. Singer, and D. Sjøberg, editors, Guide to Advanced Empirical Software Engineering. Springer-Verlag, London, 2008.
185. F. Shull, M. G. Mendoncca, V. R. Basili, J. Carver, J. C. Maldonado, S. Fabbri, G. H. Travassos, and M. C. Ferreira. Knowledge-sharing issues in experimental software engineering. Empirical Software Engineering, 9:111-137, 2004.
186. F. Shull, J. Singer, and D. Sjøberg, editors. Guide to Advanced Empirical Software Engineering. Springer-Verlag, London, 2008.
187. J. E. Sieber. Not your ordinary research. Empirical Software Engineering, 6:323-327, 2001.
188. S. Siegel and N. J. Castellan. Nonparametric Statistics for the Behavioral Sciences, 2nd edition. McGraw-Hill, 1988.
189. S. E. Sim, J. Singer, and M.-A. Storey. Beg, borrow, or steal: Using multidisciplinary approaches in empirical software engineering. Empirical Software Engineering, 6:85-93, 2001.
190. J. Singer, T. C. Lethbridge, N. G. Vinson, and N. Anquetil. An examination of software engineering work practices. In CASCON First Decade High Impact Papers, CASCON '10. ACM, New York, NY, USA, 2010, pp. 174-188.
191. J. Singer and N. G. Vinson. Why and how research ethics matters to you. Yes, you! Empirical Software Engineering, 6:287-290, 2001.
192. J. Singer and N. G. Vinson. Ethical issues in empirical studies of software engineering. IEEE Transactions on Software Engineering, 28(12):1171-1180, 2002.
193. D. Sjøberg, T. Dybå, B. Anda, and J. E. Hannay. Building theories in software engineering. In F. Shull, J. Singer, and D. Sjøberg, editors, Guide to Advanced Empirical Software Engineering. Springer-Verlag, London, 2008.
194. D. Sjøberg, T. Dybå, and M. Jørgensen. The future of empirical methods in software engineering research. In L. Briand and A. Wolf, editors, Future of Software Engineering (FOSE'07), 2007, pp. 358-378.
195. D. Sjøberg, J. E. Hannay, O. Hansen, V. B. Kampenes, A. Karahasanovic, N.-K. Liborg, and A. Rekdal. A survey of controlled experiments in software engineering. IEEE Transactions on Software Engineering, 31(9):733-753, 2005.
196. R. E. Stake. The Art of Case Study Research. SAGE Publications, 1995.
197. M.-A. Storey, J. Ryall, J. Singer, D. Myers, L.-T. Cheng, and M. Muller. How software developers use tagging to support reminding and refinding. IEEE Transactions on Software Engineering, 35(4):470-483, 2009.
198. C. Stringfellow and A. A. Andrews. An empirical method for selecting software reliability growth models. Empirical Software Engineering, 7(4):319-343, 2002.
199. E. B. Swanson and C. M. Beath. The use of case study data in software management research. Journal of Systems and Software, 8(1):63-71, 1988.
200. O. Taipale, K. Smolander, and H. Kalviainen. Finding and ranking research directions for software testing. In I. Richardson, P. Abrahamsson, and R. Messnarz, editors, Software Process Improvement, Volume 3792 of LNCS. Springer-Verlag, 2005, pp. 39-48.
201. H. E. Thomson and P. Mayhew. Approaches to software process improvement. Software Process: Improvement and Practice, 3(1):3-17, 1997.
202. W. F. Tichy. Hints for reviewing empirical work in software engineering. Empirical Software Engineering, 5:309-312, 2000.
203. E. J. Uusitalo, M. Komssi, M. Kauppinen, and A. M. Davis. Linking requirements and testing in practice. In Proceedings of the 16th IEEE International Requirements Engineering Conference. IEEE Computer Society, 2008, pp. 265-270.
204. M. van Genuchten. Why is software late? An empirical study of reasons for delay in software development. IEEE Transactions on Software Engineering, 17(6):582-590, 1991.
205. J. C. van Niekerk and J. D. Roode. Glaserian and Straussian grounded theory: similar or completely different? In Proceedings of the 2009 Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists. ACM, New York, NY, USA, 2009, pp. 96-103.