Advances in software inspections
IEEE Transactions on Software Engineering
ICICLE: groupware for code inspection
CSCW '90 Proceedings of the 1990 ACM conference on Computer-supported cooperative work
Computer support of groups: theory-based models for GDSS research
Management Science
An improved inspection technique
Communications of the ACM
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Software inspection process
The anonymity and proximity factors in group decision support systems
Decision Support Systems
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
Assessing Software Review Meetings: Results of a Comparative Analysis of Two Experimental Studies
IEEE Transactions on Software Engineering
A case study of distributed, asynchronous software inspection
ICSE '97 Proceedings of the 19th international conference on Software engineering
An instrumented approach to improving software quality through formal technical review
ICSE '94 Proceedings of the 16th international conference on Software engineering
An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development
IEEE Transactions on Software Engineering
Communications of the ACM
IEEE Transactions on Software Engineering
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
Understanding GDSS in symbolic context: shifting the focus from technology to interaction
MIS Quarterly - Special issue on Intensive research in information systems: using qualitative, interpretive, and case methods to study information technology—third installment
EasyWinWin: a groupware-supported methodology for requirements negotiation
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Group Support Systems: New Perspectives
Group Support Systems: New Perspectives
Software Inspections: An Effective Verification Process
IEEE Software
Distributed, Collaborative Software Inspection
IEEE Software
Using Group Support Systems for Software Inspections
IEEE Software
Communication and Organization: An Empirical Study of Discussion in Inspection Meetings
IEEE Transactions on Software Engineering
Scrutiny: A Collaborative Inspection and Review System
ESEC '93 Proceedings of the 4th European Software Engineering Conference on Software Engineering
A Review of Tool Support for Software Inspection
CASE '95 Proceedings of the Seventh International Workshop on Computer-Aided Software Engineering
An assessment of group support systems experimental research: methodology and results
Journal of Management Information Systems - Special issue: GSS insights: a look back at the lab, a look forward from the field
A Computational Framework for Supporting Software Inspections
Proceedings of the 19th IEEE international conference on Automated software engineering
ISPIS: A Framework Supporting Software Inspection Processes
Proceedings of the 19th IEEE international conference on Automated software engineering
The design and field evaluation of a repeatable collaborative software code inspection process
CRIWG'05 Proceedings of the 11th international conference on Groupware: design, Implementation, and Use
Hi-index | 0.01 |
In software inspection, a key principle endorsed by Fagan is openness. However, scholars have recently questioned the efficacy of openness. For example, some argue that ego-involvement and personality conflicts that become more transparent due to openness might impede inspection. Still others point out that familiarity and (preexisting) relationships among inspection team members negatively affect the comprehensiveness in detection of defects. This brings up concerns if the openness as originally envisioned by Fagan may in fact lead to suboptimal outcomes. As the trend towards computer-based inspection continues, we believe that anonymity could play a positive role in overcoming some of the drawbacks noted in team-based inspection. Drawing upon the literature on software inspection and group support systems, this research proposes possible influences of group member anonymity on the outcome of computer-mediated software inspection and empirically examines the validity of the posited relationships in a set of controlled laboratory experiments. Two different inspection tasks with varying levels of software code complexity are employed. While both the control groups (i.e., teams without anonymity) and treatment groups (i.e., teams with support for anonymity) consume more or less the same time in performing the inspection tasks, the treatment groups are more effective in identifying the seeded errors in the more complex task. Treatment groups also express a more positive attitude toward both code inspection tasks. The findings of the study suggest a number of directions for future research.