Text below the image describes the process in greater detail.

Enlarge Image

The process starts with a developer who has changes that need to be reviewed. In some organizations code review is done "as needed;" in others code review is manditory.

Creating New Reviews: The developer requests a new review from the Code Reviewer application. He is prompted to select the set of files he wishes to have reviewed. A comment tells the reviewer what to expect and is also preserved in version control. Finally, the developer assigns the review to one of the reviewers in his list.

Performing Reviews: The review is delivered to the specified reviewer. The reviewer can see all files selected by the developer and view changes in a convenient side-by-side before/after screen. The reviewer also gets a list of all prior changes to the file and can elect to see the before/after on any of them as well.

The reviewer can comment directly on the before/after screen. Individual lines of code can be highlighted. Comments can be marked "block check-in" which means the developer is not permitted to check in these changes because of some significant problem.

If a Reviewer Check-List has been created, the reviewer must check off each item for every file he accepts as "OK."

When the review is complete, the reviewer can pass a review off to another reviewer or can submit the review back to the developer.

Returned Reviews: The developer receives the returned review and can see all comments made by the reviewer. Files can be viewed or edited directly from the Returned Review dialog.

If changes are made, the review can be sent back to a reviewer with the new changes intact. The review can also be deleted.

If the reviewer accepted all files, the developer can submit all files into version control with all comments and communication used as the change comment.