My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-32_DesignAndImplementationYear1Summary
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-32_DesignAndImplementationYear1Summary
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:52 AM
Creation date
5/30/2008 3:48:34 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.05-32 - Study of System Integration Issues Design and Implementation Coordination Year 1 Summary
Description
The following issues are addressed in this memorandum: 1)Have the work products defined in the scope of work been completed? 2)What decisions were made in coordinating system development and system integration? 3) Do any concerns about system integration exist for Year 2 of the project?
Decision Support - Doc Type
Task Memorandum
Date
1/9/1995
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.
/
5
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
Development of portability guidelines and implementation of such guidelines. <br />? <br />Development of guidelines for benchmarking and validation and implementation of such <br />? <br />guidelines. <br />Each of the work products has been addressed in the Year 1 work and is discussed below. In general, the <br />work products have been completed according to the scope, but some may require refinement or <br />extension in Year 2. <br />Note that the overall system is integrated by providing access to the system (and its component <br />crdss crdssgui <br />applications) through either the character-based program or the GUI-based program. <br />Adjust the SIT Membership <br />The membership of the SIT has been adjusted during Year 1 as dictated by the needs of the project. <br />Some changes were made due to staff additions/departures, and others were made because of changing <br />responsibilities within project tasks. SIT meetings were held regularly at CSU at which important <br />system design issues where discussed. Both State and consultant personnel attended the meetings. <br />System Design Documents <br />Initial hardware and software for the project is outlined in Task Memorandum 1.04-1. Additional <br />hardware and software has been purchased during Year 1 to address project needs and has been <br />documented in project correspondence. In particular, the portable GUI development software XVT <br />Design has been purchased for GUI development, and several additional hard drives have been <br />purchased to address data storage needs. The Database chapter in the CRDSS Developers? Manual <br />discusses database design and maintenance. <br />Task Order I-001 with CSU was executed to provide Internet service to RTi for the CRDSS project. <br />Addressing real-time data access as related to the database has not been performed as it applies to Year 3 <br />work and is not appropriate at this time. Task Memorandum 1.05-19 addresses Internet use within the <br />project. <br />Task Memoranda 1.05-24 addresses system backup and restore procedures, and the Database chapter of <br />the CRDSS Developers? Manual addresses database backup and restore procedures. <br />The Database chapter of the CRDSS Developers? Manual also addresses efficient data storage and <br />retrieval. <br />GUI Design Guidelines <br />Task Memorandum 1.05-31 discusses the overall GUI design for the CRDSS. General guidelines have <br />been documented in the task memo, in the on-line documentation, and have been discussed at SIT <br />meetings. These include menu conventions (such as always having File and Help menus), overall look <br />and feel (interface colors and fonts), status message areas for interfaces, etc. <br />Many of the GUI features discussed in specifications have been implemented. The main area where <br />conformance is lacking is that some applications do not have the same color scheme, and some fonts are <br />not standard. In some cases this is due to the fact that the functionality of the interface depends <br />2 <br />A275 .01.09.95 1.05-32. Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.