1 / 13

What is a Fault?

Standardized Fault Reporting in Electronic Commerce Software University of St. Thomas MBIF 705 – Foundations of Electronic Commerce Jeff D. Conrad December 3, 2003. What is a Fault?. Step 1. Step 2. Step 2. Step 3. Fault. Step 4. A fault tolerance system is resilient.

caesar
Download Presentation

What is a Fault?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standardized Fault Reporting in Electronic Commerce SoftwareUniversity of St. ThomasMBIF 705 – Foundations of Electronic CommerceJeff D. ConradDecember 3, 2003

  2. What is a Fault? Step 1 Step 2 Step 2 Step 3 Fault Step 4 A fault tolerance system is resilient

  3. Software Faults in EC Hardware Network connection Operating system Database Server application Security Process Validation Payment Image source: http://www.sticare.com/cable/internet.htm

  4. User Faults in EC ... Validation User interface Accessibility Data entry Image source: http://www.mormedia.com/default.asp?bhcd2=1070487151&bhcp=1

  5. EC Test Example

  6. EC Requires Information Payment Trust Legal Regulatory Image source: http://www.aucklandfinance.co.nz/images/pics/deal-handshake.jpg

  7. Affect on EC Labor Failure Performance Redundancy Delayed Profits Sales Forfeited Image source: http://www.rsi-ketchum.com/ketchum/images/inside-costs-image.jpg

  8. Software Reliability Image source: http://www.swen.uwaterloo.ca/~rekram/reports/software_reliability_growth_modeling_and_prediction.pdf

  9. Fault Tolerance Image source: http://www.hq.nasa.gov/office/codeq/doctree/fthb.pdf

  10. Failure Space Image source: http://www.hq.nasa.gov/office/codeq/doctree/fthb.pdf

  11. Severity

  12. Fault Standard <fault> <appCustomer/> /* the customer id of the application */ <appEnvironment/> /* environment that the application is running on */ <appMode/> /* what mode the fault was found in – testing, live or development */ <appServer/> /* environment that the application is running on */ <appUser/> /* the user id of the application */ <appVendor/> /* url of software vendor */ <appVersion/> /* the application version */ <faultCode/> /* fault code */ <faultDetails/> /* any extra details that should be saved */ <faultId/> /* unique id for this fault */ <faultMessage/> /* 0-256 character line simply describing the error */ <faultSeverity/> /* log-based severity 1-10 */ <faultType/> /* type of fault */ <occDate/> /* date the fault occurred */ <occTime/> /* time the fault occurred */ <srcFile/> /* if the error occurred external to the application source */ <srcFilePos/> /* file position in the external file */ <srcFileLine /> /* line number in the external file */ <srcFileLinePos /> /* position in the line in the external file */ <src/> /* path to the source code */ <srcFunction/> /* source code function or method name */ <srcLine/> /* line number in the source code */ <srcLinePos/> /* position in the line in the source code */ <stackReference/> /* reference indices, keys or ids that may help debug */ <stackTrace/> /* a stack trace of the functions called */ </fault>

  13. Conclusion Proactive Feedback Diagnostic Resiliency Paper and presentation available at: http://personal.stthomas.edu/jdconrad1/jdconrad1.htm

More Related