Action Research in Software Engineering: Metrics’ Research Perspective (Invited Talk)

Abstract

Action research entered into software engineering as one of the responses to the software engineering research crisis at the end of the last millennium. As one of the challenges in the crisis was the lack of empirical results and the transfer of research results into practices, the action research could address these challenges. It is a methodology where collaboration and host organizations are the focus of knowledge discovery, development, and documentation. Although the methodology is often well received in industrial contexts, it is inherently difficult to learn as it requires experience and varies from organization to organization. This chapter describes the pillars of action research as a methodology and how to teach them. The chapter includes examples of teaching action research at the bachelor, master and PhD levels. In addition to theory, the chapter contains examples from practice.

Evaluate and control service and transaction dependability of complex IoT systems

“…We followed the method of action research, which combines research and practice in a cyclical approach Reason and Bradbury (2001). While it focuses on improving industrial practices, it enables iteratively to develop solutions for complex problems Staron (2019). Action research is appropriate for the solution of our design problem, where we aim to improve the dependability evaluation with our research artifact -the transaction-based dependability evaluation approach -and simultaneously studying the experience of applying it in real-world industry use case Davison et al (2004).…”