"Software Testing" peer review

first, the definition
Peer review is an inspection method that verifies defects and needs to change areas through the author's peers (development, testing, QA, etc.).
second, the process
(i) Planning phase
1. The project leader designate the organizer, the author self-inspection work product, the organizer plans This review, formulates the review plan
2. Check the entry criteria: is compliance with the documentation standards? Have you checked with the tool? Code <=500 Line; Document <=40 page;
3. Prepare the Review package: Review notice, pending Review product, reference, review form (Review form), review plan (Review plans)
4. Identify the review experts 3-6 people, select the principle: Review objects in the life cycle of the previous stage, the current stage and the next stage of the participants (that is, and the review object related to the person)
5. The organizer sends the review package, the review notice to the relevant person
(ii) introductory meeting (* optional)
1. Do not understand the process and product technology is more difficult, the technology is relatively new, by the experts, the author explains the relevant products and processes
2. The time does not exceed 1 hours, 30-60 points is advisable
(iii) preparatory phase (most important, most defects found)
1. The review expert individual completes the work product the examination, proposes the flaw, fills in the appraisal form, the feedback review form to the organizer
2. The preparation time is greater than the meeting time and should begin 2 days before the meeting
3. Organizer: Summarize and review the review form, decide whether to increase the evaluation input (increase the preparation time, increase the number of experts to review, change the review experts, etc.)
(iv) Review meeting (questions only, not addressed)
1. Organizer holds a review meeting (cannot be author)
2. Instructors explaining work products (not authors or organizers)
3. Common identification of issues (issues recorded in the review form, problems identified at the meeting), and decisions by the organizer
4 The Recorder records all questions and sends them to the organizer
5. The Organizer updates the review form (problem identification, root cause, prevention/corrective action)
(v) third-hour meeting (* optional)
unresolved or controversial issues at the review meeting, the author decides whether to convene
(vi) Rework
The author modifies the work product and updates the review form
(vii) Tracking
1. The organization review expert confirms that the defects have been modified and that no new defects have been introduced;
2. Assist the Organizer to confirm that the relevant issues have been correctly modified and that no new defects have been introduced;
3. Summarize all required data to the review form and send it to the relevant review experts
4. Whether to re-re-review

"Software Testing" peer review