Laserfiche WebLink
<br />5.2. Run Scripts Create and run the scripts developed above to create the database <br />spaces, the database itself as part of HydroBase. The table creation scripts contain the <br />table and attribute definitions as well as constraints and indexing strategy for each <br />table. The SQL scripts available from ERWIN in the development of Figure 1.1. will <br />be used as a starting point, but will need to be modified to include any indexing <br />strategies necessary for the administration tool. Note: the tables will be populated by <br />Task 2, Data Collection, Task 6,V AX to Server Database Utilities, Task 15, <br />CWRA T Implementation I, and Task 20, CWRA T Implementation II. <br /> <br />5.3. Develop ACCESS tables Build the local, ACCESS, database tables to mimic <br />relevant portions of HydroBase for use by a Water Commissioner. Note: the tables <br />will be populated by the procedures developed in Task 7, Client-Server Database <br />Transfer Routines. <br /> <br />5.4. Review DMI relative to HydroBase Scope Review DMI routine requirements and <br />implement additional updates relative to the HydroBase Scope. <br /> <br />5.4.1 Review DMI Routines Relative to HydroBase Scope Identify changes in <br />existing D1'-.11 routines ('.Veb interface, State~v1od, CD, etc.) needed to support <br />embedded SQL (ESQL) database connectivity required for the CWRAT and not <br />covered in the HydroBase Scope. <br /> <br />5.4.2. Update DMI Routines Update the routines identified in Task 5.4.1. to work <br />with the HydroBase design. The approach, which might include using ESQL or <br />ODBC-based queries, will be detennined in Task 4, Recommended. Software <br />Tools. . <br /> <br />5.4.3.Create an Object Map of the Relational Database This task will identify <br />objects that are necessary for displays and the administrative tool, without regard <br />to the programming language being used. Objects may closely match the <br />relational database table structure but will likely require table joins in many <br />instances. For example, to display reservoir infonnation may require definition of <br />reservoir characteristics, net amount and transaction water rights, and time series, <br />all as objects. The recommended software tools will have some impact on the <br />object definitions, but C++ and Java have a similar syntax when defining objects. <br />RTi will summarize the database to object map in a Developer's Manual Word <br />document that will be reviewed by the State. <br /> <br />5.4.4.Develop class library (or libraries) In this task, implement the data and <br />member functions for the objects identified in Task 5.4.3. This will involve <br />writing code (Java or C++, as defined by the recommended software tools) to <br />implement the object definitions to store data and query functions to query and fill <br />data members. The completion of this task will result in reusable (Java or C++) <br />code that can be used for display and analysis tools. A subset of this code will be <br />used in Task 5.7 to implement a test of all database components. <br /> <br />5.5.Draft Documentation Document the results of the database build and DMI <br />construction for inclusion as a new section in the Developer's Manual in MS Word <br />fonnat. <br /> <br />c.\w\crdsslscope\ph I IIb\scope.doc <br /> <br />0720 <br /> <br />4/24/97 - 14 <br />