What is Orthogonal Defect Classification (ODC)? by Vivek Vasudeva
- ODC is a systematic framework for Software Defect Classification developed by IBM in the early 1990’s.
- ODC is a concept that enables in-process feedback to developers by extracting signatures on the development process from defects.
- ODC uses of semantic information from defects to extract cause-effect relationships in the development process.
- ODC has built-in mechanisms for Phase Escape and Root Cause Analysis.
- ODC is referred to as an “MRI” on a Software Defect.
ODC (Orthogonal Defect Classification) Builds Cause – Effect Relationships
ODC (Orthogonal Defect Classification) Values
- Provide fast & effective feedback to developers.
- Captures information from defects that occurred through development phases & field usage.
- Allows understanding of defect trends over the lifecycle phases due to consistency of defect types.
- Through multi-dimensional measurement & analysis ODC assists developers to properly manage their development processes & product quality.
ODC (Orthogonal Defect Classification) Sections
A Defect passes through TWO sections with ODC
- Opener Section: When you find a defect, the following attributes can be classified:
- Activity: This is the actual activity performed at the time of defect discovery. For example, during function test phase, an engineer might decide to do a code inspection. The phase would be function test but the activity is code inspection.
- Trigger: The environment or condition that had to exist for the defect to surface. What is needed to reproduce the defect? During Review and Inspection activities, choose the selection which best describes what you were thinking about when you discovered the defect. For other defects, match the description with the environment or condition which was the catalyst for the failure.
- Impact: For in-process defects, select the impact which you judge the defect would have had upon the customer if it had escaped to the field. For field reported defects, select the impact the failure had on the customer.
- Closer Section: when you know how the defect was fixed, the following attributes can be classified:
- Target: Represents the high level identity of the entity that was fixed.
- Defect Type: Represents the nature of the actual correction that was made.
- Qualifier (applies to the Defect Type): Captures the element of either a nonexistent or wrong or irrelevant implementation.
- Source: Identifies the origin of the Target ( i.e. Design/Code, ID, etc.) which had the defect.
- Age: Identifies the history of the Target ( i.e. Design/Code, ID, etc.) which had the defect.
ODC (Orthogonal Defect Classification) Benefits – Software Testing
- All metrics and data in ODC can be viewed visually, please see chart below
Have you worked with ODC? Are you interested in trying? We can help and provide suggestions. Please ask us.
This post is authored by Vivek Vasudeva
ODC and Agile/SCRUM Coming Soon……