Cleanroom Software Development: An Empirical Evaluation
IEEE Transactions on Software Engineering
Comparing the Effectiveness of Software Testing Strategies
IEEE Transactions on Software Engineering
Structured walkthroughs: 4th edition
Structured walkthroughs: 4th edition
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Software inspection process
Evolving and packaging reading technologies
Journal of Systems and Software - Special issue on achieving quality in software
Extreme programming explained: embrace change
Extreme programming explained: embrace change
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
SIGSOFT '00/FSE-8 Proceedings of the 8th ACM SIGSOFT international symposium on Foundations of software engineering: twenty-first century applications
A controlled experiment in program testing and code walkthroughs/inspections
Communications of the ACM
Peer reviews in software: a practical guide
Peer reviews in software: a practical guide
Software Inspection
Structured Programming; Theory and Practice the Systems Programming Series
Structured Programming; Theory and Practice the Systems Programming Series
Proceedings of the 24th International Conference on Software Engineering
Attaining Level 5 in CMM Process Maturity
IEEE Software
Quantitative Modeling of Software Reviews in an Industrial Setting
METRICS '99 Proceedings of the 6th International Symposium on Software Metrics
An experimental analysis of program verification methods.
An experimental analysis of program verification methods.
Software Reviews: The State of the Practice
IEEE Software
Impact of software engineering research on the practice of software configuration management
ACM Transactions on Software Engineering and Methodology (TOSEM)
The impact of software engineering research on modern progamming languages
ACM Transactions on Software Engineering and Methodology (TOSEM)
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Evaluating a model of software managers' information needs: an experiment
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Impact of process simulation on software practice: an initial report
Proceedings of the 33rd International Conference on Software Engineering
Hi-index | 0.00 |
Software inspections, reviews, and walkthroughs have become a standard process component in many software development domains. Maturity level 3 of the CMM-I requires establishment of peer reviews [12] and substantial sustained improvements in quality and productivity have been reported as a result of using reviews ([16], [21], [22], [27]). The NSF Impact project identifies the degree to which these industrial success cases have been instigated and improved by research in software engineering. This research identifies that there is widespread adoption of inspections, reviews or walkthroughs but that companies do not generally exploit their full potential. However there exist sustained industrial success cases with respect to the wide-spread and measurably successful application of them. It also identifies research in software engineering that can be credibly documented as having influenced the industrial success cases. Credible documentation may exist in the form of publications or documented reports by witnesses. Due to the semi-formal nature of inspections, reviews, and walkthroughs, a specific focus is given to empirical research results as motivators for adoption. Through the examination of one detailed case study, it is shown that software engineering research has had a significant impact on practice and that the impact can be traced in this case from research to that practice. The case study chosen provides evidence of both success and failure regarding sustained application in practice. Thus the analysis of historic impact chains of research reveals a clear impact of software engineering research on sustained industrial success for inspections, reviews and walkthroughs. More importantly, in impact chains where the empirical results have not been established, we conclude that success has not been achieved or has not been sustained. The paper closes with (1) lessons learned for creating the sustained use and impact of semi-formal software engineering processes, (2) a request for researchers and practitioners to further consider how their work can improve the effectiveness of research and practice, and (3) a request to contribute additional success cases and impact factors to the authors database for future enhancements of this paper.