CFP last date
20 December 2024
Reseach Article

Achieving Code Quality using Code Review System

Published on April 2012 by Snehal Bhosale, Shraddha Bhosale, Varsha Bhalerao, Ketan Bhagwat
Emerging Trends in Computer Science and Information Technology (ETCSIT2012)
Foundation of Computer Science USA
ETCSIT - Number 1
April 2012
Authors: Snehal Bhosale, Shraddha Bhosale, Varsha Bhalerao, Ketan Bhagwat
c9246562-0053-498a-9ac1-0844462b8de6

Snehal Bhosale, Shraddha Bhosale, Varsha Bhalerao, Ketan Bhagwat . Achieving Code Quality using Code Review System. Emerging Trends in Computer Science and Information Technology (ETCSIT2012). ETCSIT, 1 (April 2012), 24-27.

@article{
author = { Snehal Bhosale, Shraddha Bhosale, Varsha Bhalerao, Ketan Bhagwat },
title = { Achieving Code Quality using Code Review System },
journal = { Emerging Trends in Computer Science and Information Technology (ETCSIT2012) },
issue_date = { April 2012 },
volume = { ETCSIT },
number = { 1 },
month = { April },
year = { 2012 },
issn = 0975-8887,
pages = { 24-27 },
numpages = 4,
url = { /proceedings/etcsit/number1/5964-1007/ },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Proceeding Article
%1 Emerging Trends in Computer Science and Information Technology (ETCSIT2012)
%A Snehal Bhosale
%A Shraddha Bhosale
%A Varsha Bhalerao
%A Ketan Bhagwat
%T Achieving Code Quality using Code Review System
%J Emerging Trends in Computer Science and Information Technology (ETCSIT2012)
%@ 0975-8887
%V ETCSIT
%N 1
%P 24-27
%D 2012
%I International Journal of Computer Applications
Abstract

The purposes for code review are as diverse as the environments in which they are conducted. However, almost all code reviews have these goals in common: 1. Defect-free, well-documented software. 2. Software that complies with enterprise coding standards. 3. Teaching and sharing knowledge between developers. Other objectives often include: maintainability, security, and consistent end-user documentation, adequate comments in code, complete unit tests, and scalability.

References
  1. White Paper 'Why review code?' by Jason Cohen, Smart Beer Software, inc.
  2. White paper on 'Peer code review: an agile process' This paper was originally published by Smart Bear Software in the proceedings of the Agile Development Practices conference in November 2009.
  3. A. Harel: 'Estimating the Number of Faults Remaining in Software Code Documents Inspected with Iterative Code Reviews' in Computer Science Dep. Technion.
  4. Alan Page: 'Peering Into the White Box: A Testers Approach to Code Reviews' in Microsoft Corp.
  5. A Borland White Paper By Richard C. Gronback: 'Software Remodeling: Improving Design and Implementation Quality' in January 2003.
  6. T. A. Gonsalves & Hema A. Murthy: 'Code Review Guidelines' TeNeT Group, IIT-Madras. In 7/11/2001.
  7. Nathaniel Ayewah, WilliamPugh: 'Using FindBugs On Production Software' University of Maryland
  8. ayewah,pugh@cs. umd. edu and J. David Morgenthaler, John Penix, YuQian Zhou Google, Inc. jdm,jpenix,zhou@google. com.
  9. EFindbugs: Effective Error Ranking for Findbugs. Haihao Sheny_, Jianhong Fangz, and Jianjun Zhaoy ySchool of Software Shanghai Jiao Tong University, 800 Dongchuan Road, Shanghai 200240, China
  10. Identifying Changed Source Code Lines from Version RepositoriesGerardo Canfora, Luigi Cerulo, Massimiliano Di Penta RCOST — Research Centre on Software Technology
Index Terms

Computer Science
Information Sciences

Keywords

Keywords Are Your Own Designated Keywords Which Can Be Used For Easy Location Of The Manuscript Using Any Search Engines