What is a Title Defect?

Defect Management / Software Defect Management (Defect Management) is the process of identifying, managing, and communicating any defects in the software life cycle (from the identification of defects to the closure of defect resolution) to ensure that defects are tracked and managed without loss. In general, tracking management tools are needed to help with defect full-process management.

Defect management

Defect Management /
Software defects are an important attribute in the software development process and it provides a lot of information. Software organizations of different maturity levels manage defects in different ways. Low maturity software organizations record defects and track defect correction processes. Highly mature software organizations will also make full use of the information provided by defects to build organizational process capabilities
Defects (Defects or Bugs) in software are "by-products" in the software development process. In general, defects cause software products to some extent fail to meet user needs.
Every software organization knows that defects in software must be handled properly. This is fundamental to the quality of the survival and development of software organizations. Unfortunately, not all software organizations know how to effectively manage defects in their software.
The description of the defect should include the following:
Defect ID
Unique defect ID, which can track defects
Defect state
Common defect states are: "New", "Pending", "Resolved", "Fixed"
Generally, the tester identifies the defect and its initial state is "new"; the project manager or technical leader analyzes the defect and assigns it to the appropriate developer to resolve, and the state flow is changed to "to be resolved"; the designated engineer resolves the defect and puts its state Tracked to "Resolved", the tester reviews the defect, if the review passes, closes the defect, the status is "Fixed", and if the review fails, returns to "Pending resolution".
Defect Title
Title describing the defect
Detailed description of the defect
A detailed description of the defect, how to reproduce the defect, and so on. The reason why this is listed separately is because the level of detail in the defect description directly affects the developer's modification of the defect. The description should be as detailed as possible.
The severity of the defect
Describe the severity of the defect, generally divided into four types: "fatal", "serious", "fair", and "subtle"
Urgency of the defect
Describe the urgency of the defect, from 1-4, 1 is the highest priority level, 4 is the lowest priority level
Although the urgency and severity of defects are not the same, they are closely related. The more severe they are, the more urgent they are. Therefore, some organizations only use "severity"
Defective author
Defect author name
Defect submission time
Defect submission time
Project / module to which the defect belongs
The project and module that the defect belongs to, it is better to locate the module more accurately
Defect designation
Defects can cause an unwanted or unacceptable external behavioral result when the software runs,
CMM Level 4 (or called Managed Level) software organizations will use the collected defect data to adopt
Compared with the fourth level of the CMM, the fifth level of the CMM (also known as the continuous optimization level) emphasizes continuous improvement of the organization's processes, so that the process capabilities are continuously improved.
In terms of defect management, software organizations should continuously improve the development process and defect discovery process at the organizational level based on a quantitative understanding of their process capabilities, introduce new methods and tools, and strengthen the exchange of experience to achieve defect prevention ).
The focus of defect prevention is on the common cause of defects. Defect prevention is achieved by finding, analyzing and dealing with common causes of defects.
When defect prevention is implemented, the process behavior diagram of defect density can be represented in the form below.
Defect management

IN OTHER LANGUAGES

Was this article helpful? Thanks for the feedback Thanks for the feedback

How can we help? How can we help?