当前位置：网站首页>Management of software defects

The generation of software defects is mainly determined by the characteristics of software products and the development process , For example, the demand is not clear 、 Requirements change frequently 、 The level of developers is limited . It comes down to , The main reasons for software are as follows .

1.1 Unclear needs

Software The demand is not clear Or developers Unclear understanding of requirements , It leads to the deviation of software design from the customer's requirements , cause Defects in software functions or features . Besides , Customer Frequent change requirements It will also affect the final quality of the software .

1.2 The software structure is complex

software system The structure is more complicated , It's hard to design a framework with a good hierarchy or component structure , This will cause the software to Development 、 expand 、 system maintenance Upper difficult , This leads to hidden software defects .

1.3 Coding problem

In software development , because The level of programmers is uneven , Coupled with the lack of effective in the development process Communication and supervision , Problems accumulate more and more , If this problem cannot be solved one by one , It will lead to a lot of defects in the final software .

1.4 Project duration is too short

project The deadline is too short , The development team should complete the development of software products in a limited time .

1.5 Use new technology

With the development of the times , Every technology is changing with each passing day , When developing with new technology , If The new technology itself has shortcomings perhaps Developers are not proficient in new technologies , It also affects the development process of software products , Cause software defects .

2. Classification of software defects

2.1 Divide defects from test categories

Interface class , Functional class , Performance class , Security , Compatibility class, etc .

2.2 Divide from defect severity

serious 、 commonly 、 secondary 、 Suggest

2.3 Prioritize defects

Solve it immediately 、 High priority 、 Line up correctly 、 Low priority

2.4 From the stage of defect occurrence

Demand stage defects 、 Architecture phase defects 、 Design phase defects 、 Coding phase defects 、 Test phase defects

3. Software defect handling process

The software processing flow of each company is different , But the basic process is the same , All of them have to go through these links ：

3.1 Submit

After the testers found the defect , Submit defects to test team leader

3.2 Distribute

After the test team leader receives the defect submitted by the tester , Hand it over to the developers

3.3 confirm

After the developer receives the transferred defect , We will discuss with the team and even the tester , Determine if the defect is ig defects

3.4 Refuse / delay

If after consultation , If the defect is not a real defect, it will be rejected , Close defects ;
If it is confirmed to be a defect , According to the severity or priority of the defect, self-interest treatment or delay treatment can be selected

3.5 Handle

Developers modify defects

3.6 Retest

After the developers fix the defect , The tester retested （ Retest ）, Check whether the defect has been modified , If it is not modified correctly , Then submit the defect again

3.7 close

After the testers retested , If the defect has been corrected correctly , Then the defect is closed , The whole defect treatment is completed .

4. Common software defect management tools

ZenTao

Zen is an excellent project management software made in China , Product management , project management , Quality management , Defect management , Document management , Organization management and affairs management in one .