Software Testing • Peer review

In software testing, peer review is used to test software development, software evaluation of the various stages of the work is complete, specifications, whether the product reached the specified technical requirements and quality requirements, in order to determine whether it can be transferred to the next stage of work. Software review is to ensure that the successful development of software projects must be carried out, often peer review by more than 5 groups to complete, in a certain period of time, found as many errors, is to judge whether a peer review to meet the requirements of the evaluation indicators.

In peer review, the departmental review phase is generally divided into nine phases:

1. System Analysis and Design

2. Software Requirements Analysis

3. System Overview Design

4. Detailed Software Design

5. Code and Unit tests

6. Software Component Testing

7. Software Configuration test

8. Software system Testing

9. System receive

Each phase is constantly improving the software development process, providing strong support for the entire development phase.

The above-mentioned peer review stage is divided into nine different stages, each of which has its own role, the nine-phase combination of software development testing to become rational and orderly, then in the process of review, peer review of the general process is how to do? The following diagram illustrates the phase of the process in which it operates:

The above picture shows that in the implementation of peer review, divided into four stages, respectively, the planning phase, implementation phase, measurement phase, review/audit phase. Each stage has specific implementation steps, including in the implementation phase of the daytime, technical review, formal inspection, is to support the entire process of the review phase.

It said that at least 5 people in the review, then the five people are how to assign roles, five characters are moderator, inspectors, Author, Reader, Recorder five characters, of which inspectors can be played by many people.

The above figure is in the entire PR process, five roles have the function and time, below the next five role of the detailed role of what:

1.Moderator in the PR process as the role of the Moderator, responsible for ensuring the smooth implementation of the PR, and ensure that it is efficient;

2.Inspectors in the PR process as the role of the reviewer, mainly found in the software design of some defects and loopholes and other bugs;

3.Author is the designer of the review software;

4.Reader in the PR for everyone to interpret the role of the software design;

5.Recorder in PR as record, evaluation of the efficiency of the PR work;

When Recorder records and evaluates the efficiency of the PR work, it calculates the specific efficiency according to some indicators, and often has the following indicators:

1. Defect density = Defects/review scale

2, Review speed = Review Scale/review hours

3, Review efficiency = Defects/man-hour

These three indicators of the high and low can be almost a description of the PR efficiency how.

Software Testing • Peer review