|A Collection of Informative and Interesting Articles|
|HOME||LOGIN||SUBMIT ARTICLES||TOP AUTHORS||WANT AN ACCOUNT?|
What is Code Review Process?BY: Arivuvel Ramu | Category: Technology | Submitted: 2010-06-16 06:27:45
Article Summary: "Help your team to understand the importance of code review and the implementation strategy.."
Overview: Help your team to understand the importance of code review and the implementation strategy.
Code review is the key process of stream lining and standardizing the implementation artifacts and deliverable up to the mark to meet the internal or external SLA.
1. Code Review Process Established in the project team
2. Code Review panel or Gate Keeper needs to be indentified
3. Define the Code Review checklist
4. Define the coding guidelines
5. Define the Naming conventions across the reference architecture layers components
6. Prioritize the Review comments Severity
7. Needs to have the Review comments tracking System (Bug tracking system can be used)
Types of Code Review Activity:
1. Desk Review
2. Peer Review
3. Panel Review
4. Client Review
Desk Review /Informal Review:
1. As a Senior Developer/ team lead / Project lead can sit with developer in his machine and check the complex component implementation.
2. Review the naming convention, number of lines per method or class and for loop, if else ladder, Map or List or array usage and review the developer business logic understanding and implementation.
3. Provide the on the fly review comments to the developer to focus on the key implementation skeleton.
1. As part of any logical component implementation completion, the developer can call for the Peer Review.
2. Peer will be identified with in his track/team and the code artifacts needs to be submitted to the peer by the developer
3. Identified peer will review the code artifacts against the coding checklist as well with the help of coding guidelines
4. Peer will provide the review comments to the appropriate developer and Keep the Team Lead/Project lead in the communication loop.
1. Panel will be identified with in the project
2. Panel consist of Architect, SME, Lead, Senior Developers (max 5- 8 people)
3. End of Specific Service or Functionality formal component implementation completion, the code or deliverable will be submitted to the Panel by the respective track or team lead.
4. Panel member will do the offline review on the code/artifacts thoroughly
5. Panel needs to check the Implementation strategy, design pattern, reusability, QoS and the functional logic implementation.
6. Panel will gather in the Meeting room and the team lead /code owner will present the code to panel and walkthrough the artifacts.
7. Panel will raise the concern or identified gap in the meeting and the panel member will discuss the gaps.
8. Finally the panel will recommend the refactoring or approve the code for baseline.
9. All the review comments will be prioritized under one of the following criteria such as Development change/refactoring, bug, design issue, requirement missing, Change Request etc
1. After the panel review ,the code will be given to the Client Technical panel (if your project structure has this?) and receive their inputs for further beautification in your client deliverables.
Finally your project manager will take the summary of the code review metrics from the tool and use that for code quality metrics/ SLA Base line.
About Author / Additional Info:
Technical Architect (SOA)
Comments on this article: (1 comments so far)
• MySpace Social Networking Site: What it is all About
• Moving Home With Pets
• Why Go For Executive MBA in India?
• Love and Its Meaning
Latest Articles in "Technology" category:
• Security Robots on Patrol
• Apple Pay Overview
• Enterprise Mobility - Overview Part 1
• M-OTA: Mobile 'Over-The- Air' (OTA) Overview
• MDM: Mobile Device Management Overview
• 3M MAC Protocol Review
• Build, Deploy and Test - Advanced Software Development Practice - Part 1
Important Disclaimer: All articles on this website are for general information only and is not a professional or experts advice. We do not own any responsibility for correctness or authenticity of the information presented in this article, or any loss or injury resulting from it. We do not endorse these articles, we are neither affiliated with the authors of these articles nor responsible for their content. Please see our disclaimer section for complete terms.
Copyright © 2010 saching.com - Do not copy articles from this website.
|| Home | Disclaimer | Xhtml ||