Software Peer Review:

In software development, peer review is a type of software review in which a work product (document, code, or other) is examined by its author and one or more colleagues, in order to evaluate its technical content and quality.
The purpose of a peer review is to provide "a disciplined engineering practice for detecting and correcting defects in software artifacts, and preventing their leakage into field operations" according to the Capability Maturity Model.
When performed as part of each Software development process activity, peer reviews identify problems that can be fixed early in the lifecycle. That is to say, a peer review that identifies a requirements problem during the Requirements analysis activity is cheaper and easier to fix than during the Software architecture or Software testing activities.
In the most traditional approach to peer review, known as single-blind review, reviewers know the author's identity, but not vice versa. Blinding the identity of reviewers enables them to comment freely and not worry about disgruntled authors seeking retribution for negative reviews. Another approach is double-blind review, in which the identities of the author and referees are both hidden, making it easier for reviewers to focus on the paper itself without being swayed by any preconceived ideas about the author or his institution. Finally, many have adopted open peer review. In this model, the author's and reviewers' identities are known to each other, a situation that forces reviewers, who can't hide behind a veil of anonymity, to provide more thoughtful critiques.