Fundamentals of Software Quality via Orthogonal Defect Classification
The Fundamentals of Software Quality is formed at the defect classification level, where we want to be able to the following:
- Know how the defect was “Triggered”
- What is the “Impact” of the defect, how severe will it be
- What “Type” of Software Defect it is, we need to standardize “defect types”
- “Where” in the source code the defect is?
- Is this new code, legacy code or rewritten code?
- Is the defect due to something missing or incorrect ?
- Where in the process was this defect discovered, i.e., Requirements, Design, Coding, or Testing?
ODC (Orthogonal Defect Classification) provides us with the capability to visually observe all of the above and look at trends through our software architecture. We then know where potential risks are in our software.
ODC is a standardized approach to Software Quality, developed by IBM. ODC methodology is now open source.
ODC forms the fundamentals of Software Reliability because it allows software developers, testers, as well as customer facing teams collaborate on a standardized approach.
ODC is “VISUAL”, i.e., all trends are viewed, rather than numbers or analysis. The defect classification fields are Orthogonal, and can be plotted against each other. As we plot “Activity vs. Trigger” or “Impact vs. Trigger”, we get a unique insight in our software.
ODC is used for IT , Enterprise & Business Software, Telecommunication , Real time applications, Aerospace, Health care applications, and the list is growing.
ODC can be easily implemented in JIRA. A defect can be classified in less than 4 minutes using ODC.
ODC data can be visually interpreted, and corrective actions are taken in the current phase. ODC provides for live feedback.
We at SWReliability.com have the expertise in training, developing an ODC culture and implementing ODC. We have implemented ODC in various tools including JIRA.
Please provide us your feedback on your approach to Software Reliability? If you have use ODC, please share your stories with us.
This post is authored by Vivek Vasudeva