A technique of examining documentation or code with a view to detecting, recording and tracking faults, communicating information and improving the development process.

[Source: <>BCS]


It is almost always cheaper and quicker reviewing documentation or code rather than testing the resulting product or service. It is also always cheaper fixing faults found during a review than it is fixing the product or service after it has been prepared for testing.

There are a number of different kinds of review that can take place, depending upon the stage of the software process. These range in formality and the people that attend them. With all reviews, preparation must be done beforehand by all participants to ensure that everyone can contribute to the review.

Reviews are often unpopular as they appear time consuming. This time though is less than is taken up with trying to correct a fault that is found at a much later stage.

Contact acutest