Detecting defects in object-oriented designs: using reading techniques to increase software quality
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
Using Experiments to Build a Body of Knowledge
PSI '99 Proceedings of the Third International Andrei Ershov Memorial Conference on Perspectives of System Informatics
Proceedings of the 28th international conference on Software engineering
Requirement error abstraction and classification: an empirical study
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
A systematic literature review to identify and classify software requirement errors
Information and Software Technology
Verification of Use Case with Petri Nets in Requirement Analysis
ICCSA '09 Proceedings of the International Conference on Computational Science and Its Applications: Part II
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Fault links: exploring the relationship between module and fault types
EDCC'05 Proceedings of the 5th European conference on Dependable Computing
FASE'06 Proceedings of the 9th international conference on Fundamental Approaches to Software Engineering
| Hi-index | 0.00 |
In previous experiments we showed that the Perspective-Based Reading (PBR) family of defect detection techniques was effective at detecting faults in requirements documents in some contexts. Experiences from these studies indicate that requirements faults are very difficult to define, classify and quantify. In order to address these difficulties, we present an empirical study whose main purpose is to investigate whether defect detection in requirements documents can be improved by focusing on the errors (i.e., underlying human misconceptions) in a document rather than the individual faults that they cause. In the context of a controlled experiment, we assess both benefits and costs of the process of abstracting errors from faults in requirements documents.