Laserfiche WebLink
<br />.... . . <br /> <br />Functional Specification for the Planning Model . '. <br /> <br />.'. <br /> <br />3. <br /> <br />Specifying a Scenario. Modifying the Network Structure. The <br />preferred means of indicating any changes or additions to the <br />arrangement of arcs and nodes In the network will be by operating <br />directly upon the network diagram with graphical methods. The <br />advantage of this approach.is primarily that it will, if successful, enable <br />each scenario to be illustrated by a network diagram which represents <br />. all of its components, including components which may not be included <br />in the Baseline. <br /> <br />e <br /> <br />This feature, referred to as the :Network Drawing Tool," is an <br />important component of the user interface design, Implementation of <br />this feature, however, requires the development of new technology and <br />will be supported in part by resources outside of the Gunnison Basin <br />Planning Model Project, Accordingly, it is not possible to specify <br />completely the functionality of the Network Drawing Tool at this time, <br />Progress will be reported regularly to the steering committee during <br />the programming specification and implementation phases of the <br />project. <br /> <br />The graphical design of network models is more nearly an intuitive <br />activity than is the writing of computer code, Still, specifying <br />modifications of the Baseline nelwork will not be trivial or errorproof. <br />In order to support users in this activity, the user interface will provide <br />some generic constructs for complex entities, such as reservoirs, which <br />can be "snapped" into the network diagram at appropriate locations, <br />The use of such constructs will enable the software to assist the model <br />user in defining appropriate parameter values. Moreover, the software <br />will be able to "operate" new instances of such constructs correctly <br />within the multi-step solution process, Additional guidance for the <br />graphical modification of the network will be provided through written <br />examples in the user manual, <br /> <br />e <br /> <br />4. Specifying Output Data for a Model Run. One means of specifying <br />the output to be generated during a model run could be similar to the <br />method of accessing point-specific data. If the user were in the process <br />of specifying output, selecting an arc or construct in the network <br />diagram could result in the display of a list of possible parameters, <br />from which the user might select those to be included in the output <br />from the model run. <br /> <br />Error Checking <br /> <br />As a user specifies the series of changes in the Baseline which will define a new <br />scenario, there will be opportunities for the interface to detect errors in logic, completeness <br />and internal consistency, Examples include range testing of parameter values and network <br />"logic" testing. The interface might present an error message, for instance, if the user <br />attempted to specify a negative physical capacity, if the sum of storage account limits exceeded <br />the volume of the corresponding reservoir, or if the user attempted to define an "illegal." <br />network configuration, such as a return flow entering the middle of a standardized construct. <br /> <br />The scope of possible error checking is limited by the design goal of flexibility. for users <br />to specify unforeseen configurations of the network and to design their own analytical <br />strategies for investigating problems. <br /> <br />. <br /> <br />20 <br />