Question

What is the difference between code inspection and code review?

1) Code inspection examines the whole program and is expensive if the program changes, while code review examines each change and is good if a new concern arises.
2) Code inspection examines each change and is good if a new concern arises, while code review examines the whole program and is expensive if the program changes.
3) Code inspection examines each change and is good if the definition of "good" changes, while code review examines the whole program and is expensive if the program changes.
4) Code inspection examines the whole program and is good if a new concern arises, while code review examines each change and is expensive if the program changes.

Answer 1

Code inspection is a formal process examining the whole program and can be expensive with frequent changes, while code review is less formal, focuses on each change, and is better for addressing new concerns as they arise.

Step-by-step explanation:

The difference between code inspection and code review is primarily in their process and focus during the software development life cycle. A code inspection is a more formal process that involves examining the whole program to find defects. It is typically a very thorough examination by someone other than the author, often following a strict procedure with a checklist, and it can be expensive in terms of time and resources, especially if the program has frequent changes. Code review, on the other hand, is generally less formal and involves examining each change made to the codebase. It is usually conducted by peers and is a good practice for continuous improvement and for catching issues as they arise. Code review is conducive to an evolving program as it addresses new concerns with each iteration of the code.

Therefore, the correct statement from the options provided is: Code inspection examines the whole program and is expensive if the program changes, while code review examines each change and is good if a new concern arises.