Code Review

Use the information in the web article Effective Code Reviews Without the Pain for methods and best practices for conducting a code review, and tips for conducting the review remotely.

http://www.developer.com/tech/article.php/3579756/Effective-Code-Reviews-Without-the-Pain.htm

When reviewing the code fragment, the review team will look for problem areas in the code and make recommendations for fixes. Problem areas in the code might include the use of global variables, lack of comments or documentation in the code, failure to meet requirements, incorrect logic, the inefficient use of memory, input validation, problems with exception handling, and no use of naming conventions, to name a few. Recommendations might include items such as running efficiency tests and introducing naming conventions for maintainability.

Document your findings in your report. Make sure to include the following:

• Problem areas in the code and recommendations for fixes or improvements

If you find no problems within the code, note that, and specify what problem types you checked for that the code successfully avoided

• Greater modularity incorporated during the design phase

Please locate and include resources on the web that support your recommendations.

Attachment:- Assignment File.rar