The code review process only checks the quality of code not the functionality. The process is not intended to replace the testing process but simply to assure the quality of the code produced.

Failure of an upgrade does not reflect on the proficiency of the programmer. It simply means the modifications have varied from the expected standards.

In the event of an upgrade failing the review areas of concern will be noted on the review document and the details passed back to the originating team for re-working. Revisions will never be undertaken by the reviewer.

The following notes are the guidelines that will be used by the review team to assess the modifications made to LIFEfit. They are loosely based on the current production standards but are not intended to replace them.