Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />. <br /> <br />'''J.'''-'7 <br />,il. ." P <br />.. ~..I,...... <br /> <br />12-6-91 <br /> <br />SCOPE OF SERVICES <br />Page 15 <br /> <br />Subtask 2.3.b, 2.3.c,...: Generic Unit Programming and Testing Subtask <br /> <br />In general, each subtask will have a similar pattern: a programming phase followed <br />by a testing phase. The programming specification should provide detailed guidelines for <br />the programming phase. The programming phase will not be considered complete until the <br />code is thoroughly documented with comments. Prior to beginning each testing phase, the <br />engineer responsible for the programming will write a test plan to identify areas that <br />should be tested. The testing will be accomplished by the engineer who wrote the <br />computer code. This type of testing is commonly known as ''white box" testing. <br /> <br />Although the integration of the subunits is not a critical objective of this phase, as <br />modules are created and tested, they will be integrated into a temporary system. This <br />integration process will assist in later unit testing and serve to identify integration problems <br />before the beginning of Task 2.4. <br /> <br />Subtask 2.4: System Integration and Testing <br /> <br />The objectives of this task are to integrate all the subunits and components of the <br />Planning Model into a complete system, to exhaustively test the complete system, to release <br />a test system to a selected group of users to uncover any remaining problems and release <br />a final version of the model. <br /> <br />Subtask 2.4.a: System Integration and Internal Testing <br /> <br />The objective of this task will be the overall integration and testing of the subunits <br />produced in Subtask 2.3. Although some integration will be accomplished in Subtask 2.3, <br />thorough testing will await completion of all subunit programming and testing. Internal <br />testing will be accomplished by both the engineers responsible for the software and by <br />users unfamiliar with the software. The former testing method is known as ''whitebox'' <br />testing because the designers and producers know the internals of the software. The latter <br />testing method is known as "blackbox" testing because the tester is not familiar with the <br />software. <br /> <br />Subtask 2.4.b: Model 8asPlinp Calibration <br /> <br />The objective of this subtask is to calibrate the Planning Model to a baseline <br />representative of existing water development conditions in the basin. Calibration will <br />proceed by comparing model-predicted streamflow and reservoir storage conditions to <br />observed conditions over a specified validation period and progressively modifying selected <br />