|
<br />DWR Data Population, is expected to contain approximately IO pages of text and will
<br />include the results of the relationship and constraint checking, the population
<br />verification, the accounting of records, and the spot-checks,
<br />6, Incorporate State comments,
<br />7, Provide a final section of the Developers Manual in the following formats: one hard
<br />copy, one version in Microsoft Word, one version included in the existing on line
<br />(HTML) Developers Manual.
<br />
<br />Task R6 - Revise CRDSS Software.
<br />
<br />Approach
<br />Software to be revised in this Task falls into two categories, I) Existing low-level DMI
<br />routines, and 2) DMI Utilities, All low-level DMI routines use embedded SQL that
<br />perform selects on the database, These routines are coded in ,ec files that are translated to
<br />C by the compiler and are then put into a DMI library,
<br />
<br />DMI Utilities call the low-level routines in standard C fashion, Ideally, only the low-
<br />level routines will need to be modified because the interfaces to the utilities are governed
<br />by functionality, not data storage, However, in some cases, the functionality of a DMI
<br />Utility may need to be revised because of a change in database structure, For example,
<br />additional data items may need to be passed to a DMI Utility or a DMI Utility may be
<br />able to take advantage of a derived table,
<br />
<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 Codinlf Chant!es, 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 />09\.0
<br />
<br />Scope of Work, HB - CRDSS, 12/20/96
<br />
<br />8
<br />
|