Software reliability: measurement, prediction, application
Software reliability: measurement, prediction, application
Reliability Analysis of Large Software Systems: Defect Data Modeling
IEEE Transactions on Software Engineering
Application of software reliability modelling to product quality and test process
ICSE '90 Proceedings of the 12th international conference on Software engineering
IEEE Transactions on Software Engineering
The cleanroom approach to quality software development
The cleanroom approach to quality software development
Managing computer projects: avoiding the pitfalls
Managing computer projects: avoiding the pitfalls
A Practical View of Software Measurement and Implementation Experiences Within Motorola
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
Software Reliability Analysis of Three Successive Generations of a Switching System
EDCC-1 Proceedings of the First European Dependable Computing Conference on Dependable Computing
The Confounding Effect of Class Size on the Validity of Object-Oriented Metrics
IEEE Transactions on Software Engineering
Object-oriented metrics: A review of theory and practice
Advances in software engineering
A Measurement-Based Framework for Software Reliability Improvement
Annals of Software Engineering
Quantitative Analysis of Faults and Failures in a Complex Software System
IEEE Transactions on Software Engineering
A Replicated Quantitative Analysis of Fault Distributions in Complex Software Systems
IEEE Transactions on Software Engineering
A quantitative analysis into the economics of correcting software bugs
CISIS'11 Proceedings of the 4th international conference on Computational intelligence in security for information systems
Hi-index | 0.00 |
Analyzes data collected on a commercial telecommunications system and summarizes some of the lessons learned from this study. The data correspond to failure and fault information recorded during system validation and operation: 3,063 trouble reports, corresponding to a five-year period during which five versions of the system have been developed and more than 100 systems have been introduced in the field. The failure information includes software failures as well as hardware failures due to design faults.