User interface evaluation in the real world: a comparison of four techniques
CHI '91 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
What is gained and lost when using evaluation methods other than empirical testing
HCI'92 Proceedings of the conference on People and computers VII
A Model for Software Product Quality
IEEE Transactions on Software Engineering
IEEE Software
Software Quality—Prevention versus Cure?
Software Quality Control
Determinants of software quality: A survey of information systems project managers
Information and Software Technology
Predicting software defect density: a case study on automated static code analysis
XP'07 Proceedings of the 8th international conference on Agile processes in software engineering and extreme programming
Exploring quality attributes using architectural prototyping
QoSA'05 Proceedings of the First international conference on Quality of Software Architectures and Software Quality, and Proceedings of the Second International conference on Software Quality
| Hi-index | 0.00 |
Finding and fixing software code defects is crucial to product quality. It also, however, often proves difficult and time-consuming, especially late in the development cycle. While some believe that code analysis provides a simple way to detect quality defects, Lauesen and Younessi argue otherwise. To prove their point, they analyzed datafromerror reports, and their results show that code analysis detects only a small percentage of meaningful defects.