A review of software inspections
A review of software inspections
Assessing Software Review Meetings: Results of a Comparative Analysis of Two Experimental Studies
IEEE Transactions on Software Engineering
Measuring cognitive activities in software engineering
Proceedings of the 20th international conference on Software engineering
Characterizing implicit information during peer review meetings
Proceedings of the 22nd international conference on Software engineering
Lessons from Three Years of Inspection Data
IEEE Software
Communication and Organization: An Empirical Study of Discussion in Inspection Meetings
IEEE Transactions on Software Engineering
An empirical method based on protocol analysis to analyze technical review meetings
CASCON '98 Proceedings of the 1998 conference of the Centre for Advanced Studies on Collaborative research
Thematic coherence and quotation practices in OSS design-oriented online discussions
GROUP '05 Proceedings of the 2005 international ACM SIGGROUP conference on Supporting group work
Making sense of engineering design review activities
Artificial Intelligence for Engineering Design, Analysis and Manufacturing
A socio-cognitive analysis of online design discussions in an Open Source Software community
Interacting with Computers
Comparing of feedback-collection and think-aloud methods in program comprehension studies
Behaviour & Information Technology
Multimodality and parallelism in design interaction: co-designers' alignment and coalitions
Proceedings of the 2006 conference on Cooperative Systems Design: Seamless Integration of Artifacts and Conversations -- Enhanced Concepts of Infrastructure for Communication
Hi-index | 0.00 |
Peer review meetings (PRMs) are formal meetings during which peers systematically analyze artifacts to improve their quality and report on non-conformities. This paper presents an approach based on protocol analysis for quantifying the influence of participant roles during PRMs. Three views are used to characterize the seven defined participant roles. The project view defines three roles: supervisor, procedure expert and developer. The meeting view defines two roles: author and reviewer, and the task view defines the roles reflecting direct and indirect interest in the artifact under review. The analysis, based on log-linear modeling, shows that review activities have different patterns, depending on their focus: form or content. The influence of each role is analyzed with respect to this focus. Interpretation of the quantitative data leads to the suggestion that PRMs could be improved by creating three different types of reviews, each of which collects together specific roles: form review, cognitive synchronization review and content review.