Defect Management Flowchart

Defect Management Flowchart

In QC , the management process of the defect:

Roles in the process:
1. Test personnel: The person who carries out the test, the initiator of the defect;
2, the developer : Carry out the development task of the personnel, complete the actual design and coding work;
3, the Evaluation Committee: The final confirmation of defects, when the project members of the defect reached a consensus, the exercise of the power of arbitration.

defect status
1,  new: Initial state of defect,
2,  open: Developers begin to modify defects,
3,  fixed: Developers modify the defect complete; Span lang= "en-us" >
4,  closed: Regression test passed, closed defect;
5,  reopen: Regression test failed;
6,   Postpone: deferred modification;
2, rejected: developer rejects defect;
3, Duplicate: Submitted defect duplicates;
4,  abandon: Abort

Bug severity level (Severity,bug level ): Refers to the extent to which the failure caused by a defect affects the SOFTWARE product, as specified by the tester.

A-crash	Cause system or application crashes, freezes, system hangs, or data loss
B-major	The main function of the system is lost, data cannot be saved, and a single function failure results in the failure of multiple related functions.
C-minor	Minor features are not fully implemented but do not affect the use of
D-trivial	Makes the operator inconvenient or troublesome, but it does not affect the operation and execution of the function
E-nice to (recommended)	Constructive comments or suggestions

Severity level definitions for bugs:

1) Frequency of Use

2) Degree of influence

3) Probability of occurrence

Priority definition of BUG:

1) impact on other modules

2) impact on your own modules

3) effect on the current function point

Defect Management Flowchart