Also I need a separate document that explains why the factors were chosen and how I feel they would be important to the quality assurance process of reviewing a programmers written code/ program.
|
Name Of Computer Programmer:
|
XX
|
|
Reviewed By:
|
XXX
|
|
Program Name and Version ID:
|
XXXX
|
|
Name of Program
|
Content
Rating 1-10
|
Design
Rating 1-10
|
Codes or Programming Comments
|
|
XXX
|
|
Program Execution
|
|
|
|
|
Application Starts Correctly?
|
|
|
Compile
|
|
|
|
|
Build
|
|
|
|
|
Linked files
|
|
|
|
|
Proper input
|
|
|
|
|
Do the identifier heading Appropriate the ID of the Program?
|
|
|
|
|
Ambiguous
|
|
|
|
|
Name of Program
|
|
|
|
|
Version
|
|
|
|
|
Tagging ETC.
|
|
|
|
|
Code clean for review
|
|
|
|
|
Unnecessary code
|
|
|
|
|
Constants/variables appropriately named?
|
|
|
Naming Conventions
|
|
|
|
|
Understood
|
|
|
|
|
Compatible
|
|
|
|
|
Level of consistency
|
|
|
|
|
Does the code indicate structure is it easily understood by the reviewer?
|
|
|
Purpose of program
|
|
|
|
|
Design Specifications
|
|
|
|
|
Structure of Code
|
|
|
|
|
Comments support design
|
|
|
|
|
Problems noted
|
|
|
|
|
Solution recommendations
|
|
|
|
|
Does the written program have indentations and comments to support its function?
|
|
|
|
|
Use of space
|
|
|
|
|
Organization
|
|
|
|
|
Indentations
|
|
|
|
|
Code Blocks Defined
|
|
|
|
|
Confusing Comments
|
|
|
|
|
Unneeded comments
|
|
|
|
|
Reviewer's comments that support a positive feedback and explains possible problems.
|
|
|
Positive Feedback
|
|
|
|
|
Recommended changes
|
|
|
|
|
Program End By User
|
|
|
|
|
|
|
|
|