Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />. <br /> <br />a single location, changes would not have to be propagated among the various functions, and <br />remote users could be prohibited from changing the data. The main disadvantage of this <br />solution is the speed at which the data could be accessed. Low speed modem connections can <br />slow the process down significantly. In addition, the server on which the data would be <br />stored would have to be sufficiently powerful to insure that a large number of users could <br />access the system at the same time without having the server respond too slowly. A possible, <br />and partial, solution to this problem would be to let users download information from this <br />main data server so that they could use it locally and not be encumbered by the possibly slow <br />and frequent data transfers. The downloading of data would have to be a one-way transfer <br />so that data integrity could be maintained. The users could change their local copies of data <br />but would not be able to change the main database. <br /> <br />A final issue to resolve is user ability and technical aptitude with respect to computers <br />and the tasks that they need to perform. The user interface of CRDSS must be designed in <br />such a way that users with a basic familiarity with mouse and keyboard-based computers will <br />be able to efficiently and effectively use the system. To insure that the user interface <br />properly addresses the tasks that users wish to perform, problem centered design will be used. <br />Thus, the interface will have to be iteratively designed such that users' needs are met. <br /> <br />Anmini,;tration <br /> <br />This task will be led by Steve Wehrend who will be assisted by Hussam Fahmy and <br />David Sieh. <br /> <br />. . ~tailed Work Plan <br /> <br />The user intenace options that will be provided will depend on a detailed profile of <br />potential users and their anticipated hardware and software combinations. As with other <br />aspects of this design process, problem-centered design will be used as a basis for <br />determining who will use the system, what hardware and software they will use, and how <br />they will want to use it. These determinations will have to be weighted with respect to their <br />anticipated development and operating costs before a recommendation can be made. <br /> <br />The evaluation of the possible user interface alternatives will be based on a number <br />of criteria. These include: <br /> <br />· user needs and desires; <br /> <br />· hardware and software availability; <br /> <br />· hardware and software cost; <br /> <br />· implementation cost on a variety of hardware platforms; <br /> <br />· data integrity; <br /> <br />. <br /> <br />. access speed; <br /> <br />-11- <br />