Laserfiche WebLink
<br />e; <br /> <br />e <br /> <br />e <br /> <br />Ori3-j58 <br /> <br />Table 5: System Access Architectures <br /> <br />Architecture Description <br />Centralized Data and executable programs are stored and maintained in one <br /> centralized location, This central site might actually be multiple sites, <br /> although it will appear as one site to those using it. Users may access <br /> this site in tile following ways: <br /> _ Through public machines at the central site. These machines will <br /> provide full functionality, yet they may require users to travel a great <br /> diSUlIlce,lOmake.use of them. <br /> _ Remote users with appropriate computing capabilities may copy data <br /> and/or executable programs from the central location to their own site <br /> and use them as they see fit. They may not copy infonnation or <br /> executable programs back to the central location and are responsible <br /> for keeping their infonnation current. This is useful for those with <br /> sufficient computing power. <br /> _ Remote users with low computing power will be able to access the <br /> central location and perfonn some subset of the full capabilities of the <br /> system. <br />distributed Data and executable programs are stored and maintained in the <br /> centralized location and in all disuibuted nodes, The nodes are copies <br /> of the centralized sire in that they will have access to all infonnation <br /> that tile centralized site has access to, The centralized site will be <br /> responsible for propagating any changes to the distributed locations <br /> and infonnation can be passed only from the central location to the <br /> node, This option gives the same functionality as the purely <br /> centralized approach, except that users who do not have sufficient <br /> computing power and wish to use the full system will only have to <br /> travel to their local node, rather tfian to one central location, <br />Stand Alone Data and executable programs are stored and maintained in a <br /> centralized location and in all sites wishing to do so, This option <br /> allows all users who have sufficient computing capabilities to have and <br /> maintain tIleir own copy of both the data and the executable programs <br /> associated with the system. Users with fewer capabilities may also <br /> keep whatever data and executable programs they are able to store and <br /> use, These users would be responsible for updateS of their infonnation, <br /> altllough it would be reasonable to assume that the central location <br /> would a1en them to this necessity, For users with limited functionality, <br /> this scheme degenerates to the centralized approach. in that they will <br /> have to travel to the central location to meet their needs, For users with <br /> more complete functionality. this approach is essentially the same as <br /> either the central or disuibuted approach. <br /> <br />Next, all three architectures were related to the four main use categories, Status <br />overviews, Reporting. Basin Planning and Water Right Administration, The <br />results-,in Table, 6 show that both. the_ centralized and distributed architectures. <br />suppon all four use categories, The stand alone alternative suppons only Basin <br />Planning, <br /> <br />Access Vs, Needs <br /> <br />DAMES & M OORE/CADSWES-40 <br />