Procedures for Performing Systematic Reviews

Procedures for Performing Systematic Reviews

July, 2004 | Barbara Kitchenham
This document provides a comprehensive guideline for conducting systematic reviews in software engineering, adapted from existing medical guidelines. It covers three main phases: planning, conducting, and reporting the review. The planning phase involves identifying the need for a review and developing a review protocol, which includes defining the research question and selecting appropriate study designs. The conducting phase includes identifying relevant research, selecting studies, assessing study quality, extracting data, and synthesizing results. The reporting phase focuses on effectively communicating the findings through technical reports or journal/conference papers. The document emphasizes the importance of transparency, reproducibility, and rigorous methodology in systematic reviews, addressing issues such as publication bias, data management, and the use of quality instruments. It also discusses the challenges unique to software engineering research, such as the lack of empirical studies and the need for expert opinion.This document provides a comprehensive guideline for conducting systematic reviews in software engineering, adapted from existing medical guidelines. It covers three main phases: planning, conducting, and reporting the review. The planning phase involves identifying the need for a review and developing a review protocol, which includes defining the research question and selecting appropriate study designs. The conducting phase includes identifying relevant research, selecting studies, assessing study quality, extracting data, and synthesizing results. The reporting phase focuses on effectively communicating the findings through technical reports or journal/conference papers. The document emphasizes the importance of transparency, reproducibility, and rigorous methodology in systematic reviews, addressing issues such as publication bias, data management, and the use of quality instruments. It also discusses the challenges unique to software engineering research, such as the lack of empirical studies and the need for expert opinion.
Reach us at info@study.space