Laserfiche WebLink
<br />In order to test and document the software revisions, R Ti will <br />. Based on the Exhibit I, verify the Low Level DMI Routines that require <br />modification, Exhibit 2 contains a preliminary list by table, Note that some routines <br />are repeated for different tables, <br />. Schedule modifications, if possible, such that incremental upgrades in the utilities can <br />be made and tested, In other words, if several routines hit a modified table and can be <br />updated without totally disrupting all the utilities, do so, <br />. Verify that the output of each revised utility is the same as the original version created <br />using the CRDSS database in a memorandum, <br /> <br />Low-level DMI Coding Changes, Exhibit 2 lists the low-level DMI routines that are <br />expected to need revision because of a difference or enhancement between the HB - <br />CRDSS and CRDSS designs, Anticipated changes include, at a minimum, revising table <br />names and table attribute names in the embedded SQL select statements, Other changes <br />which may result if a table structure and/or table relationships are changed include: <br />. the embedded SQL, <br />. the data structures used to pass information between DMI's and user utilities, <br />. the DMI Utilities themselves, <br />. new code development <br /> <br />Because the overall functionality of the HB - CRDSS database is similar to the existing <br />CRDSS database, relatively little new code development is expected, <br /> <br />DMI Utilitv Code Changes, DMI Utilities that RTi will recompile, test and perhaps <br />modify in this Task include demandts, netresev, watright, makenet, and crdssdb, the <br />World Wide Web database interface program, It is anticipated that crdssdb will require <br />the most testing, <br /> <br />Testing Software changes to both Low level DMI's and DMI Utilities will be conducted <br />as follows: <br />. Software which access both the CRDSS and HB - CRDSS databases will be <br />compared for all command line options using a defined data set (one water district, <br />basin, or division), The data set will be selected randomly in concert with the State, <br />. Differences will be identified and resolved, <br />. A memo will be prepared documenting the testing procedures and results, <br /> <br />The above procedure is estimated to be adequate to assure but not guarantee that the <br />revised software produces the same results as the existing CRDSS software, RTi will <br />resolve any differences which result from additional checks performed by the State and <br />reported to RTi within 2 weeks of the projected completion date, <br /> <br />0870 <br /> <br />Scope of Work, HB - CRDSS, 1/30/97 <br /> <br />9 <br />