Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />· Openness of architecture; <br /> <br />. <br /> <br />· Execution speed; <br /> <br />· Ease of use; <br /> <br />· Ease of integration with other software applications; <br /> <br />· Maintenance requirements; <br /> <br />. Cost of development and maintenance; <br /> <br />· Ease of distribution/user accessibility; <br /> <br />· Need for user interface languages; <br /> <br />· Portability to other platforms;._ <br />· Platfonn dependent functionality; <br /> <br />· Location 'of data relative to application software; and <br /> <br />· Functional extensibility. <br /> <br />. <br /> <br />From these evaluations and the needs and objectives associated with the overall <br />system, alternative conceptual designs will be developed. The problem-centered design <br />approach outlined earlier will "drive" this part of the feasibility study. This design effort will <br />lead to a complete list or objectives, criteria. data needS and. most imporrantly, a list of <br />functional requirements. These will then be used to evaluate the various conceptual design <br />options in accordance with the !:MAP evaluation procedures specified in the RFP. <br /> <br />TASK 6: OPERATION, MAlNTEJ.'fAJ.'fCE AJ."ID REPLACEJ.'\1EJ.'IT REQUlREMEl'ITS <br /> <br />Introduction <br /> <br />. <br /> <br />The ongoing costs associated with the day-to-day operation of the CRDSS application <br />will include maintenance of the application software, routine upgrades to the system software <br />and upgrades/replacement of the hardware upon which the application will run. Over the <br />projected ten year life cycle of the CRDSS application, it could be expected that these costs <br />will be greatest in the early years. As new users to the system become familiar with the <br />decision-making power of such a tool, it is typical that they become aware of logical <br />extensions to the functionality of the system that would enable them to perfonn tasks that they <br />either cannot do today, or that cannot be efficiently accomplished in the absence of an <br />easy-to-use automated tool. Thus, users typically wish to extend the functionality or the <br />system most heavily in the first two years of use. The costs associated with extending the <br />system capabilities are unpredictable. However. a system designed and written with <br />structured. modular code will be much less expensive to modify as user needs change. <br /> <br />-13- <br />