Defect:

A deviation from given requirements (non-conformance of requirements).

As we have Software Development Life Cycle (SDLC), A defect is also have its own life cycle starts from its identification to Closure. Below is the diagram which depicts its entire life cycle.

Defect Life Cycle Diagram:

Defect Life Cycle and Process:

1. New/Open: Testers will raise a defect with this status
2. Assigned: BA will analyze the defects raised by testers and assign them to respective developers
3. Deferred: Defect raised on this functionalities are deferred till further development and taken care later
4. Pending: Defect status can be pending when there is no clarity or need further discussion on that
5. Rejected: BA can reject the defect if it is invalid / Developers can reject if it is not a defect actually
6. Duplicate: BA can mark the defect if it is dupe of another defect / Developers can mark if it is a duplicate
7. Work as Designed: BA/Developers can mark it as WAD if it is working as per design or not reproducible
8. Returned to QA: If defect is not reproducible after Re-Open then developers can re-assign back to QA for re-verification.
9. Fixed: Once developer fix the defect will marked as fixed
10. Returned to Dev: Defect status can be pending
11. Closed: If the issue what is being addressed and fixed then tester will close it after verification.

 Severity and its Definition:

Severity: Severity describes/defines how seriously (impact) the defect/issue is affecting the system. In other words the seriousness (impact) of the defect/issue.

• Severity 1-Fatal: System crashes, system inoperable.
• Severity 2-Critical: Key function is inoperable, no workaround.
• Severity 3-Severe: Key function is inoperable, workaround available.
• Severity 4-Significant: Minor function is inoperable, no workaround available.
• Severity 5-Minor: Non-functional impact, cosmetic, workaround available.