Example of Code Review Guidelines, providing a look at the whole landscape of a good code review process, along with detailed checklists and forms for capturing what's found in the reviews.
What this is
Example of a company guideline for how to conduct formal software code reviews. It includes the following contents:
Why it's useful
A good review requires more than just a good meeting! Good code reviews that catch mistakes and communicate critical changes require preparation, appropriate off-line review, and good records. This example of Code Review Guidelines from a medical device development company coding in C provide an excellent look at the whole landscape of a good code review process, along with detailed checklists and forms for capturing what's found in the reviews.
This particular company created medical devices and coded the embedded software in C. Their development process had to be stringent enough to ensure that "safety-significant" errors were caught during reviews and testing. They also had to be able to show regulatory agencies at any time that their project followed a process that reviewed designs for problems (especially those that could cause a danger of harm to a patient on whom the device was being used), recorded those problems, then fixed the problems. This code review process was part of their documented development process.
Note, however, that such a code review guideline is useful for other types of software products as well! Any software group wanting to improve the quality of their code and the actual reviews can benefit from elements of this process. The payoff will be finding more problems sooner rather than later- on paper rather than during testing or beyond.
How to use it
During a project, such a document is used by team members in the following way:
©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail firstname.lastname@example.org