SISUS Bugs: Reporting Problems

Send me an email at "Erik Barry Erhardt" <erik AT StatAcumen.com>, include suggested information below that you think will be helpful, and attach your data workbook. I will troubleshoot the problem as soon as I'm able.

Suggested Reporting Format

(Follows the best practices from apple, in most cases if you simply send me your SISUS input workbook with a short message, that will be all I need to fix the problem.)

  1. Bug Header Information
    1. Date/Time: When reported.
    2. Bug Classification: Setting the appropriate classification for the bug helps us properly classify the priority of the problem. Following are the Classification options and definitions:
      • Security: Potential security exposures.
      • Crash/Hang/Data Loss: Bugs which cause a machine to crash, resulting in an irrecoverable hang, or loss of data.
      • Performance: Issues that reduce the performance or responsiveness of an application.
      • UI/Usability: A cosmetic issue, or an issue with the usability of an application.
      • Serious bug: Functionality is greatly affected, and has no workaround.
      • Other bug: A bug that has a workaround.
      • Feature (new): Request for a new feature
      • Enhancement: Request for an enhancement to an existing feature.
    3. Reproducibility: Let us know how frequently you are able to reproduce this problem.
    4. Version/Build Number: Provide the following information, and more if relevant.
      • SISUS Workbook version: (eg. 0.01-07)
      • Operating System: (WinXP, MacOSX, etc.)
      • Internet Browser: (IE, Firefox, Safari, etc.)
      • Spreadsheet Editor: (MS Excel, Open Office, etc.)
  2. Bug Title & Description:
    1. Problem Report Title: The ideal problem title is clear, concise, succinct and informative. The ideal title includes the following:
      1. Version of the software on which the problem occurred
      2. Verb describing the action that occurred
      3. Explanation of the situation which was happening at the time that the problem occurred
    2. Description: Include a Summary, Steps to Reproduce, Expected Results, Actual Results, Workaround, and Regression/Isolation.
      1. Summary: Be explicit in providing a more descriptive summary information.
      2. Steps to Reproduce: Describe the step-by-step process to reproduce the bug. It is better to include too much information than not enough, as this minimizes the amount of back-and-forth communications.
      3. Expected Results: Describe what you expected to happen when executing the steps to reproduce.
      4. Actual Results: Explain what actually occurred.
      5. Workaround: If you have found a workaround for this problem, describe it.
      6. Regression/Isolation: Note any other configurations in which this issue was reproducible.
  3. Send your SISUS workbook and results:
    1. e-mail your SISUS workbook (that you submitted) to the author Erik.
    2. If your submission completed, e-mail your results, as well.
      • This is the *.zip file that comes from the "Results and Data" link at the bottom of the results page.