My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-29_PCAccessOfCRDSS
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-29_PCAccessOfCRDSS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:52 AM
Creation date
5/30/2008 3:41:57 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.05-29 - System Integration Issues PC Access of the CRDSS
Description
This memorandum discusses the issues related to the ability of PC users to utilize the CRDSS.
Decision Support - Doc Type
Task Memorandum
Date
6/29/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.
/
8
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
Third-Party Database Access Tools <br />Several third-party database access tools exist for PCs. Examples are Power Builder from Powersoft <br />and 4GL++ from INFORMIX (forthcoming). Other products are ViewPoint from INFORMIX, SQL <br />Windows and Quest from Gupta Technologies, and Microsoft Excel, to name a few. These products <br />allow custom database applications to be quickly created on a PC such that the PC can query any <br />number of databases that conform to the Microsoft ODBC (Open Database Connect) standard. <br />Consequently, a PC user can access a database using an interface that has been customized for that <br />user (or for a general class of users). If a list of database products (meaning reports, graphs, etc.) can <br />be identified within the CRDSS, then such a tool may be used to provide access to the database. The <br />limitation on the products is that they typically require transparent network connectivity. In other <br />words, the PC must be connected to the database server machine by a network such as a Novell <br />network or the Internet. A SLIP connection could provide this connectivity, but the limitations of <br />this type of connection must be considered. <br />Supporting PCs and UNIX Workstations <br />Many topics can be discussed when addressing the issue of ?support.? Of major importance are <br />support from a development standpoint and support from a maintenance standpoint. <br />If an application is to be supportable from a development standpoint, then development efforts for a <br />specific ?product? should be efficient and straightforward. The most desirable result is that the <br />software developed for the workstation will port to the PC. This eliminates the need to support <br />multiple versions of the software and consequently eliminates the need to have workstation ?experts? <br />and PC ?experts.? RTi has proposed that all development conform to accepted industry standards <br />such as ANSI C and FORTRAN programming languages (see Task Memorandum 1.05-28). These <br />standards will ensure that much of the CRDSS code can be ported. However, because PC hardware <br />and operating systems have inherent limitations, the consultant also recognizes that some software <br />will not port from a workstation to a PC. Such software includes third-party software such as <br />INFORMIX, over which the consultant has no control. In terms of database access, third-party PC <br />products such as Power Builder and 4GL++ can be used to provide access to the database and the <br />same application may work on the PC and workstation. In terms of some of the more fully-featured <br />CRDSS applications (e.g., the modeling applications), it is unlikely that the full functionality of the <br />software could be ported to the PC. The consultant has recommended that a portable GUI builder be <br />purchased for the CRDSS development effort (see Task Memorandum 1.05-15). Such a product will <br />allow new GUI code to be portable between workstations and PCs. Again, however, some <br />applications may not be suitable for PCs because of limitations of the PCs. <br />Support from a maintenance standpoint refers to the fact that software that is distributed to users <br />must be maintained regardless of whether the software changes. Software that is written for PCs will <br />ideally run on every PC; however, because PCs have widely varying configurations, there is no <br />absolute guarantee that software written for a PC will actually run on all PCs. Also, software will <br />need to be updated to reflect changes in PC operating systems. PC software written as part of the <br />CRDSS could be written for a PC that has certain minimum configuration requirements; however, <br />such a requirement may impose a penalty on users who cannot supply such a configuration. <br />Supporting all PCs will pose problems to the CRDSS team. <br />An overall concern for the consultant is that if extensive PC development is to take place, then <br />budget for such efforts must be made available, possibly by reallocating Year 2 funds. There is a <br />4 <br />A275 06.29.94 1.05-29 Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.