IHSDM Problem Report/Change Request Form Instructions

Beta testers should use Problem Report/Change Request (PR/CR) forms to
document the results of their testing. Ideally, one form should be
completed for each problem encountered or change requested. The form
contains several sections, as follows:

***The top of the form*** is used to record information about the
tester, such as name, organization, title, telephone number, etc.

> ***Module/Function Tested:*** The IHSDM module/function being tested
> is identified (e.g., Policy Review Module, version 1.22). If a problem
> occurs while testing a specific roadway design, then the (roadway)
> data input file, IHSDM Project and IHSDM Analysis should be identified
> to help GDL staff and IHSDM software developers diagnose and resolve
> the problem.
>
> ***Type of Issue***: If a problem (i.e., a "bug") is detected, the
> tester should check the "Problem" box on the form. The Change Request
> or Enhancement boxes should be checked if the tester would like the
> software modified or enhanced in some way, rather than reporting a
> problem (bug).
>
> ***Category:*** The urgency of the problem is indicated by checking
> "Critical," "Severe," "Annoyance," or "Cosmetic." Critical problems
> are those that prevent the software from running as intended (e.g.,
> problems that result in a "fatal error"). Severe problems do not
> prevent the software from running, but are high priority items, such
> as erroneous results. Annoyances are problems that should be
> addressed, but are lower priority than severe or critical problems.
> For example, a bug that results in errors that do not otherwise effect
> the operations of the system might be termed an annoyance. Cosmetic
> problems are low priority, such as correcting misspelled words in the
> user interface.
>
> ***Description/Other Information:*** Testers should provide enough
> details to fully describe the problem or requested change. Additional
> information (e.g., roadway data files, output files, etc.) can be
> attached to the PR/CR to help the software developers diagnose the
> problem.
>
> ***The bottom of the form*** is for use by the IHSDM software
> developer (ITT Systems) to record and track the status of each PR/CR.
>
> These forms should be e-mailed by the beta test site coordinator to
> Mike Dimaiuta at <Michael.Dimaiuta@fhwa.dot.gov>. A completed PR/CR
> form is provided as an example.

**Sample of a Completed Form**

  ------------------ ------------------------ ----------- ----------------------------
  **IHSDM Problem                                         
  Report/Change                                           
  Request** **No.:**                                      
  P-B-GDL-193                                             

  **Tester**         John Q. Tester           **Title**   Transportation Engineer

  **Organization**   Geometric Design Lab     **Tel.**    202-555-1234

  **Date**           March 6, 2001 1:24 PM    **EMail**   John.tester@fhwa.dot.gov
  ------------------ ------------------------ ----------- ----------------------------

  ------------------- --------------------- -------------- -----------------------------------
  **Module/Function                         IHSDM(1.31)    
  Tested**                                  Policy Review  
                                            Module(1.22)   

  X                   **General**                          

                      **Design-Specific**   **Data Input   route_17.txt
                                            File**         

                                            Project        run2

                                            Analysis       test3
  ------------------- --------------------- -------------- -----------------------------------

  -------------- --- ---------- --- --------------- -- ------------- -- ----------
  **Type of      X   Problem        Change Request     Enhancement      
  Issue**                                                               

  **Category**       Critical   X   Severe             Annoyance        Cosmetic
  -------------- --- ---------- --- --------------- -- ------------- -- ----------

+-----------------------------------------------------------------------+
| **Description (or Steps to Problem):**                                |
|                                                                       |
| In the main IHSDM interface, I chose the "Policy Review Module" tab,  |
| then selected "Choose or Change Policy." From the "Choose Policy"     |
| dialog box, I highlighted the "AASHTO 1994" policy and clicked on the |
| "Select" button. At that point, I received a "Program Error: Illegal  |
| selection" message.                                                   |
|                                                                       |
| I exited IHSDM, restarted the program and tried again to select a     |
| policy. The same error message appeared once again.                   |
+-----------------------------------------------------------------------+
| **Other Information:**                                                |
+-----------------------------------------------------------------------+

  ------------------ ----------------- ---------------- -------------------
  **ITTS                                                
  Programmer**                                          

  **Receiving Date**                   **Closing Date** 

  **Final                                               
  Resolution:**                                         

  **Staff Hours**                                       
  ------------------ ----------------- ---------------- -------------------