The Effects of Fault Counting Methods on Fault Model Quality
COMPSAC '04 Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01
Incorporating a fault categorization and analysis process in the software build cycle
Journal of Computing Sciences in Colleges
An approach to the measurement of software evolution: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice - 2003 International Conference on Software Maintenance: The Architectural Evolution of Systems
Categorizing faults in the software build cycle decreases the total number of faults
Journal of Computing Sciences in Colleges
Software faults: a quantifiable definition
Advances in Engineering Software
Fourth international workshop on Software quality assurance: in conjunction with the 6th ESEC/FSE joint meeting
Analysis of fault models for student use
ACM SIGCSE Bulletin
Software faults: A quantifiable definition
Advances in Engineering Software
Hi-index | 0.00 |
An important aspect of developing models relatingthe number and type of faults in a software system to a setof structural measurement is defining what constitutes afault. By definition, a fault is a structural imperfection ina software system that may lead to the system's eventuallyfailing. A measurable and precise definition of whatfaults are makes it possible to accurately identify andcount them, which in turn allows the formulation of mod-elsrelating fault counts and types to other measurableattributes of a software system. Unfortunately, the mostwidely-used definitions are not measurable - there is noguarantee that two different individuals looking at thesame set of failure reports and the same set of fault definitionswill count the same number of underlying faults.The incomplete and ambiguous nature of current faultdefinitions adds a noise component to the inputs used in