Bug Management Specification

Reasonable bug process management can help to improve the efficiency and quality of the whole project, first of all, I first knot the concept of bug related.

first, the classification of the bug

Bug refers to a variety of defects in the system, you can classify the bug from many angles.

1. In terms of functional aspects, the cause of the bug can be summed up in the following four types:

A. Repetitive functions; B. Redundant functions;

C. function does not meet the requirements of the design; D. Functional implementation does not match the design requirements.

2, from the point of ease of use, can be attributed to three points:

A. The interface is not beautiful, the control arrangement, the format is not unified, the focus control is unreasonable or not comprehensive;

B. Lack of help information, or help incomplete;

C. Complex function operation, the information is unreasonable, easy to produce ambiguity.

3, from the point of security, the bug can be divided into the following categories:

A. Data validity detection is unreasonable; B. Important data is not encrypted in the transmission;

C. Lack of authentication mechanisms or certification is unreasonable; D. Lack of randomness in data generation;

E. Network security: Open port, service, F. System log, Audit.

4, from the reliability point, the bug can be divided into the following categories:

A. Reliability of data storage; B. Reliability of business processes;

C Hardware reliability: such as printer; D. Emergency response measures;

E. Data backup, recovery.

5, from the performance considerations, the bug can be divided into three kinds:

A. concurrency; B. throughput; C. Response time.

6, from the compatibility considerations, there are two types of bugs:

A. hardware compatibility; B. Software compatibility.

7, from the maintainability considerations, can be divided into two kinds of reasons:

A. Scalability; B. Easy to upgrade.

Second, Bug level

The bug level is divided according to the severity of the bug appearing in the system, and is defined as the following 5 levels:

Level 1-slight (low): Do not affect the normal use, minor, small problems, the function has little impact, products and properties can still be used, such as a typo. The modification priority is low, which is recommended for programmers to modify.

Level 2-General (Medium): The system can be used normally, but there is a potential risk, and the system business is affected slightly. If the message is incomplete. This level requires programmer modification.

Level 3-Higher (high): The system secondary function is not realized, the main function part fails, the system business is affected, and the user's interests are lost. This level requires the programmer to modify.

Level 4-Serious (Very high): The main function of the system can not be realized, the system business is seriously affected, causing the user's interests to be lost. This level requires programmer modification.

Level 5-Deadly (Fatal): The system important function is unable to use normally, the system crashes, the system design has the big hidden danger, causes the user benefit to suffer the significant loss. This level requires programmer modification.

Third, Bug Status

Bug status Flag The current state of the bug, is used to deal with the main parameters of the bug process, our QC Defect management platform has the following status:

NEW: Newly discovered system bug by testers;

On (Open): The tester notifies the developer of the bug that needs to be modified;

Modified (Modify): Bug that the developer is modifying;

Fixed: The developer notifies the tester that a bug has been fixed;

Trace: It is difficult for testers to determine whether a bug has been fixed in a short time;

Closed (Close): The tester determines the fixed bug after regression test;

Deprecated (rejected): Bug that was rejected by the developer;

Reopen (Reopen): Bug not fixed, re-appear in the new beta version;

Deferred modification (wait): A bug that waits for a delay to fix for various reasons.

Four, Bug Priority Level

Level 1-Suggested: Proposed modification, corresponding to the bug level 1 slight;

Level 2-General: Need to modify, corresponding to the bug Level 2 general and 3 higher;

Level 3-Higher: Focus on the change, the corresponding bug level of 4 serious;

Level 4-Emergency: immediately modified, corresponding to the bug Level 5 fatal. Five, the bug processing process

1. Testers add bugs to the QC platform, the initial state is new, the tester will put the status of "open" status, notify the developer to modify;

2. Developers double-click their own responsibility of the bug, the status is set to ' modify ', modify the correct bug in the comment box after the description, fill in the repair date, the defect status of "fixed" state;

If the developer feels that there is no need to change, put the status as ' deprecated ';

3. The tester sees the fixed state of the bug will carry on the acceptance test, after passing the status to "closed" state, if the acceptance does not pass the status is set to "reopen".

4. For a bug that has been placed as ' deprecated ', the tester agrees to close after negotiation with the developer, then "closed", and if the tester does not agree to the closure, it will be submitted to the project owner to decide whether to modify it or not;

To modify, set the bug status to ' reopen ', and the developer will continue to modify it, or ' closed ' if no further modifications are made, and if deferred processing is set to ' deferred modification '.

5. To be able to modify the bug, the developer is then reset to ' modify ' and fix it.