Laserfiche WebLink
3.0 CONCLUSIONS AND RECOMMENDATIONS <br />The following recommendations are made for consideration now that the CRDSS on-line and hard copy <br />documentation is in final review: <br />? <br />tstool <br />As is used by more people, its functional specifications should be revised and appropriate <br />updates should be made. <br /> <br />? <br />Based on input from the State management team during software development, it is recommended <br />that future development efforts within CRDSS clearly define the role of the State management team <br />and the briefing room in the testing process. Future software development efforts should identify <br />beta software users with the understanding that the software reviewed by such users is preliminary <br />and subject to change. The budget for review tasks should not be less than twenty-five percent of the <br />software development budget. Each software product development effort needs to have a review and <br />testing task. <br /> <br />? <br />Model development was scheduled parallel to database and tools development and therefore <br />modelers could not take full advantage of the tools until later in the project. In future CRDSS <br />phases, analysis tools should be developed after the database revision, with modeling occuring after <br />the tools are developed. <br /> <br />? <br />RTi was unable to configure the State machines and provide technical information to State staff <br />related to hardware and software considerations. This resulted in miscommunications and delays in <br />system configuration. It is recommended that the State system administration staff be given the <br />budget to more directly support the CRDSS effort and be involved with its future implementation. <br /> <br />? <br />It is recommended that the CRDSS software be more fully-integrated with the workstations on the <br />other State machines to give increased access to the system. This effort would involve system <br />administration activities involving both the State and the current system integration task leader. <br /> <br />? <br />The machines used by RTi are essentially the development environment for CRDSS, while the <br />machines at the State are the distributed, end-user implementations of the system. It is <br />recommended that when the RTi machines are delivered to the State, they remain a separate system <br />containing the development environment. This separation will allow development to proceed <br />without disrupting the working system. <br /> <br />? <br />The hardware configuration of the State machines has, at times, caused performance problems in <br />software, resulting in unresolvable bug reports and unexplained behavior. It is recommended that <br />any workstation running CRDSS have at least 64 MB of main memory, with appropriate swap space. <br />It is also recommended that the database be housed in a separate machine than the rest of the system. <br />This will result in better performances, especially on heavily-used machines. <br /> <br />4 <br />a320/taskmems/ 2-11-01.doc 01/03/97 <br />