Scribd
Upload
69 views2 pages

Checklist For Code Reviews

The document provides a checklist for reviewing code for tightness, accuracy, completeness and adequate documentation. The checklist contains questions about design translation, language conventions, comments, data types, constants, redundancy, maintainability, data and subprogram references, computations in loops, expressions and efficient data processing.

Uploaded by

ABINOU OUNIBA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
69 views2 pages

Checklist For Code Reviews

The document provides a checklist for reviewing code for tightness, accuracy, completeness and adequate documentation. The checklist contains questions about design translation, language conventions, comments, data types, constants, redundancy, maintainability, data and subprogram references, computations in loops, expressions and efficient data processing.

Uploaded by

ABINOU OUNIBA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd

Checklist for Code Reviews

Confidentiality Statement
This <document title> along with all attachments hereto shall be considered <company>’s
Proprietary/Confidential Information
gantthead.com Checklist for Code Reviews

The following checklist contains questions to keep in mind when reviewing code for
tightness, accuracy, completeness and adequate documentation. If the code is
constructed with care and attention to these details, the development process will be
quicker and less error-plagued and the maintenance process will be smoother.

This checklist assumes that a design walkthrough has been conducted and that
algorithm correctness has been established as part of the design review.

 Has the design been properly translated into code? (The results of the procedural
design should be available during this review.)

 Is the code free of misspellings and typos?

 Has proper use of programming language conventions been made?

 Is there compliance with coding standards for language style, comments, module
prologue?

 Are all comments accurate and unambiguous?

 Are comments useful and not simply explanations to suffice for poor coding?

 Are data types and data declarations appropriately used?

 Are physical constants correct?

 Is the code free of redundant operations for which there is no compensating benefit?

 Is the code maintainable?

 Are all referenced data defined, computed, or obtained from external source?

 Are all defined data used?

 Are all referenced subprograms defined?

 Are all defined subprograms used?

 Are all non-loop dependent computations kept out of loop?

 Are all compound expressions defined once?

 Are data grouped for efficient processing?

 Are data indexed and referenced for efficient processing?

©2007 gantthead.com 2

You might also like