Some Ideas about software review

 

Software Review

The software review is not reviewed after the software development is completed, but is reviewed at all stages of the software development. Because errors may occur at all stages of software development. If these errors are not found and corrected in time, they will be constantly expanded, which may lead to uncontrollable development results.

Software Review is a very important task and is currently the least important task for domestic development.

(1) review Objectives

. Identifies software functional, logic, or implementation errors in any form;
. Verify software requirements through review;
. Ensure that the software is represented according to pre-defined standards;
. The obtained software is developed in a unified manner;
. Make the project easier to manage.

(2) review process

A. Hold a review meeting: Generally, the Review Committee should be organized by the company to prepare each participant before the meeting.

B. There must be a result after the meeting: accept the product and do not need to be modified; reject the product due to serious errors; temporarily accept the product.

C. Review reports and records. All issues raised should be recorded. A review problem form should be generated before the review ends. In addition, the review brief report must be completed.

(3) review criteria

. Review the product, not the designer (no pressure on the designer );
. The venue should have a good atmosphere;
. Establish and maintain the agenda (the meeting cannot be separated from the topic );
. Restrict arguments and redisals (review will not aim to solve the problem, but to discover the problem;
. Specify the scope of the problem, rather than solving the problem mentioned;
. Display records (it is best to have a blackboard and write the questions on the blackboard at any time );
. Restrict the number of participants and insist on preparations before the meeting;
. Review the list of each product to be reviewed (to help reviewers think );
. Allocate resources and time schedules for each formal technical review;
. Conduct necessary training for all reviewers;
. Review your own review as soon as possible (review of the review criteria ).

 

Note: Based on my years of experience, if the meeting is not planned before the meeting, most of the meetings will last in the form, which makes no sense to us.