Definition of defect
Software does not meet the function of product manual
Software has inconsistent performance in the product manual
Software features exceed the scope of the product manual
The software does not meet the target of users (although there is no requirement in the product manual)
Tester or users think the ease of use of software
Not all defects will be modified
The pressure of the market makes the product ultimately issued time limit
Tester error to understand or incorrectly operate the defects (FAQ)
The wrong modification affects more modules, and the risk is large (legacy)
Modifying price is too low (FAQ, legacy)
The problem proposed in the defect report is difficult to reproduce
Points for defect analysis:
Analyze the functional domain distribution of software issues to find out the weak links of the system
To collect the bug data of each functional module or system component in detail, and classified by function, error type, severity.
Compare whether the software bug is in combination with expected problems distribution
Two-eight rationter: 80% of software issues always occur in approximately 20% of functional modules (system components).
Analysis on the distribution of the injection phase of the bug and compared with historical data. BUG data should be collected in detail according to different development stages
The defect density required to the development phase of the software is less than the average of the past.
Moreover, the sum of the defect exclusion rates of demand analysis, design, and code review phases is greater than or equal to the predetermined value (for example, 75%). (Peer review)
The type of software defect should be analyzed in order to fix a serious defect.
