Laserfiche WebLink
<br />e <br /> <br />e <br /> <br />e <br /> <br />on'3 H2 <br /> <br />Alternatives <br /> <br />Given a set of requirements, the alternative methods for satisfying the user's <br />needs were investigated. First the nature of how a user could interact with the <br />system was explored in the form of user interfaces. Then the internal <br />organizations of systems providing the functionality, measured along with <br />service delivery to users. The various combinations of user interface, internal <br />organization and delivery were reviewed for probable costs; both for initial <br />development and for ongoing operation, <br /> <br />Definition of Alternative Interfaces <br /> <br />CRDSS will need to accommodate a diverse set of users. These users will have <br />a variety of tasks to perform and a variety of computer types on which to <br />perform them. In addition. they may need to access the system data and/or <br />executable programs remotely. <br /> <br />Tasks that users need to perform include Status, Reporting, Basin Planning, <br />and River Administration, Status entails requesting and displaying data about <br />the historical, current, or forecast state of the river system, Reponing entails <br />updating the database as new data is generated, Basin Planning entails the long <br />term analysis of new projects and policies. Finally, River Administration <br />involves near real-time operations/management of the river system, <br /> <br />Computer interfaces essentially divide into two main categories: window <br />based and non window based interfaces, Window based systems include PCs <br />with windows, MacIntosh and X based workstations and terminals, These <br />systems allow for the use of interactive graphics, Non window based systems <br />are typically text based systems that use command line or form based <br />interfaces, These systems often allow for tne display of static images, <br /> <br />Access to the CRDSS could be accomplished in a number of ways. depending <br />on the location and capabilities of the users. This access may range from userS <br />having both executable programs and data stored on their local macnine to <br />users having to remotely log in to another system to use executable programs <br />and access data. <br /> <br />The goal of this Task is to articulate the issues associated with providing access <br />to CROSS and inventory options associated with these issues, <br /> <br />There are three broad classes of user interface methods that can be used to <br />accomplish the user tasks mentioned above, Tnese are command line, form <br />based, and interactive graphics, <br /> <br />A command line interface requires the typing of commands to enter all <br /> <br />Users <br /> <br />Task categories <br /> <br />CQlIInumd Line ". <br />Interface <br /> <br />DAMES & MOORE/CADSWES-22 <br />