One way of ensuring good quality is by creating a test suit that actively test the code to fine flaws. Another way is to comb through the code and verify there are no errors in the logic. This process in known as a software technical review.
A software technical review consists of 4 parties, the producer, the recorder, the review leader, and the reviewers.
The producer is the entity that develops the code this could be a single developer and development team or an outside company. They are responsible for providing a frozen copy of the code and a set of requirements and expectations. It is important that the code does not change during the technical review process.
The recorder is responsible for taking notes and documenting what takes place during the review.
The review leader is responsible for scheduling the review, suppling what is necessary for the review, as well as producing the final report and sharing the findings.
The code reviewers as well as the leader and the reported are responsible for looking through the code before the meeting and documenting all errors of other issues found in the code.
During the review each member shares what they found and compares it to the others. As a group the determine if what is found is actually an issue that needs to be fixed. The team does not make suggestions to how the issues can be resolved.
The review leader then takes the information from the review session and generates a final report to be shared with the producer.
From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.
