Directions of Peer Review in Software Engineering

Summary

Listen to this interview of Bram Adams, Professor at the School of Computing, Queen's University, Canada. We talk about current developments in peer review, as it is practised in software engineering research.

Bram Adams : "As an editor, one thing you want to see in a review is a summary that clearly says, 'Okay, my overall scoring is this, and my reasons for that are (a) these few negative points but also (b) these few positive points.' But that, in my experience, is missing from reviews much more often than before. Now it is common for editors to get very long and detailed reviews — very well done, in fact — but the major turning-point-reasons for the reviewer’s final recommendation are really spread all throughout the review. And the problem here is that the editor is now put in the difficult position of having to sift through and to locate and in the end really interpret so that those reasons can be made clear to the authors but also to the presiding editor too.”

Related Topics

Your Host

Daniel Shea

I am a textician — that is, my work in research text resembles the work in research equipment done by a technician. Want to know more? Contact me at shea@kit.edu
View Profile