ContentReporting Usability Defects : limitations of Open Source Defect Repositories and Suggestions for ImprovementAccessibility in Software Practice: A Practitioner’s PerspectiveImprovement of Open Source Software Usability: an Empirical Evaluation from Developers’ PerspectiveArticle previewSupportWhat are defect taxonomies?Appendix A. Root-Cause and Defect List
Thus, organizations can allocate more experience developers in more critical tasks. At the same time, we also used the card-sorting technique to group defects that could not be classified using UPT. We looked for commonalities and similarities to further group the defects within each category as well as across categories. Remedies applying to Tier 1 and 2 findings can include indemnification, mitigating documentation, refunds, and principal reduction .
A second categorisation identified potential causes of Impact, Environmental causes, Operational causes, Poor maintenance, Poor manufacturing and Fatigue. These two categorisations were integrated with an ontology. In principle, this work is expandable to other parts of gas turbine engines, such as annulus fillers, cases, discs, rotors, air seals, bearings, shafts, drums, liners, fuel nozzles and ducts. The work was developed for the aviation maintenance industry, in particular for the visual inspection of gas turbine engine blades, but it may be possible to apply more widely.

Binder also references specific defect taxonomies for C++, Java, and Smalltalk. The book Testing Computer Software contains a detailed taxonomy consisting of over 400 types of defects. Only a few excerpts from this taxonomy are listed here.
Reporting Usability Defects : limitations of Open Source Defect Repositories and Suggestions for Improvement
Another benefit of the ontology is that it provides means of knowledge storage in a computer readable way . No application of ontologies to blade defects is apparent in the literature. The specific ontology software used was ‘Protégé’ . The operation of modern [...]