Software Defect Life Cycle

In a Software Defect Life Cycle, software defects will undergo following states:

  1. New: This is the default state when Defect is created.
  2. Rejected: Defect has been evaluated and deemed not valid because of a triage session.
  3. Open: Defect has been reviewed and is waiting to be assigned
  4. Need More Info: The assignee (usually Development Lead or Developer), who has determined that more information is needed, returns the defect to the issuer.
  5. Assigned: Defect has been assigned to a team member for resolution by test lead.
  6. Analysis: Defect is being analyzed.
  7. Repair: Defect is being fixed.
  8. Fixed: Defect has been resolved by the assignee and is waiting to be included in a build for re-test.
  9. Deferred: Defect has been deemed not immediately required for production and will be reviewed for a future release of the project.
  10. Pending Management Decision: Defect has been analyzed and deemed to require decision from management before any action can be taken.  Response from management is required before moving forward with Defect.
  11. Ready for Re-Test: The configuration management team has received this fix in a build request and the Defect has been applied to the test environment and is ready to be re-tested.
  12. Monitor: Defect has been identified as possibly incidental in nature.  Defect issue will be monitored for a set period to determine if it occurs again for moving forward with any resolution.
  13. Re-Open: Defect did not pass a test case after being fixed.
  14. Closed: Defect has been resolved and validated; it is no longer a problem.