Advances in software inspections
IEEE Transactions on Software Engineering
A Two-Person Inspection Method to Improve Programming Productivity
IEEE Transactions on Software Engineering
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
Assessing software review meetings: a controlled experimental study using CSRS
ICSE '97 Proceedings of the 19th international conference on Software engineering
An experiment to assess different defect detection methods for software requirements inspections
ICSE '94 Proceedings of the 16th international conference on Software engineering
Active design reviews: principles and practices
ICSE '85 Proceedings of the 8th international conference on Software engineering
IEEE Transactions on Software Engineering
Evaluating Capture-Recapture Models with Two Inspectors
IEEE Transactions on Software Engineering
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products
Software Inspection
Software Inspections: An Effective Verification Process
IEEE Software
Comparing Inspection Strategies for Software Requirement Specifications
ASWEC '96 Proceedings of the 1996 Australian Software Engineering Conference
Experience, gender composition, social presence, decision process satisfaction and group performance
WISICT '04 Proceedings of the winter international synposium on Information and communication technologies
Hi-index | 0.00 |
The effects in the empirical study of different kinds of inputs on the software inspection process can be classified into explicit inputs and implicit inputs. Explicit inputs are the software artifacts to be inspected, the documentation and inspection aids used by the inspectors. Implicit inputs include inspectors' expertise, norms, beliefs and values.