Laserfiche WebLink
<br />e <br /> <br />e <br /> <br />- <br /> <br />003H7 <br /> <br />Batch transfer of data involves moving entire files from one computer system <br />directly to another. This is accomplished through a physical connection <br />between the machines (e.g. a modem connection on each machine). and <br />specialized communications software (e.g, kermit, procomm. etc.), Using this <br />mode of transfer. data are duplicated on both machines. Hardware (modems <br />and phone lines) and software are readily available and in common use for this <br />type of data exchange. <br /> <br />The last mode of data exchange is interactive data communications. This mode <br />of exchange involves moving small packets of data between machines, The <br />data needed. by an agplication progI'am can be retrieved when the application <br />needs the data (e.g. entire files of data do not have to be moved around), The <br />machines are physically connected, In addition. there are specialized <br />communications protocols that interpret the packets of data and assure that <br />they are being routed to the appropriate machines, There are a variety of <br />communications hardware (e.g. TI. T3, SLIP, etc.) and seIVices (e.g. Colorado <br />SuperNet. interNet, etc.) that suppon this type of data exchange. In addition, <br />there are industry standard protocols for this type of communications (e,g. <br />TCPIIP). This is the most sophisticated and high performance method of data <br />exchange. <br /> <br />Alternative DSS Architectures <br /> <br />The goal of this task can be phrased as: <br /> <br />"Mapping user needs onto system functionality through various system <br />architectures. such thaI a maximum number of evaluation criteria is satisfied." <br /> <br />Four components involved in evaluating system architectures for CROSS <br />(Figure 4) must be addressed: <br /> <br />User Needs: Needs must be mapped on available architectures. <br /> <br />Functionality: This component refers to a system architecture which allows <br />flexible representation and accessibility of information regarding state, <br />processes. and the analysis of any of these types of information with <br />sophisticated analysis tools, <br /> <br />Access: This component refers to the various ways in which a CROSS might <br />be accessed by users. <br /> <br />User Interfaces: This component refers to the part of the system with which <br />users interact directly. <br /> <br />Evaluating an overall system architecture for a complicated system such as <br />CRDSS has the..inttinsic.danger of becom,ing c:ntangled in the complexities of <br />the many Closs-relationships which exist between the various components. It <br />was therefore decided to evaluate the three non-user need categories separately <br /> <br />Goal and Reducing <br />Complexity <br /> <br />DAMES&MOORE/CADSWES.27 <br />