Defect management can be defined as a process of detecting bugs and fixing them. It is necessary to say that bugs occur constantly in the process of software development. They are a part of the software industry. That is because of the fact that software development is quite a complex process.
Defect management process
- Identification: This will be the first step to identify the defect in the process this can be done by the testing team and sometimes the customer can also tell you about the defect.
- Categorization: After the defect is registered, then it passes to the desired person then checks it and categorize it that what type of defect it is and then move to the next step.
- Prioritization: According to the type of defect or severity of the defect. These defects are set of priorities for fixing it accordingly. It can handle through a formal channel or an individual team member who is working on defect can set its own priorities for fixing defects.
- Assignment: As soon as the priorities are decided by formal channel defect is assigned to a developer to fix it.
- Resolution: Developer fixes the defect and places it in the same place from where it was identified.
- Verification: As soon as the defect is fixed, the developing team verifies that defect is actually fixing and working in the smoothest way or not.
- Closure: once it is fixed and resolved it is marked as closed case.
- Management Reporting: This provided at regular intervals which helps management to know which work is done and which work is going on and when it will be done.
