Code Review Process

Systematic examination of computer source code by peers.

To improve the quality of the document and help the authors.

Formal reviews follow a structured and managed process.

<p>To detect all faults, violations, and side-effects.</p> Signup and view all the answers

<p>When the code is in a reasonable state of readiness after basic desk checking and walkthroughs.</p> Signup and view all the answers

<p>Multiple views.</p> Signup and view all the answers

<p>Take detailed notes and circulate them to the inspection team after the meeting.</p> Signup and view all the answers

<p>Call for a review meeting to inspect the fixes.</p> Signup and view all the answers

<p>To focus on the technical content of the document.</p> Signup and view all the answers

<p>A trained moderator or a technical expert.</p> Signup and view all the answers

<p>To evaluate the value and consistency of technical concepts in the document.</p> Signup and view all the answers

<p>Line coverage or segment coverage.</p> Signup and view all the answers

<p>To improve the quality of software by finding errors in early stages of the development cycle.</p> Signup and view all the answers

<p>Reduce development time and increase development productivity.</p> Signup and view all the answers

<p>A less formal group-oriented method where a set of people checks program code and raises questions for the author.</p> Signup and view all the answers

<p>Walkthroughs are less formal than inspections and are not a formal process.</p> Signup and view all the answers

<p>It helps in fulfilling common understanding and collecting feedback.</p> Signup and view all the answers

<p>The author guides the review team through the document to ensure common understanding.</p> Signup and view all the answers