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
A case study in root cause defect analysis
Proceedings of the 22nd international conference on Software engineering
The cost of errors in software development: evidence from industry
Journal of Systems and Software
Experimenting with Error Abstraction in Requirements Documents
METRICS '98 Proceedings of the 5th International Symposium on Software Metrics
The impact of background and experience on software inspections
The impact of background and experience on software inspections
Evaluation of capture-recapture models for estimating the abundance of naturally-occurring defects
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
A systematic literature review to identify and classify software requirement errors
Information and Software Technology
A checklist for integrating student empirical studies with research and teaching goals
Empirical Software Engineering
Hi-index | 0.00 |
Software quality and reliability is a primary concern for successful development organizations. Monitoring and controlling quality by helping developers detect as many faults as possible is a subjective and intricate approach. Due to the inherent difficulties and limitations, additional methods are required to obtain a more complete solution to the software quality problem. This paper analyzes the software quality problem from a different perspective involving a step back from faults to focus on the fundamental causes of faults. The first step in this direction is the application of the Error Abstraction Process (EAP) to the requirements phase of the software lifecycle to develop a Requirement Error Taxonomy (RET). This paper presents an empirical study on the application of the EAP and RET to requirement documents in a controlled classroom setting. The results show that the EAP significantly improves the productivity of subjects, that the RET is useful for improving software quality, that it provides useful insights into the requirements document, and that various context variables also impact the results. These results are promising and are important to motivate further investigation, to refine the RET, and to derive more formalized tools and methods for assisting developers. The result of this investigation will be a sound verification process for requirements phase.