Laserfiche WebLink
After identifying the displays to be supported, the GUI will be developed using the XVT GUI <br />builder. Both the model and the interface could potentially be ported to a PC because it is <br />anticipated that this model will not require links to the CRDSS database (data will be supplied by the <br />USBR). DMI utilities will need to be developed if any of the data or output from the AOP data set <br />are to be made available to other applications via the CRDSS database. The work needed to mimic <br />the existing AOP model interface will be completed in Year 1. Minor enhancements will be made in <br />Year 2 if deemed necessary by the State. <br />The GUI development work will be coordinated with the CRSM task and will be performed by <br />personnel at RTi and CSU. Because the GUI development is limited in extent and is for an existing <br />model, hands-on development by one person at CSU, with review by RTi, may be appropriate and <br />cost-effective. The look and feel of the GUI will be consistent with other GUIs because the GUI will <br />conform to Motif standards. <br />CRSM Model <br />The displays for the CRSM model interface will be similar to those developed for the AOP model <br />interface and may, in fact, be the same interface as used by the AOP model. The CRSM task leader <br />from RTi will consult with State personnel familiar with the CRSM to determine which AOP <br />displays can be applied to the CRSM interface and whether additional displays are needed. As with <br />the AOP model, the CRDS model data will most likely not come from the CRDSS database because <br />it will be supplied by the USBR and because the CRSM model is slated to be abandoned in Year 2. <br />The work needed to implement a CRSM model interface will be completed in Year 1. Minor <br />enhancements will be implemented in Year 2 in response to State requests. <br />GUI development will be done in conjunction with the AOP interface GUI development and will <br />therefore most likely involve CSU labor with review by RTi. Similar to the AOP interface, the <br />CRSM model and interface could potentially be ported to a PC. <br />Displays that are outside the scope developed for the AOP model interface may be satisfied by using <br />third-party or other display tools and may therefore not require additional development (see below). <br />MODSIM Model <br />The consultant recommends that the existing MODSIM interface, which uses Motif, be used with <br />minor changes. The interface will be modified slightly to provide consistent look and feel with other <br />CRDSS interfaces and to provide additional features that are required for the CRDSS. Code sharing <br />between the MODSIM interface and other programs that use Motif code will be implemented where <br />possible; however, the GUI code in the interface comprises only a small part of the total code for the <br />interface (the remainder is control code to handle data). The MODSIM interface does make <br />XMgr xbae <br />extensive use of public domain tools (e.g., the plotting program and the spreadsheet <br />library). The consultant recommends that continued study of the MODSIM interface throughout <br />Year 1 will indicate whether changes to the interface need to be made. Changes to the interface will <br />be the responsibility of the CSU staff who maintain the model and interface. The existing MODSIM <br />interface (with changes needed to support CRDSS modeling activities during Year 1) will be <br />completed during Year 1. <br />Rewriting the MODSIM interface using a portable GUI builder should only be considered if budget <br />exists to do so and if it is anticipated that such an interface will be used on a PC. However, because <br />4 <br />A275 07.28.94 1.05-31 Malers <br />