My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-31_OverallCRDSSUserInterface
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-31_OverallCRDSSUserInterface
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:52 AM
Creation date
5/30/2008 3:46:15 PM
Metadata
Fields
Template:
Decision Support Systems
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.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
7
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
CRDSS <br />TASK MEMORANDUM 1.05-31 <br />System Integration Issues <br />Overall CRDSS User Interface <br />1.0 ISSUE <br />Task memoranda 1.05-8 discusses low-level DMI library routines for the CRDSS. Task <br />memorandum 1.05-9 discusses in general terms the structure of a DMI utility program. Task <br />memoranda 1.05-15, 1.05-16, 1.05-17, and 1.05-18 discuss general issues related to building GUIs. <br />This memorandum unifies the concepts of ?data interfaces? and ?graphical interfaces? under the <br />envelope of ?user interfaces.? This is necessary in order to provide guidelines and limitations for the <br />overall capabilities of programs that interface with the CRDSS database and the user. <br />The following issues are addressed in this memorandum: <br />What is the general framework for the CRDSS (how are the large applications organized)? <br />? <br />What are the major components of the CRDSS and what are the DM I and GUI features of <br />? <br />the components? <br />What are the minor components of the CRDSS and what are the DMI and GUI features of <br />? <br />the components? <br />Who is responsible for developing the GUI and DMI components of applications? <br />? <br />What is the prototyping cycle for user interface components? <br />? <br />2.0 DISCUSSION/ANALYSIS <br />The term data management interface (DMI) applies to any application/routine that transfers data <br />from one format (e.g., the CRDSS INFORMIX database) to another (e.g., a flat file used by a <br />model). A ?DMI Utility? is an application that the user runs to perform the data transfer. ?Low- <br />level DMI routines? are the library routines that actually do the work and are not directly visible to <br />the user. A ?Graphical User Interface? may be part of a DMI utility and is used to give the utility a <br />friendly presentation. Consequently, the terms ?DMI? and ?GUI? are not mutually exclusive in that <br />a DMI utility can also have a GUI. Any utility that performs a data translation should be referred to <br />as a DMI utility (or just DMI) with the implication that low-level DMI routines are used in the <br />utility. Additionally, the DMI utility should be described as having or not having a GUI (either is <br />possible). For example, very simple DMI utility may read a time series from the database and print <br />the information to a flat file without requiring any intervention from the user. In this case, there is <br />It should not be assumed that every DMI utility will have a GUI <br />no reason to have a GUI. . <br />CRDSS Framework <br />1 <br />A275 07.28.94 1.05-31 Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.