Laserfiche WebLink
<br />. .. .... <br />o ~ r <br /> <br />~ ~. '. <br />"!. (' <br /> <br />Functional Specification for the Planning Model <br /> <br />User Interface Design Objectives <br /> <br />The design of a "user interface" for a computer program encompasses all aspects of how <br />the "end user" obtains useful information or results from the program. A traditional user <br />interface for a model of a hydrologic system might involve a time-consuming process of <br />communication between the end user and a technical conSultant, who would modify and <br />actually operate the model and provide the output together with analysis and conclusions to the <br />end user. The technical consultant might operate the model by making changes to a <br />combination of computer "files" containing code, data and commands, which would be obscure <br />or incomprehensible to the end user. <br /> <br />. <br /> <br />Generally speaking, the advantages of the traditional approach are the freedom the end <br />. user enjoys in formulating hypothetical situations to be simulated and the freedom the <br />consultant has in tailoring the model to address a particular set of questions. The end user also <br />benefits by saving the design and implementation costs of a more general model and of more <br />convenient means for operating the model. <br /> <br />Disadvantages of the traditional approach include the following: <br /> <br />1. The cost of the consultant's time for performing each model run, even <br />if partially offset by lower initial design costs, inhibits the end users <br />from making full use of the model. <br /> <br />2. <br /> <br />The leadtime required for end users to obtain results from each <br />successive model run inevitably limits the potential value of the model <br />as a vehicle for exploring and learning about the real-world system <br />represented by the model. <br /> <br />e <br /> <br />3. <br /> <br />The tendency of a traditional model to evolve as new questions are <br />presented means that there may be uncertainty about the degree to <br />which current and previous results are genuinely comparable. <br /> <br />4. The consultant's limited capacity to perform model runs inevitably <br />restricts the number of organizations having an opportunity to specify <br />scenarios and to explore planning issues from their own perspectives. <br /> <br />5. The separation which is maintained between the end users and the <br />model limits the extent to which the end users can develop an <br />understanding of the model and, therefore, develop confidence in the <br />results produced by the model within its proper scope of application. <br /> <br />Compared to these advantages and disadvantages, it is clear that the objectives for the <br />Gunnison Basin Planning Model dictate a very different type of user interface from the <br />traditional approach. The primary user interface criteria for the Planning Model are as <br />follows: <br /> <br />I. Each end user should be able to operate the model without assistance <br />and should be able to fashion his own approach to exploring those <br />questions which are of greatest interest to him. <br /> <br />2. <br /> <br />All end users should be able to get comparable answers to comparable <br />questions, or should, at least, be able to understand how their different <br />interpretations of a question led to different results. To this end, the <br />model should automatically document differences in assumptions used <br />in different model runs. <br /> <br />. <br /> <br />16 <br />