CRDSS_Task1_05-31_OverallCRDSSUserInterface

• Title: CRDSS Task 1.05-31 - System Integration Issues Overall CRDSS User Interface
• Description: This memorandum unifies the concepts of “data interfaces” and “graphical interfaces” under the envelope of “user interfaces.”
• Decision Support - Doc Type: Task Memorandum
• Date: 7/28/1994
• DSS Category: DMI Utilities
• DSS: Colorado River
• Basin: Colorado Mainstem
• Contract/PO #: C153658, C153727, C153752
• Grant Type: Non-Reimbursable
• Bill Number: SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
• Prepared By: Riverside Technology inc.

available (e.g., plotting, on-line documentation). The need for additional tools for Year 2 tasks will
be anticipated at the end of Year 1.
3.0 CONCLUSIONS AND RECOMMENDATIONS
The following recommendations are made related to the issues presented in this memorandum:
The general framework of the CRDSS will be a UNIX script that sets important
?
configuration parameters and controls program executions. A version of the CRDSS
interface that has a GUI will be developed to control the execution of the major CRDSS
components. Minor components of the CRDSS will be accessible from the UNIX script but
may not be accessible from the GUI within Year 1. Some components will never be
available from the GUI because they are of little use to the user (e.g., database
administration tools).
The major components of the CRDSS are the models (AOP, CRSM, MODSIM,
?
Consumptive Use) and their interface programs; the general database browse tool; and the
main CRDSS shell. The AOP and CRSM models will have GUI programs (one program
may be sufficient since the models have similar functions). DMI utilities for the AOP and
CRSM models are not required because the data for the models will be acquired from the
USBR and will not be taken from the CRDSS database. The MODSIM model GUI will be
the existing interface program. DMI utilities for MODSIM will be developed to provide
data to the MODSIM GUI and are not anticipated to have GUIs. The main DMI utility for
the consumptive use model will have a GUI and will rely on GIS to format data for the
model.
The minor components of the CRDSS consist of supporting DMI utilities and software
?
tools. DMI utilities will generally not include a GUI unless the data being transferred by
the DMI is map-based or requires extensive user input. Public domain software that uses
GUIs will be implemented under task 1.05 and will be made available to all tasks.
GUIs for models will generally be developed by the group developing/porting the model.
?
The GUI for the AOP and CRSM will be developed at CSU and will be reviewed by RTi.
The existing GUI for MODSIM will be implemented by CSU. The GUI components of the
consumptive use model DMI will be developed by CSU. The CRDSS shell will be
developed by RTi. Additional tools (such as DMI utilities) will be developed by RTi with
input from the specific tasks for which the DMI is being developed.
CRDSS interface components will first be mocked up using GUI builder tools. The
?
mockups will be reviewed by appropriate task leaders and by RTi. Preliminary
implementations of application interfaces will be developed and will be reviewed by RTi.
The applications will then be reviewed by the State. Finally, the applications will be
installed on the Briefing Room machine and will be reviewed in a working environment by
users. Changes to the interfaces will be implemented in future cycles of the prototype.
7
A275 07.28.94 1.05-31 Malers