My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP01852
CWCB
>
Water Supply Protection
>
Backfile
>
1001-2000
>
WSP01852
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 12:33:05 PM
Creation date
10/11/2006 10:40:34 PM
Metadata
Fields
Template:
Water Supply Protection
File Number
8449.850
Description
Miscellaneous Small Projects and Project Studies - MWSI
State
CO
Basin
South Platte
Date
9/17/1993
Author
Hydrosphere Inc.
Title
Proposal for the Metropolitan Water Supply Investigation
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
45
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 />.' <br /> <br />Metropolitan Water Supply Investigation Proposal <br />Hydrosphere, Inc. <br /> <br />Septmber 17, 1993 <br />Page 54 <br /> <br />Cost <br /> <br />The initially estimated budget for this task is $12,000. <br /> <br />Model Development <br /> <br />Purpose <br /> <br />The purpose of this task is to develop a model for use in the MWSI Project to <br />investigate the yield and operational aspects of a variety of system integration opponunities at a <br />reconnaissance level. In addition, the act of model creation forces a fonnal evaluation of the <br />implementation techniques-both from a modeled perspective and that of real life-associated <br />with the modeled system. This latter purpose of model creation is often overlooked in the rush <br />to inspect modeled data but it is a valuable output from model creation in and of itself. <br />especially with new proposed systems where the real life implementation is not fixed and can <br />be investigated using the model. <br /> <br />The model will be developed either as a new model or as a modification of existing <br />modeling tools such as Denver's updated model. <br /> <br />Methodology and Evaluation Techniques <br /> <br />The basic course of development will be largely detennined during the scoping and <br />specification phase of the Study. The functional specification developed in Task 9 will serve to <br />determine more exact requirements needed prior to commencing this task. If a new model is <br />detennined to be needed, the model will be developed as an application of Hydrosphere's <br />CRAM modeling tool. If a modification to Denver's model or some other existing model is <br />the selected procedure. Hydrosphere will work with others to effect such modifications, with <br />the exact roles of the various panies to be detennined as the Study progresses. <br /> <br />The model will be developed to maximize its compatibility with Denver's modeling <br />efforts with regard to such things as study period, natural hydrology, etc. The model will be <br />tested and validated against a known "baseline" scenario of existing water rights, operating <br />procedures, facilities and demands. An elaborate calibration and validation effort is not <br />anticipated since the MWSI Project model will be used for preliminary investigations, and any <br />promising water supply options will be "proven out" using other capabilities (i.e. Denver's <br />model). <br /> <br />Once the baseline system has been created, integration opponunities will be modeled "on <br />top or the baseline system. Interestingly, integrated system operations are often easier to <br />model because legal and physical constraints present in the baseline model are removed from <br />the baseline modeled assumptions. <br /> <br />Fast track software development is best accomplished by providing a detailed <br />specification of the desired capabilities, the functional specification, and then following an <br />iterative prototyping approach until the desired final product is created. This is the suggested <br />approach for the MWSI model given the time and budget constraints associated with this <br />project. <br /> <br />Quality assurance and quality control are an important pan of any software project <br />regardless of the development method. Testing should first be undertaken at the software <br />module level ("unit testing") and proceed upwards to the entire product ("system" or <br />
The URL can be used to link to this page
Your browser does not support the video tag.