Eight, software defects Detailed

 

table of Contents

1. The definition of software defect

2. The principle of software defect report

3. Basic information software defects

4. Software defect severity and priority

5. Software Defect Management Overview

6. Software defect management role

7. The life cycle of software defects

8. The process flow software defects

9. face questions

---

1. The definition of software defect

1. Unrealized software product specification requirements of function
2. An error has occurred Software product name should not appear in the manual
3. Software functionality is not mentioned in the product description
4. Unrealized software product specifications, although not explicitly mentioned but the realization of the objectives
5. Software difficult to understand, not to use, run slowly or software testers point of view - the end user will think bad

2. The principle of software defect report

As soon as the report software defects;

The earlier software defects found, the more left in the progress of the repair time, the higher the possibility of the bug fixes;

Effectively describe software defects;

Explain and demonstrate the facts straight, must describe the details of software defects; gives a clear set of steps illustrate the problem.

3. Basic information software defects

4. Software defect severity and priority

5. Software Defect Management Overview

Recognition in the software life cycle management, communication of any defect process (to identify defects to solve the defect closed), defect management is to ensure tracking management without losing.

General need to track defect management tools to help manage the whole process.

6. Software defect management role

1. Make sure that each defect found can be resolved;
2. And defect data collected during the test phase of the curve according to identify defect trends
3. Defect data collecting and analyzing data, data associated with the software can be obtained from the quality defect data.

7. The life cycle of software defects

1. Identify defects
2. Submitting
3. Analysis and positioning defects
4. Modify the program
5. Verify modification
6. Close defects
7. By analyzing the common defects, prevent defects from happening again.

8. The process flow software defects

1. First project created and initialized;
2. Testers find errors, submit bug reports, when defective state New;
3. Project Manager subject to error reports submitted by the tester, confirm it, and assigned to the developers, this time the defect state Open;
4. Developers receive the error distribution, modify, and defect status to Fixed, defect again sent for confirmation to the testers;
5. Testers verify bug fixes, error elimination, defect status to Closed, otherwise an error status will restart;
6. If the error can not be modified or temporarily developers consider it necessary to amend the error will be submitted to the review committee to check whether it is necessary to modify it, if there is no need to modify, then close the project defects;
7. If it is necessary to modify the return (4);
8. 

9. face questions

1. The more defects found, indicating that the more software defects?
2. All software defects can be repaired? All software defects must be repaired?
3. When developers say that is not BUG, ​​how do you respond?
4. How to grade software defects divided?
5. Take what management measures for the defect?
6. 
7. Impressive BUG?