On Peer Review (peer review)

This week's software testing technology, we have access to peer review (peer Review), and combined with the testing of parking manuals for example analysis. So below I will briefly introduce what is the PR?

from Wikipedia, we know that Peer review (peer Review, also known as refereeing in some academic fields), or peer review , is an academic results review process, That is, an author's academic writings or plans are reviewed by other experts and scholars in the same field. The general academic publishing units are mainly peer-reviewed methods to choose and select the manuscript to be delivered or not, and academic research funding providers, also widely in a peer-reviewed way to decide whether to grant funds, bonuses and so on. The main purpose of the peer review process is to ensure that the author's work level conforms to the standards of the general academic and the subject area. The publication of books in many fields or the awarding of research bonuses, if not conducted in a peer-reviewed manner, may be more questionable, or even become the primary criterion for the publication or work to be called academic publications.

We all know that the complete formation of a software needs to be divided into the following stages:

(1) System analysis and Design

(2) Software requirement analysis

(3) System outline Design

(4) software detailed design

(5) Coding and unit test

(6) Software component test

(7) Software configuration test

(8) Software system test

(9) System acceptance

in each of these phases, appropriate review activities should be arranged, the PR organization is divided into technical review (Technical Review), the formal inspection (formal inspection), the daytime (walkthroughs), management review (Management review). There are strict and loose forms of organization. The top three peer reviews are key to technical experts and development peers. Managers should not participate in peer review or otherwise change the review process and distort the objectivity of the participants. Management review participants are managers who are designed to ensure the progress of the project and the rational allocation of resources.

Generally, the PR process is as shown

Next I will introduce each of the daytime, technical review and formal inspection. The purpose of the day (walkthrough) is to evaluate a product, usually a software code. Days have always been associated with code checking, in fact, the days can also be applied to other products (such as structural design, detailed design, test plans and other documents). The main goal of the daytime is to identify defects, omissions and inconsistencies, to improve the product and to consider the implementation of replacement. In addition, there are some other purposes, including the exchange of technology, the technical training of participants, the introduction of design ideas and so on. Second, Technical review (Technical Review), is a peer review technology. The main feature is that a group of reviewers carefully examines the software requirements, design, code, or other technical documentation in accordance with the normative steps to identify and eliminate defects. The technical review is also referred to as "review" (inspection). The main purpose of the technical review is to include the following points: (1) Discovering the error of the software in function, logic and realization;(2) Verify that the software complies with its requirements specification;(3) confirming that the software complies with predefined development specifications and standards;(4) Ensure that the software is developed in a unified mode;(5) Facilitate project management. 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)To support the main responsibilities of the staff in the pre-evaluation of 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 jury, to ensure the efficiency of the review meeting, after the review will be responsible for the classification of the problem and the revised review. reading Clerk (Reader)the mission of the reader 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. record Clerk (Recorder)The Recorder is responsible for documenting the software issues found at the review meeting in the technical review issue record form. 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. practice has proved that peer review, especially technical peer review is the most effective practice activities to confirm product quality, and timely delivery. Demonstrate its effectiveness in NASA and industry. Improve quality and reduce costs. End the mistake in its infancy. Prevent it from spreading to follow-up works and reduce the cost of total rework rework. An additional benefit is to improve team productivity. Improve the communication between team members, train new people quickly, and educate project team member's effective development practice. Third, the formal inspection (formal inspection) is in the software development process, the discovery, the elimination of software in the development cycle at all stages of the error, insufficient process, is a software static testing method, its life cycle for the software development cycle, (non-phased) software documentation and program code generated during the application and development process.

In each stage of software development, how to make the appropriate choice of the above three technologies has become a priority, can be simply used to indicate:

Of course, peer review is not perfect, there are some common problems, such as:

(1) No review plan

(2) Inappropriate choice of experts

(3) not fully prepared

(4) The review meeting deviates from the theme and focus

(5) No use of checklist as a guide

(6) Excessive controversy in the review meeting takes a lot of time

(7) Poor tracking after modification of the problem

 

On Peer Review (peer review)