Code review

Static analysis relies primarily on automated tools, self-checks involve only the author, testing requires code execution, and pair programming is performed continuously during development rather than as a separate step.

[6] Historically, the first code review process that was studied and described in detail was called "Inspection" by its inventor, Michael Fagan.

[7] Fagan inspection is a formal process that involves a careful and detailed execution with multiple participants and phases.

[3] Major software corporations including such as Microsoft,[9] Google,[10] and Facebook follow a change-based code review process.

[24] A 2012 study by VDC Research reports that 17.6% of the embedded software engineers surveyed currently use automated tools to support peer code review and 23.7% planning to use them within two years.