Recommendations for Conducting Software Reviews

Recommendations for Conducting Software Reviews

Yuk Kuen Wong (Griffith University, Australia)
Copyright: © 2006 |Pages: 13
DOI: 10.4018/978-1-59904-013-4.ch011


This chapter provides recommendations for conducting software reviews in software development environments. It is recommended that the software review process planning should consider three issues. These include: 1) decision on the selection of inputs, 2) a determination of the level of review meetings required, and 3) identifying the measurement metrics. For researchers, it is recommended that 1) future research should pay more attention to important relationships between software artefact characteristics and the use of supporting documents, 2) designing and conducting laboratory studies be done more realistically, 3) direct and indirect relationships between the use of inputs as predictors for software review performance, 4) the important relationships between the software artefact characteristics and meeting process factors, 5) meetings should be held when the artefact is complex, of large size and poor initial quality, 6) the use of previously reviewed software documents in relation to meeting process, 7) perceived contingency (motivation) is the most critical factor to meeting process, and 8) future studies should further concentrate on the use of previously reviewed software documents in combination with the implicit inputs, process, and performance.

Complete Chapter List

Search this Book: