HW26: Chapter 24

24.6: Briefly explain what happens during the software quality review process and the software quality inspection process.

There are three different phases in the software quality review process:

The pre-review activities help prepare for the review to be executed effectively.  This includes setting up a review team, arranging times and locations to review, and the distribution of appropriate documents.  The review team may meet during this phase to get an overview of the software.  They also work individually to look over the the software.  

The review meeting is then held, in which the authors of the software or documentation walks through the document with the review team.  All review decisions and and actions to be taken should be recorded and given to the chair of the review team.  The chair should also ensure that all comments are considered and sign a record at the end.

The post-review activities involve addressing the comments raised in the review meeting.  This includes fixing bugs and refactoring, as well as making documentation changes. If there are large issues discovered in the review, they may be sent to management to make the decision on how to handle it.  After the updates, there may be another review or simply an approval that all the comments have been addressed.  

In the software quality inspection process, team members collaborate to find bugs in the software.  This involves verifying versions of the software and doing test reviews.  Inspectors must make a detailed review of each line in the source code.  Any errors or issues are discussed in an inspection meeting.  Organizations may develop their own checklists of common errors which take into account company standards.  This helps inspectors identify errors in the code more easily.  


Popular Posts