My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SPDSS_WatRightScope4_20060712
CWCB
>
Decision Support Systems
>
DayForward
>
SPDSS_WatRightScope4_20060712
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/26/2011 8:30:16 AM
Creation date
7/17/2008 10:43:57 AM
Metadata
Fields
Template:
Decision Support Systems
Title
SPDSS Phase 4 - Relational System Integration and Water Rights Administration Component
Description
The Scope of Work for the Relational System Integration and Water Rights Administration components of the South Platte Decision Support System; Phase 4.
Decision Support - Doc Type
Scope of Work
Date
7/12/2006
DSS Category
Surface Water
DSS
South Platte
Basin
South Platte
Contract/PO #
C153966
Bill Number
SB01-157, HB02-1152, SB03-110, HB04-1221, SB05-084, HB06-1313, SB07-122
Prepared By
CWCB
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
31
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
<br />With the test plan document, test files, and StateDMI software, RTi, DWR, and <br />CWCB staff will be able to run regression tests and verify the software at any <br />time. As appropriate, tests can be rerun to evaluate impacts of software and <br />HydroBase changes. Once the formal tests are established, they can help ensure a <br />working system and can help new developers better evaluate impacts of their <br />work. <br />141.9 Additional Enhancements. Additional StateDMI updates/enhancements will be <br />made in order to facilitate data processing in SPDSS. Enhancements that have <br />been previously identified and which maybe implemented after discussions with <br />the State include: <br />1. Update software based on changes in HydroBase, for example to handle <br />seasonal water rights for instream flows. <br />2. Add the capability to add a free water right based on a wildcard identifier, so <br />that multiple set commands are not needed. <br />3. Reference water rights using an "absolute" identifier (e.g., a combination of <br />station ID and administration number) rather than the sequential water right <br />number. This will more easily allow the data set to be enhanced over time. <br />4. Reference reservoir accounts using a "absolute" identifier rather than the <br />account number. For example the owner account (name) could be used. If the <br />StateMod software is updated to use anon-sequential number for the account, <br />then name would not need to be used. <br />5. Remove create*TS () commands, which initialize time series files that <br />have more than one time series. An evaluation of the software as it has been <br />used in production indicates that this enhancement could improve usability. <br />6. Need a way to read water rights for a structure in HydroBase using a different <br />WDID. This is necessary because sometimes a structure spans several <br />districts and the water rights maybe stored in HydroBase in a district other <br />than the headgate. <br />7. Enhance network printing. In particular, the current software has two print <br />dialogs, which can be confusing. Print setup should be streamlined. <br />8. Manage commands files and associated results in a tabbed panel, allowing <br />multiple commands files to be visible and be processed at one time. <br />9. Various cosmetic changes to command dialogs, for example to make data <br />entry fields larger. <br />10. Update commands that use adate/time to enforce a precision more explicitly. <br />Users sometimes do not put in date/times to the correct precision. <br />11. Convert to use the more precise structure_decree_summarytable rather than <br />the structure.dcr_capacity column, for decreed capacity (sum of net absolute <br />water rights). The former properly handles structures with flow and storage <br />rights. Changing this approach will result in some changes in data and <br />therefore the change should be phased in with a command parameter option. <br />25 <br />
The URL can be used to link to this page
Your browser does not support the video tag.