Web Site

Economy-point.org



» Economics » Quality management (software technology) » Topics begins with C » Codereview


Page modified: Friday, June 23, 2006 20:31:10

Codereview designates the examination of source texts (source text review) by another person. The procedure of the Codereview serves for to the improvement and quality assurance of computer programs.

With the Codereview a program section, after or during the development, is correction-read of one or more consultants, in order to find possible errors, simplifications or cases of test. The consultant can be a software developer. For inexperienced developers the Codereview offers a good possibility by an experienced programmer of training itself further fast and practice-orientedly.

Frequently a Codereview runs off in such a way that the creator of the code (programmer) explains the code to the Rezensenten (consultant). It is explained, why and how something was programmed. Results are improved code (efficiency, robustness, maintenance) in addition, improved comments in the code (maintenance).

Different quality processes run off:

  • The programmer discovers a possibility for improvement (often seconds before the Reviewer this sees).
  • The Rezensent places understanding questions and the programmers can the answer to these questions as comments into the program code build and so the comprehensibility and the documentation improve.
  • The Rezensent discovers possibilities for improvement and recommends these to the programmer.

Requirements at Rezensenten

  • It may not have written the code.
  • It must have clock feeling: Codereviews can be unpleasant for the programmer, since the own code is criticized. If it does not proceed tactfully, resistance and refusal are developed against the examination of the source texts.

Groups of individuals make it possible on-line software to Repositories such as CVS to accomplish jointly Codereviews to improve and thus security and quality of the program code.

Continuous examining of the source text as during pair programming is also one of the methods extremes of the Programming. In extremes Programming (XP) assigned pair programming, also "„Codereview during the development "“one calls. XP-advocates argue that other XP-practices, as Refactoring and the letter from tests produce better code, which does not have so frequently sighted or again written to beginning of the code development, like traditionally developed code. Thus the software development one accelerate.

Examples of how Codereviews improved a project:

  • Blender - the 3D-Grafikdesign-Paket was strongly improved by an open SOURCE development community.
  • The Linux Kernel - once as hobby of a Finnish programmer written, he was world-wide sighted and revised meanwhile of hundreds of programmers.

Automated Codereview software simplifies the task of the examination of large program sections by systematic examinations on places open to attack how:

  • Race conditions
  • Format stringer attacks
  • Buffer over runs
  • Memory leakage

Flawfinder and Rough Auditing Tool for Security (ADVICE) are two well-known tools for the Codereview.

Related links


Articles in category "Codereview"

We found here 3 articles.

C

» Capability Maturity Model integration
» Code Walkthrough
» Codereview

Related Websites

We found here 5 related websites.

Page cached: Wednesday, July 5, 2006 14:58:48
Valid XHTML 1.0!  Valid CSS!

Page copy protected against web site content infringement by Copyscape