Understanding Peer Review of Software Engineering Papers
Neil A. Ernst, Jeffrey C. Carver, Daniel Mendez, Marco, Torchiano

TL;DR
This study investigates how software engineering reviewers, including award-winners, evaluate papers, identifying key qualities of good reviews and paper features that influence review outcomes through interviews and a survey of 175 reviewers.
Contribution
It provides empirical insights into reviewer behaviors, criteria for good reviews, and features of papers that lead to positive or negative evaluations in software engineering.
Findings
45% of award-winners review 20+ papers annually
88% of reviewers spend over two hours on journal reviews
Clear, supported validation and novelty are key for positive reviews
Abstract
Peer review is a key activity intended to preserve the quality and integrity of scientific publications. However, in practice it is far from perfect. We aim at understanding how reviewers, including those who have won awards for reviewing, perform their reviews of software engineering papers to identify both what makes a good reviewing approach and what makes a good paper. We first conducted a series of in-person interviews with well-respected reviewers in the software engineering field. Then, we used the results of those interviews to develop a questionnaire used in an online survey and sent out to reviewers from well-respected venues covering a number of software engineering disciplines, some of whom had won awards for their reviewing efforts. We analyzed the responses from the interviews and from 175 reviewers who completed the online survey (including both reviewers who had…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
