GB/T 32421-2015Software engineering—Software reviews and audits (English PDF)

3.1 Anomaly

With the case according to the requirements specification, design documents, user documentation, such as the establishment of the desired standard deviation from, or with human perception or by

Deviations from the test phase.

Note. The exception may be in the following (but not limited to) during discovery. software products or applicable documentation review, testing, analysis, compilation, or use. Including the failure, lack of

Depression and so on.

3.2 Review

To project members, managers, users, customers, user representatives, auditors or other related parties elaborate software products, software products or collections

Conferencing software process or procedure for inspection, review, or approval.

3.3 Management Review

By the management department or the representative of a systemic management software product or process evaluation carried out in order to monitor progress, to determine the count

The status and progress of the plan, confirm system requirements and distribution needs, or evaluate the effectiveness of management in order to achieve the best purpose.

3.4 Technical Review

Made a systematic evaluation of a group of qualified personnel for software products in order to check the software product is suitable for its intended use

Sex, and identify specifications and standards differ. Technical Review may suggest alternative approaches recommended and examine various alternatives.

3.5 Review inspection

A visual inspection of software products, software to detect and identify abnormalities, including error, standard deviation and specifications.

Review was reviewed by trained technical training, fair organizers led by peer review.

Note. The results of the review may not include a solution, but wish to identify remedial measures or investigative measures abnormality.