ACM Home Page
Please provide us with feedback. Feedback
Digital Library logoTake a look at the new version of this page: [ beta version ]. Tell us what you think.
Automating Software Failure Reporting
Full text HtmlHtml (26 KB),  PdfPdf (418 KB)
Source
Queue archive
Volume 2 ,  Issue 8  (November 2004) table of contents
System Failures
FEATURE: Q focus: Error Recovery table of contents
Pages: 42 - 48  
Year of Publication: 2004
ISSN:1542-7730
Author
Brendan Murphy  Microsoft Research
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 195,   Downloads (12 Months): 951,   Citation Count: 3
Additional Information:

abstract   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1036474.1036498
What is a DOI?

ABSTRACT

There are many ways to measure quality before and after software is released. For commercial and internal-use-only products, the most important measurement is the user's perception of product quality. Unfortunately, perception is difficult to measure, so companies attempt to quantify it through customer satisfaction surveys and failure/behavioral data collected from its customer base. This article focuses on the problems of capturing failure data from customer sites. To explore the pertinent issues I rely on experience gained from collecting failure data from Windows XP systems, but the problems you are likely to face when developing internal (noncommercial) software should not be dissimilar.




REVIEW

"Timothy R. Hopkins : Reviewer"

A major problem facing today's software developers is how to capture the data necessary to pinpoint the causes of failures in their systems, once these have been released to end users. This paper looks at the problems associated with collecting su  more...