A Systematic Review in Software Engineering
📜 Abstract
Background: Systematic literature reviews, almost unknown in software engineering, are a comprehensive approach to identifying, interpreting, and summarising existing evidence. Aim: The aim of this paper is to review and evaluate the use of systematic literature reviews and also to develop guidelines for their use in software engineering. Method: We use examples from existing literature reviews and from our own systematic review to illustrate the issues that arise in the various stages of a systematic literature review. Results: Our research shows that few systematic reviews have been conducted in software engineering to date but those that have provide useful information about existing research and identify knowledge gaps. Conclusions: Systematic literature reviews can provide a rigorous basis for identifying where there are good examples of evidence-based practice in software engineering and where more research is needed.
✨ Summary
This paper is a seminal work on the application of systematic literature reviews (SLRs) in software engineering. It introduces the concept as commonplace in medical research but almost unknown in software engineering as of its publication in 2004. The authors provide a comprehensive guideline on conducting SLRs within the software domain, suggesting a framework for identifying and analyzing existing research comprehensively.
The influence of this paper in academic circles is significant. By seeking to introduce a more rigorous methodological approach, the paper has guided subsequent research in the field by supporting the development of evidence-based software engineering. It has been widely referenced for developing further studies and guidelines, such as in Budgen et al.’s report on evidence-based software engineering (https://dl.acm.org/doi/10.1145/1368088.1368122) and in the guidelines by Dybå et al. on research synthesis in software engineering (https://ieeexplore.ieee.org/abstract/document/5072517).
Additionally, the paper’s insights have sparked discussions and developments in software engineering practices aimed at increasing the reliance on solid empirical evidence for decision making. Despite its academic orientation, the principles encapsulated in the paper have influenced industry perspectives where methodological soundness and evidential bases have gained traction.