Software Testing Technology (v)--software Review

A peer-reviewed walkthrough was conducted in this week's test class, and we had a very enthusiastic discussion, but I also found some less understood processes, such as how to plan activities, what is the purpose of the daytime, the technical review, the formal inspection, and when. I did a bit of detailed research.

First of all, Peer Review (peer review) as part of the software Review, along with the software Management reviews and software audit reviews, the general concept of the three are as follows:

• Software peer reviews, by the author and colleagues to evaluate the technical content and/or quality of work
• Software management reviews, the management representative evaluates the completion of the work and decides on downstream activities. Roles include decision maker, Review leader, Recorder, Management staff, Technical staff (required) Other team members, Customer Representative, USER representative (not required)
• Software audit reviews, by external personnel for specifications, standards, contract provisions, such as the consistency of verification. The roles of the audit include leader Auditor, Recorder, auditor, initiator, audited organization. Auditor is responsible for the objective examination of the product, should be away from the influence of their judgments, tendencies, or to identify their tendencies and continue with the permission of initiator

Peer review includes code review, collaborative coding (equivalent to the addition of review activities during encoding, two individuals as coders, one as observers, and from time to time to exchange roles), formal review, daytime, and technical review.

1. Technical review
Technical review is to provide proof to confirm the current progress when the project or part of the project is completed, and a group of people to investigate the specifications, standards, the use of the same purpose. Roles include decision maker, Review leader, Recorder, Technical Reviewer (must) Management staff, other team members, other Stakeholde Rs such as managers, technical staff, customers, and users (not required). Decision maker determines whether the product complies with the standards and arranges Review,review leader for guidance, and the role behavior is duplicated with decision maker. The rest can be literally understood.
2. Formal review
Formal scrutiny is formal and belongs to a static approach that needs to be followed by an established procedure. Roles include inspection leader, Reporter, Reader, Author, Inspector. It is important to note that all people are inpector,anthor and not as leader and reader.
3. Day
The daytime is more casual and can be used to train listeners, including walk-through leader, Recorder, Author, team member and a team that excludes managers.

Three methods of input, output and program are different, IEEE has a detailed standard can be consulted, reference IEEE standard for software reviews and audits

The value of reviews is that it can detect errors earlier and at less cost, and train the author to produce a document that is less flawed, as a troubleshooting method that should be done as early and often as possible, and that the downstream work can be carried out smoothly once the documentation of the outstanding defects is almost complete.

Software Testing Technology (v)--software Review