Laserfiche WebLink
3.0 CONCLUSIONS AND RECOMMENDATIONS <br />Based on the above discussion (and discussion in referenced task memoranda), the following <br />conclusions and recommendations are made: <br />The general development schedule for the CRDSS software is that of ?stepped <br />? <br />development,? whereby a simple but functional system is developed first, followed by an <br />enhanced system having more features (e.g., advanced GUIs). The development schedule <br />varies among the CRDSS components due to the varying complexity of the components. <br />Programs that are being developed to display data have the option of dumping data to an <br />ASCII file so that the data can be viewed in an existing tool (e.g., a spreadsheet), if <br />necessary. <br />Prototype revisions will be tracked using revision control, as discussed in Task Memoranda <br />? <br />1.05-20 and 1.05-22. In particular, executable programs will have version numbers that <br />apply to a particular prototype. RTi will catalog file revision numbers for each software <br />product. <br />A stable prototype will be maintained by freezing the software that is part of that prototype. <br />? <br />The master copy of the current prototype will exist at RTi and will be copied to the Briefing <br />Room machine. Development will continue on the next prototype by building on dated <br />copies of tested software libraries. <br />RTi will maintain one machine that has a similar configuration to the Briefing Room <br />? <br />machine. The prototype system will be tested at RTi before it is updated on the Briefing <br />Room machine. <br />The entire prototype system will be updated infrequently. Individual components of the <br />? <br />prototype will be updated as important changes are made to those components. <br />Users and reviewers will be notified of new prototype versions through formal methods <br />? <br />such as the Briefing Room bulletin board, the CRDSS update newsletter and Faxes, and <br />informal methods such as E-mail, phone conversation, and personal conversation. The <br />method of contact will vary according to an individual's interest in evaluating the system, <br />and the individual's access to E-mail. <br />The configuration of the system can greatly affect prototyping procedures, and the configuration of <br />the system is controlled to a certain extent by the performance of the system. Consequently, <br />adjustments made to increase performance may affect prototyping procedures. For example, if <br />database performance requires that a copy of the CRDSS database exist in Denver, then changes to <br />the database structure at RTi would not require an immediate update of software on the Briefing <br />Room machine. <br />7 <br />A275 01.08.95 1.05-22 Malers <br />