My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-26_UserInvolvementIssues
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-26_UserInvolvementIssues
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:52 AM
Creation date
5/30/2008 3:34:20 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.05-26 - Study of System Integration Issues User Involvement Issues
Description
This memorandum discusses the user involvement program.
Decision Support - Doc Type
Task Memorandum
Date
5/10/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.
/
6
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
*- Forums (e.g., workshops) <br /> *- Media (e.g., documentation, workbooks, multimedia) <br />*Who will conduct training? <br />? <br /> *- In near-term? <br /> - In longer term? <br />*Documentation <br />? <br /> *- How will it be done ?, What will it look like? <br /> *- How will it be maintained? <br /> *- How can the documentation be used for training? <br />How can training be dovetailed with agency job functions? <br />? <br />CRDSS Maintenance and Evolution Issues . Establishing a basis for the maintenance and <br />evolution of the CRDSS is crucial to the State in order that the system continue to provide the <br />functionality needed. Updates in support software (e.g., INFORMIX datab ase), "bug" fixes, <br />new models, and refined scenarios for application will necessitate a maintenance and evolution <br />plan. Development and continued training of in-house staff will be required; the extent of the <br />training will depend on the degree of self-sufficiency desired. Third-party users have some <br />interest in accessing the source code to review (current) solution procedures; it is not clear to <br />what extent third-party users will seek to make their own modifications to the CRDSS. <br />*How does a modular structure facilitate maintenance? <br />? <br />*Is the source code available? <br />? <br />What are the State staffing capabilities to maintain/evolve? <br />? <br />How does one develop an understanding of the CRDSS? <br />? <br />- Model solution algorithms? <br />- Database structure and management? <br />- Interface functions? <br />*Who will maintain the CRDSS? <br />? <br />Can a user add other models? <br />? <br />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />User involvement issues have been identified and sorted into several functional categories. Many of <br />these issues are being addressed in ongoing CRDSS development work and require no special <br />attention, only vigilance in following through (these issues are identified with a "*" ). Other issues <br />require more attention to determine their relevance, and to ensure that these issues do not detract <br />from the success of the CRDSS. <br />The scenarios need to be refined and extended to include vertical integration of CRDSS <br />? <br />computing functionalities, definition of problem-solving strategies, and examination of the <br />water resources policy impacts of information generated by the CRDSS. This is planned for <br />early in Phase IIa. <br />Other issues require acknowledgment and formulation of strategies seeking resolution. <br />? <br />Foremost among these are issues relating to the long-term management framework for the <br />CRDSS. Suggestions for this have been made in the attached document by Neil Grigg, <br />entitled "Toward a Future Framework for CRDSS Management." <br />5 <br />A275 05.10.94 1.05-26 Johnson <br />
The URL can be used to link to this page
Your browser does not support the video tag.