Laserfiche WebLink
tstool <br />On-line and hard-copy documentation was implemented and consists of documentation in the <br />CRDSS Users? Manual and time series library documentation in the CRDSS Developers? Manual. <br />Subtask 4. Implement and manage procedures for recording and reacting to users? reports of <br />software or data problems <br />. <br />An on-line call log was implemented in order to track bug reports and user suggestions. This is currently <br />tied into the Software News and User Feedback section of the on-line documentation. Users can email to <br />webmaster@cando.dwr.co.gov to submit problems or can use the on-line submittal form. As items are <br />received they are entered into the log and are assigned a unique sequential number. The system <br />integration task leader makes an initial evaluation of the problem and notifies the appropriate person to <br />initiate a response. The status on the log is updated as a problem is resolved, and, if status ?S?, is ready <br />for review by the State. If the State agrees that a problem is resolved (usually because of a software <br />upgrade), then the item is marked resolved. <br />Subtask 5. Manage system integration activities through system integration team meetings and <br />other correspondence. <br />System integration for the CRDSS has been a significant effort. Most guidelines have been set by the <br />system integration task leader with input from other developers. Emphasis has been made to allow each <br />application in the system to be developed and run independently, using only a few environment <br />variables, if necessary, to configure the application. Initially in Year 2, system integration meetings were <br />held each Thursday at RTi to help coordinate development of the different applications within the <br />CRDSS and to resolve problems. Later, meetings were held every other Thursday at RTi. Attending <br />were all the task leaders or substitutes and State management team representatives. Meetings were <br />approximately two hours. Through these meetings, cross-task issues were discussed and resolved. <br />Subtask 6. Update the crdss and crdssgui programs to include new system functionality developed <br />in Year 2. <br />crdss crdssgui <br />The script and program were updated to configure and run the different applications <br />within the CRDSS. In Year 2 this primarily involved hooking in the StateMod water resources planning <br />crdssgui <br />model. The was also updated to not copy data sets since this functionality is now handled by <br />the scenario manager called from the consumptive use and StateMod models. <br />Subtask 7. Attend State-sponsored meetings related to providing access to users on the Western <br />Slope and other areas of the State. <br />RTi was informed by the State that this attendance was not necessary. <br />Subtask 8. Develop/update the on-line and hard-copy documentation for system integration <br />activities <br />. <br />On-line and hard copy documentation has been written for various system integration activities. This <br />primarily involves the User Access chapter in the CRDSS Users? Manual and the Configuration and <br />Maintenance chapter in the CRDSS Developers? Manual. <br />Subtask 9. Write a task memorandum summarizing Task 2.11 activities and results. <br />This subtask involves the preparation of this memorandum. <br />3 <br />a320/taskmems/ 2-11-01.doc 01/03/97 <br />