View source for Orthogonal Defect Classification

'''Orthogonal Defect Classification''' ('''ODC''')<ref>Orthogonal Defect Classification-A Concept for In-Process Measurements, IEEE Transactions on Software Engineering, November 1992 (vol. 18 no. 11). http://www.chillarege.com/articles/odc-concept.html</ref> turns semantic information in the software defect stream into a measurement on the process.<ref>What is ODC? https://www.youtube.com/watch?v=mno4pQMqtBM</ref> The ideas were developed in the late '80s and early '90s by Ram Chillarege<ref>IEEE Computer Society, 2002 Technical Achievement Award https://www.computer.org/profiles/ram-chillarege</ref> at [[Organization:IBM Research|IBM Research]]. This has led to the development of new analytical methods used for software development and test process analysis. ODC is process model, language and domain independent. Applications of ODC have been reported by several corporations on a variety of platforms and development processes, ranging from [[Waterfall model|waterfall]], spiral, gated, and agile<ref>Orthogonal Defect Classification (ODC) in Agile Development.  
M. Jagia, S. Meena, IEEE ISSRE 2009 Supplemental Proceedings, Nov. 2009.</ref> 
<ref>Orthogonal Defect Classification: An Agile Test/QA Primer, Agile Development Conference, Nov. 2012 
</ref> [[Software development process|development processes]]. 
One of the popular applications of ODC is software [[Root cause analysis|root cause analysis]]. 

ODC is known to reduce the time taken to perform [http://chillarege.com/articles/odc-10x-root-cause-analysis root cause analysis by over a factor of 10]. The gains come primarily from a different approach to root cause analysis, where the ODC data is generated rapidly (in minutes, as opposed to hours per defect) and analytics used for the cause and effect analysis. This shifts the burden of analysis from a purely human method to one that is more data intensive.<ref>"ODC - a 10x for Root Cause Analysis", R. Chillarege 2006</ref>

ODC as proposed in its original papers have specific attribute-value sets that create measurements on the development process. Two of the five more well known categories are the Defect Type and Defect Trigger.  The Defect Type captures the changes made in the code as a result of the defect. There are seven values for Defect Type and they have been empirically established to provide a measurement of the product through the process through their distribution. The concept is that changes in the Defect Type Distribution is a function of the development process model, and thus provides an intrinsic measurement of progress of the product through the process.

The Defect Trigger, similarly provides a measurement of the Testing process. The concept of the Trigger is a key contribution that came through ODC and is now fairly widely used in technical and research publications.<ref>Software Defects and their Impact on System Availability - A Study of Field Failures in Operating Systems. M.Sullivan and R. Chillarege, IEEE 21st Fault-Tolerant Computing Systems, 1991.</ref>  The software Trigger is defined as the force that surfaced the Fault to create the Failure. The full set of Triggers is available in ODC Documentation.

The Defect Type and Trigger collectively provide a large amount of causal information on Defects. Additional information from the defect that is captured in standard ODC implementations includes "Impact", "Source" and "Age". ODC Training courses report that, once trained, an individual can categorize a defect via ODC in less than 3 minutes when performing the task retrospectively.<ref>Diamonds from Defects, LADC Keynote, http://www.unicauca.edu.co/ladc2016/?q=node/22</ref>  The time taken is far lower when done in-flight, or in-process. The categorization cannot be directly compared to root-cause-analysis, since ODC data is about "what-is", not "why". However, root cause analysis is very commonly performed using ODC. The analysis that studies ODC data is performing the first pass of root cause analysis, which is confirmed by discussing the results with the development team. This approach has five primary differences between the classical method and the ODC method.<ref>"5 Differences between classical root cause analysis and ODC root cause analysis. https://www.youtube.com/watch?v=fTJr2Pgnxco</ref>

Root Cause Analysis is just one of the applications of ODC. The original design of ODC was to create a measurement system for software engineering using the defect stream as a source of intrinsic measurements. Thus, the attributes, either singularly, or in conjunction with one of the others provides specific measurements on certain aspects of the engineering process. These measurements can be used for one or more analytical methods, since they were designed with general measurement principles in mind. Todate, several research papers have applied these for a variety of purposes. More recently, there have been research articles that use ODC to assess the methods used for security evaluation, and expanded the scope of ODC.<ref>P. J. Morrison, R. Pandita, X. Xiao, R. Chillarege, and L. Williams, “Are vulnerabilities discovered and resolved like other defects?,” Empir Software Eng, vol. 23, no. 3, pp. 1383–1421, Jun. 2018, doi: 10.1007/s10664-017-9541-1.</ref>

==References==
<references />

==External links==
* [http://researcher.watson.ibm.com/researcher/view_project.php?id=480 IBM Research: Orthogonal Defect Classification]
* [http://www.chillarege.com/odc Chillarege Inc.: Orthogonal Defect Classification]

<!-- Categorization -->

[[Category:Software quality]]

{{Sourceattribution|Orthogonal Defect Classification}}