Laserfiche WebLink
Several developers may work on related CRDSS components at the same time. Consequently, <br />provisions must be made to prevent one developer's efforts from interfering with another's. At the <br />file level, only one user will be permitted to edit a file at any time, and revision control will be used <br />for all code ( see Task Memorandum 1.05-20). <br />Software maintenance will occur at two levels: the file level and the product level. Source code for <br />a program is typically split into its individual code modules (e.g., C functions or FORTRAN <br />subroutines) so that code can be more easily maintained. Code at this file level is placed under <br />revision control (see Task Memorandum 1.05-20). Products (e.g., programs or libraries) consist of <br />groups of source code, configuration, and documentation files. <br />Software maintenance on the product level involves "packaging" the software in a way that tracks the <br />interdependence of software components. Maintenance of the software should be automated so that <br />developers need not worry about updating numerous files when a prerequisite file changes. Task <br />Memorandum 1.05-21 discusses in detail the issues related to software maintenance. <br />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />QA/QC procedures are being developed for the major technical areas: database, water rights <br />planning and consumptive use modeling, and software engineering. QA/QC procedures for these <br />major technical areas will ensure the integrity of the CRDSS database, ensure user confidence in the <br />model results, and ensure the CRDSS is reliable, maintainable, flexible, and portable. <br />3 <br />A275 05.10.94 1.05-4 Ritsch, Day <br />