• Skip to primary navigation
  • Skip to content
  • Skip to footer

Software Quality Services

Software Consultancy & Training Experts focused on empowering Development & IT teams in designing, building and measuring,high quality reliable software

  • Who Are We?
    • Leadership
    • Mission & Values
  • Services
    • Consulting
    • Onsite Training
  • Blog
  • Contact
  • Hire Us
You are here: Home / Agile Development / What is ODC? Does it work with Agile?

February 25, 2016

What is ODC? Does it work with Agile?

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

 

Orthogonal Defect Classification, Cause and 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.

 

Orthogonal Defect Classification, Opener & Closer Sections

ODC (Orthogonal Defect Classification) Benefits – Software Testing

  • All metrics and data in ODC can be viewed visually, please see chart below

 

 

ODC, Customer usage analyzed via triggers

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……

Filed Under: Agile Development Tagged With: Agile, ODC, Orthogonal Defect Classification, Software Quality, Software Reliability

Vivek Vasudeva

Vivek Vasudeva

I have over 20 years of experience in Software Development, Quality Assurance and Release Engineering. Over the years I have focused on Highly available systems, and Software Reliability engineering. I am a Master Black Belt in Software DFSS (Design for Six Sigma). I have also developed and published Software development Agile/SCRUM methodologies.

Liked This Post? Read Another!

How can we improve Software productivity

How can we improve Software productivity

February 25, 2016 By Vivek Vasudeva Leave a Comment

We have a comprehensive approach to improving Software Productivity, based on the analysis of Software Defect Cost Model.

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Footer

Services

  • Software Consulting
  • Onsite Training

Featured Post

Zero Defect Initiative for Software

Zero Defect Initiative for Software Development What is a Zero Defect Initiative? The Goal for a Zero Defect Initiative is to target zero known high severity software defects, a maximum of 10 low severity defects, including 3rd Party Vendor defects at the following SDLC phases: Entry in to System Test Customer Field Trials (Beta Test) […]

Find Us On

LinkedIn
Facebook
Google +
Twitter

About Us

We at SW Quality are the foremost experts in Software Quality and Reliability. We have extensive experience in designing and building high reliability systems for IT, SaaS, Industrial Applications, Telecom, Insurance & many other industries. We pride ourselves on offering Left shift initiative where we help our customers identify defects at the earliest point in the software life cycle. Our methodology is based around a proactive quality culture, and we work hard to deliver significant value to each and every one of our clients. Headquartered in Wisconsin, our consultants travel all over the US & the World to empower some of the world's largest organizations to build better software.

Reviews

"Vivek Vasudeva is an expert in Software Development & Quality"

Vivek Vasudeva is a Six Sigma Master Black Belt who is not only is expert in Software Development and Quality - he is passionate about it. He explores new approaches, finds both proven and promising new methods that can minimize defects, model the rates of error generation and removal, and control the software processes to meet both development time and quality goals.

I've been amazed with his enthusiasm as I've seen him drive efforts to develop and use models to improve Software Availability, System Performance, and QoS (Quality of Service) in complex communication systems, and in emerging technologies. Vivek's enthusiasm, intuitive insights and exceptional intelligence, and the rate at which he learns new things, enable him to take on any challenge.


Written by: Eric Maass
Software Development & Quality
Date published: 06/02/2009
5 / 5 stars

© Copyright 2016 Software Six Sigma Experts LLC · All Rights Reserved

  • Terms of Use
  • Privacy Policy
  • Contact