1. Standardized Fault Reporting in Electronic Commerce Software University of St. Thomas MBIF 705 – Foundations of Electronic Commerce Jeff D. Conrad December 3, 2003

2. What is a Fault? Step 1Step 2 Step 3FaultStep 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 /* the customer id of the application */ /* environment that the application is running on */ /* what mode the fault was found in – testing, live or development */ /* environment that the application is running on */ /* the user id of the application */ /* url of software vendor */ /* the application version */ /* fault code */ /* any extra details that should be saved */ /* unique id for this fault */ /* 0-256 character line simply describing the error */ /* log-based severity 1-10 */ /* type of fault */ /* date the fault occurred */ /* time the fault occurred */ /* if the error occurred external to the application source */ /* file position in the external file */ /* line number in the external file */ /* position in the line in the external file */ /* path to the source code */ /* source code function or method name */ /* line number in the source code */ /* position in the line in the source code */ /* reference indices, keys or ids that may help debug */ /* a stack trace of the functions called */

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