This HTML5 document contains 38 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dbpedia-dehttp://de.dbpedia.org/resource/
dctermshttp://purl.org/dc/terms/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n13https://global.dbpedia.org/id/
yagohttp://dbpedia.org/class/yago/
rdfshttp://www.w3.org/2000/01/rdf-schema#
n17http://www.chillarege.com/
freebasehttp://rdf.freebase.com/ns/
n12http://researcher.watson.ibm.com/researcher/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n4http://chillarege.com/articles/
wikipedia-enhttp://en.wikipedia.org/wiki/
provhttp://www.w3.org/ns/prov#
dbchttp://dbpedia.org/resource/Category:
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Software_metric
dbo:wikiPageWikiLink
dbr:Orthogonal_Defect_Classification
Subject Item
dbr:ODC
dbo:wikiPageWikiLink
dbr:Orthogonal_Defect_Classification
dbo:wikiPageDisambiguates
dbr:Orthogonal_Defect_Classification
Subject Item
dbr:Orthogonal_Defect_Classification
rdf:type
yago:Arrangement105726596 yago:ClassificationSystem105727220 yago:WikicatClassificationSystems yago:Abstraction100002137 yago:Cognition100023271 yago:Structure105726345 yago:PsychologicalFeature100023100
rdfs:label
Orthogonal Defect Classification Orthogonal Defect Classification
rdfs:comment
Orthogonal Defect Classification (ODC) ist ein Modell zur Klassifikation von Fehlern in der Softwareentwicklung, das bei IBM entwickelt wurde. Durch die Klassifikation von Fehlern nach bestimmten Kategorien und Attributen lassen sich Zusammenhänge zwischen dem Entwicklungsprozess und der Ursache von Fehlern aufzeigen. Anhand der dabei gewonnenen Erkenntnisse lassen sich Maßnahmen zur Verbesserung des Entwicklungsprozess ableiten. Orthogonal Defect Classification (ODC) turns semantic information in the software defect stream into a measurement on the process. The ideas were developed in the late '80s and early '90s by Ram Chillarege at 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, spiral, gated, and agile development processes. One of the popular applications of ODC is software root cause analysis.
dcterms:subject
dbc:Software_quality
dbo:wikiPageID
2949170
dbo:wikiPageRevisionID
1107154120
dbo:wikiPageWikiLink
dbr:Root_cause_analysis dbr:Software_defect dbr:Software_development_process dbc:Software_quality dbr:Waterfall_model dbr:IBM_Research
dbo:wikiPageExternalLink
n4:odc-10x-root-cause-analysis n12:view_project.php%3Fid=480 n17:odc
owl:sameAs
dbpedia-de:Orthogonal_Defect_Classification freebase:m.08fks8 n13:hvTr wikidata:Q1751270
dbo:abstract
Orthogonal Defect Classification (ODC) ist ein Modell zur Klassifikation von Fehlern in der Softwareentwicklung, das bei IBM entwickelt wurde. Durch die Klassifikation von Fehlern nach bestimmten Kategorien und Attributen lassen sich Zusammenhänge zwischen dem Entwicklungsprozess und der Ursache von Fehlern aufzeigen. Anhand der dabei gewonnenen Erkenntnisse lassen sich Maßnahmen zur Verbesserung des Entwicklungsprozess ableiten. Orthogonal Defect Classification (ODC) turns semantic information in the software defect stream into a measurement on the process. The ideas were developed in the late '80s and early '90s by Ram Chillarege at 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, spiral, gated, and agile development processes. One of the popular applications of ODC is software root cause analysis. ODC is known to reduce the time taken to perform 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. 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. 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. 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. 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.
prov:wasDerivedFrom
wikipedia-en:Orthogonal_Defect_Classification?oldid=1107154120&ns=0
dbo:wikiPageLength
5544
foaf:isPrimaryTopicOf
wikipedia-en:Orthogonal_Defect_Classification
Subject Item
dbr:Bonnie_Ray
dbo:wikiPageWikiLink
dbr:Orthogonal_Defect_Classification
Subject Item
dbr:Software_bug
dbo:wikiPageWikiLink
dbr:Orthogonal_Defect_Classification
Subject Item
wikipedia-en:Orthogonal_Defect_Classification
foaf:primaryTopic
dbr:Orthogonal_Defect_Classification