Defect management is widely used as an effective tool for recording and tracking project defects during software project development. In order to quickly, clearly and effectively grasp the problem points in the project, we will describe the defect development path through different States during use.
We usually use the following defect states: registration, issuance, investigation, countermeasure confirmation, correction, and result confirmation. From these six states, it is not difficult to see what we need to do in the process of discovering and solving a defect. The following describes the tasks that the responsible person must complete when the defects are in different States.
As the starting point of defect management, the importance of registration is self-evident. Therefore, we must record defects in a clear and detailed manner. First, we need to give a defect proposition, which should be concise and summarized; second, record the environment and conditions for the occurrence of the defect; third, record the occurrence of the defect; and fourth, add evidence.
The issue of defects should be done in two ways: one is to assess the importance and priority of defects, and the other is to clarify the responsibility of the defects investigation.
The investigator of the defect should record the cause of the problem in detail during the investigation, and propose corresponding countermeasures for the cause;
After the Fault Cause investigation is clear and the countermeasure is clear, we need to confirm the correctness, integrity, and scope of the countermeasure, and then submit it to the corresponding author.
For the defect correction, while correcting the defect strictly in accordance with the countermeasure, the record of the corrected object and the differential record before and after the correction should be made, so as to back up and restore the corrected object.
At the result validation stage, we need to design validation cases based on the rectification countermeasure to complete the correction validation, and reserve evidence for the validation results. If the results are incorrect, we need to re-revise the results, then confirm.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.