Orthogonal Defect Classification-A Concept for In-Process Measurements
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
In-Process Evaluation for Software Inspection and Test
IEEE Transactions on Software Engineering - Special issue on software reliability
Software test automation: effective use of test execution tools
Software test automation: effective use of test execution tools
Evaluating Software Development Objectively
IEEE Software
ISSRE '97 Proceedings of the Eighth International Symposium on Software Reliability Engineering
Evaluating the Software Test Strategy for the 2000 Sydney Olympics
ISSRE '01 Proceedings of the 12th International Symposium on Software Reliability Engineering
ECSQ '02 Proceedings of the 7th International Conference on Software Quality
Reflections on Industry Trends and Experimental Research in Dependability
IEEE Transactions on Dependable and Secure Computing
A model for software rework reduction through a combination of anomaly metrics
Journal of Systems and Software
Towards adopting ODC in automation application development projects
Proceedings of the 5th India Software Engineering Conference
Towards a measurement tool for verification and validation of simulation models
Proceedings of the Winter Simulation Conference
OSDC: adapting ODC for developing more secure software
Proceedings of the 28th Annual ACM Symposium on Applied Computing
Journal of Systems and Software
| Hi-index | 0.00 |
Orthogonal Defect Classification (ODC) is a methodology used to classify software defects. When combined with a set of data analysis techniques designed to suit the software development process, ODC provides a powerful way to evaluate the development process and software product. In this paper, three case studies demonstrate the use of ODC to improve software testing. The first case study illustrates how a team developing a high-quality, mature product arrived at specific testing strategies aimed at reducing field defects. The second is a middleware project that identified the areas of system test that needed to be strengthened. The third describes how a very small team with an inadequate testing strategy recognized its risk in trying to meet the scheduled release and made the product more stable by postponing the release date and adding badly needed testing scenarios. All three case studies highlight how technical teams can use ODC data for objective feedback on their development processes and the evolution of their products. This feedback facilitates the identification of actions to increase the efficiency and effectiveness of development and test, resulting in improved resource management and enhanced software quality.