Reporting Action Research Studies
Conducting an action research study improves practices at our industrial partners. The improvement can range from elevating the competence of the action team to changing the way in which the partner company or organization develops software. The ideal outcome, however, is the change in the way of working or in the product. While improving the industrial practice, action research also contributes to developing and evaluating theories in software engineering. Therefore, it is important that we report our action research studies in a rigorous way, so that others can learn from our experiences. In this chapter, we describe how to report studies, both in the standard format of research papers to focus on the impact of the actions and as a storytelling to focus on the actions taken alongside of the impact.
Unable to display preview. Download preview PDF.
- [Ber18]Jeremy Berg. Obfuscating with transparency. Science, page 133, 2018.Google Scholar
- [BRB+04]David E Bakken, R Rarameswaran, Douglas M Blough, Andy A Franz, and Ty J Palmer. Data obfuscation: Anonymity and desensitization of usable data sets. IEEE Security & Privacy, 2(6):34–41, 2004.Google Scholar
- [CHGL18]Zhipeng Cai, Zaobo He, Xin Guan, and Yingshu Li. Collective data-sanitization for preventing sensitive information inference attacks in social networks. IEEE Transactions on Dependable and Secure Computing, 15(4):577–590, 2018.Google Scholar
- [FW05]A Feldman and T Weiss. Suggestions for writing the action research report. In University of Massachusetts Amherst Conference Paper, 2005.Google Scholar
- [Ip17]Tiffany Ip. Linking research to action: A simple guide to writing an action research report. The Language Teacher, 41(1):37–39, 2017.Google Scholar
- [NKo10]Jernej Novak, Andrej Krajnc, and RokŽontar. Taxonomy of static code analysis tools. In MIPRO, 2010 Proceedings of the 33rd International Convention, pages 418–422. IEEE, 2010.Google Scholar
- [Pin15]Steven Pinker. The sense of style: The thinking person’s guide to writing in the 21st century. Penguin Books, 2015.Google Scholar
- [RH09]Per Runeson and Martin Höst. Guidelines for conducting and reporting case study research in software engineering. Empirical software engineering, 14(2):131, 2009.Google Scholar
- [RHRR12]Per Runeson, Martin Höst, Austen Rainer, and Björn Regnell. Case study research in software engineering. In Guidelines and examples. Wiley Online Library, 2012.Google Scholar
- [SMT+18]Miroslaw Staron, Wilhelm Meding, Matthias Tichy, Jonas Bjurhede, Holger Giese, and Ola Söder. Industrial experiences from evolving measurement systems into self-healing systems for improved availability. Software: Practice and Experience, 48(3):719–739, 2018.Google Scholar
- [Swa90]John Swales. Genre analysis: English in academic and research settings. Cambridge University Press, 1990.Google Scholar
- [Swa11]John M Swales. Aspects of article introductions. Number 1. University of Michigan Press, 2011.Google Scholar
- [Swo12]Helen Sword. Stylish academic writing. Harvard University Press, 2012.Google Scholar