About Software Testing (5): First acquaintance with peer Review

First, background: This week's software testing in the classroom, we in the case of self-grouping, Yao classmate's car parking location management system has peer Review, Chinese is peer test. This is the first time I've been in touch with peer testing, so let me introduce peer review.

Second, peer review definition: is a way to identify defects through the author's peers and need to change the area of the inspection method. Specific products that require peer review are identified during the definition of the project software process and as part of the Software development plan

Part of the schedule is scheduled.

Third, Peer review personnel distribution:

In this it is necessary to use the review team, the review team consists of at least 3 people (including the author of the material being examined), generally 4 to 7 people. Typically, a more detailed review of the design documentation is required, and a review of the technical details requires fewer reviewers. The review team should include the following roles:

• reviewers (Reviewer, Inspector): Each member of the judging panel, whether or not he or she is a moderator, author, read-out, recorder, is a reviewer. Their role is to examine the materials reviewed during the pre-preparatory phase and to identify deficiencies. The right candidate for the reviewer includes the relevant developer in the previous, current and next stages of the material being examined in the life cycle. For example, a requirement analysis reviewer can include a customer and a profile designer, and a reviewer of detailed design and code can include a profile designer, a related module developer, and a tester.
• Moderator (Moderator): The main responsibility of supporting people in the review before the formal technical review plan and pre-preparation of the inspection, in the review will be responsible for mobilizing each reviewer at the review meeting of the enthusiasm, to grasp the direction of the review will ensure the effectiveness of the review process After the review meeting, responsible for the classification of the problem and the revision of the question after the review.
• The Reader 's task is to guide the review team through reading and staging at the review session to traverse the material being examined. In addition to the code review you can choose the author as the Reading Squire, the other reviewers preferably choose to participate directly in the follow-up development phase as the reading staff.
• The Recorder (Recorder) Recorder is responsible for documenting the software issues found at the review meeting in the technical review issue record sheet. Any issues raised at the review meeting that have not yet been resolved and any errors in the pre-order work products should be recorded. author (Author)

The author of the material being examined is responsible for answering questions raised by the assessors at the review meeting, so as to avoid the obvious misunderstanding being treated as a problem.　　　　In addition, the author shall be responsible for amending the issues identified at the review meeting. In our classroom test, our group of six people, the jury has two, each other. I play the role of the author. Iv. purpose of Peer review:

• Discover and identify defects in software products as early as possible.
• Identify the parts of the product that should be improved and improved as early as possible and implement them early.
• Project members through peer review, can better understand the software products, to prevent the occurrence of some errors.

V. The process of peer review:

Two flowchart for online search:

　

In this mock-up test, we put forward a series of questions about the project of Yao's classmates, and I as the author to answer their questions or to give the improvement program, so as to update the project plan. Ultimately, in general, Yao's project has some help.

Six, Harvest

This simulation peer review brings me the feeling is that different perspectives will produce a great chemical reaction, often you can see through other people's perspective of the project's shortcomings can also be found in their own project light point to improve and optimize it. This is an activity that has a great impetus for the entire team.

About Software Testing (5): First acquaintance with peer Review