[Original summary] Peer Review

In "The top of the Tide", Wu teacher described the early work of Google, a part of the said: I usually after dinner to the code modified list sent to Craig to do code review, he generally at night around 10 o'clock will reply to me, give me a change of opinion, detailed to a line more a space. This content is actually the process of peer review in the process of software development.

Naturally, in some of the small projects we do, it is also a small peer Review to test each other for bugs before submitting the project.

Purpose
Extended to the actual software project operation process, in the formal software management process, peer review is a very effective way to control the error. The following are some good results:
Can be a good solution in the method, logic, implementation of the role;
Ensure that the product is relevant to demand
Gives the manager a good understanding of the quality of the entire product
Communicate the different methods
From the perspective of others, not just the author. Support or modify products
It is easy to find the current opportunity in the discussion
Facilitates timely discovery and solves issue.

Range
The object of peer review is not just the code we talked about and the product specifications we discussed in class, it runs through the entire software development phase:
Should we do this project? (Demand Phase)
Product Requirement Specification, etc.
Can We do this project? (Planning Phase)
System solutions, project plans, etc.
is we doing this project? (development phase)
Detailed design, unit test scenarios, integration test scenarios, code, database scripts.
In particular, detailed design reviews are needed before coding.
Did we do this Project? (Validation phase)
System test Scenarios

In fact, in conclusion, we are going to review all important project that may have potential defects.

[Implementation Method]

[People role]
Author:
The original author of the work;
To answer questions raised by others about the product during the meeting;
Not as moderator, Reader, Recorder.

Moderator:
To plan this inspection meeting man
Take control of the meeting
Last reports inspection results to Peer Review Coordinator

Reader:
Responsible for showing this product to other inspectors

Recorder:
Classify and record in meeting the issue that everyone put forward

Inspector:
The person who found the defect
Strictly speaking-everyone in the meeting is inspector.

[Original summary] Peer Review