Software Defect Management

Table of contents

1. Causes of software defects

1.1 Unclear requirements

1.2 The software structure is complex

1.3 Encoding issues

1.4 Project duration is too short

1.5 Use of new technologies

2. Classification of software defects

2.1 Classify defects from test types

2.2 Classification from defect severity

2.3 From the prioritization of defects

2.4 Division from the stage of defect occurrence

3. Handling process of software defects

3.1 Submission

3.2 Allocation

3.3 Confirmation

3.4 Denial/Delay

3.5 Processing

3.6 Retest

3.7 close

4. Common Software Defect Management Tools


The work of software testing is to find the defects in the software, and the feedback to the developers refers to the modification, so as to ensure the quality of the software.

1. Causes of software defects

Software defects are often referred to as bugs , which refer to problems in software that affect the normal operation of the software.

The occurrence of software defects is mainly determined by the characteristics of software products and the development process, such as unclear requirements, frequent changes in requirements, and limited development personnel. To sum up, the main reasons for the software are as follows.

1.1 Unclear requirements

Software requirements are not clear or developers do not have a clear understanding of the requirements , resulting in software design deviated from the customer's requirements, resulting in defects in software functions or features . In addition, the frequent change requirements of customers will also affect the final quality of the software.

1.2 The software structure is complex

The software system structure is relatively complex , and it is difficult to design a framework with a good hierarchical structure or component structure, which will lead to difficulties in software development , expansion , and system maintenance , resulting in hidden software defects.

1.3 Encoding issues

In software development, due to the uneven level of programmers and the lack of effective communication and supervision during the development process , more and more problems have accumulated. If these problems cannot be solved one by one, many defects will exist in the final software.

1.4 Project duration is too short

The project period is too short , and the development team has to complete the development of the software product within a limited time.

1.5 Use of new technologies

With the development of the times, the development of each technology is changing with each passing day. When using new technology for development, if the new technology itself has shortcomings or developers do not master the new technology well , it will also affect the development process of software products, resulting in software defects.

2. Classification of software defects

2.1 Classify defects from test types

Interface class, function class, performance class, security class, compatibility class, etc.

2.2 Classification from defect severity

Serious, Fair, Minor, Recommended

2.3 From the prioritization of defects

Resolve Immediately, High Priority, Queued Correctly, Low Priority

2.4 Division from the stage of defect occurrence

Requirements Phase Defects, Architecture Phase Defects, Design Phase Defects, Coding Phase Defects, Testing Phase Defects

3. Handling process of software defects

Each company's software processing process is different, but the most basic process to follow is the same, and it must go through these links:

3.1 Submission

After the tester finds the defect, submit the defect to the test team leader

3.2 Allocation

After the test team leader receives the defects submitted by the testers, it will be handed over to the developers

3.3 Confirmation

After the developer receives the defect handed over, they will discuss with the team and even the testers to determine whether the defect is an ig defect

3.4 Denial/Delay

If after discussion, the defect is not a real defect, then refuse to deal with it and close the defect;

If it is confirmed that it is a defect, you can choose self-interest or postponement according to the severity or priority of the defect

3.5 Processing

Developers fix bugs

3.6 Retest

After the developer has modified the defect, the tester re-tests (retests) to check whether the defect has been modified, and if it has not been corrected, resubmit the defect

3.7 close

After the tester retests, if the defect has been corrected, the defect is closed and the entire defect processing is completed.

4. Common Software Defect Management Tools

Zen way

 Zen Road is an excellent domestic project management software, which can carry out product management, project management, quality management, defect management, document management, organization management and transaction management in one.

Guess you like

Origin blog.csdn.net/m0_48273471/article/details/125952534