130 likes | 259 Vues
This document explores the complexities of fault reporting within electronic commerce (EC) software systems, providing essential insights into fault definitions, user and software faults, and the importance of fault tolerance. It outlines a systematic procedure for identifying faults, discusses the implications of hardware and software failures, and emphasizes the need for rigorous testing and validation. Furthermore, it highlights the significance of proactive feedback and diagnostics to enhance software reliability and resilience in EC environments.
E N D
Standardized Fault Reporting in Electronic Commerce SoftwareUniversity of St. ThomasMBIF 705 – Foundations of Electronic CommerceJeff D. ConradDecember 3, 2003
What is a Fault? Step 1 Step 2 Step 2 Step 3 Fault Step 4 A fault tolerance system is resilient
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
User Faults in EC ... Validation User interface Accessibility Data entry Image source: http://www.mormedia.com/default.asp?bhcd2=1070487151&bhcp=1
EC Requires Information Payment Trust Legal Regulatory Image source: http://www.aucklandfinance.co.nz/images/pics/deal-handshake.jpg
Affect on EC Labor Failure Performance Redundancy Delayed Profits Sales Forfeited Image source: http://www.rsi-ketchum.com/ketchum/images/inside-costs-image.jpg
Software Reliability Image source: http://www.swen.uwaterloo.ca/~rekram/reports/software_reliability_growth_modeling_and_prediction.pdf
Fault Tolerance Image source: http://www.hq.nasa.gov/office/codeq/doctree/fthb.pdf
Failure Space Image source: http://www.hq.nasa.gov/office/codeq/doctree/fthb.pdf
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>
Conclusion Proactive Feedback Diagnostic Resiliency Paper and presentation available at: http://personal.stthomas.edu/jdconrad1/jdconrad1.htm