Laserfiche WebLink
<br />12-6-91 <br /> <br />SCOPE OF SERViCES <br />Page 12 <br /> <br />. <br /> <br />Subtask 1.4: Functional Specification <br /> <br />Immediately upon completion of Subtask 1.3, Hydrosphere will prepare the <br />Functional Specification. This is the most important document to be generated during the <br />project, aside from the Users Manual. The purpose of the Functional Specification is to <br />capture the information gathered during the Needs Analysis as the foundation for all work <br />in the software development process. The scope of the Functional Specification will <br />include descriptions of each of the components of the simulation model and the logic of <br />their interaction, details of computations, the look and feel of the user interface, and in <br />general all of the topics covered in Subtasks 1.3.a through 1.3.g. The presentation of <br />information in the Functional Specification will include prose supplemented with tables and <br />diagrams. One section will consist of a set of "user session descriptions," which will <br />provide a narrative account of how a user would perform a representative set of typical <br />operations covering all of the capabilities of the Planning Model. The Functional <br />Specification will be written in layman's tenns, and provided to the Sponsors Committee <br />first in draft form, and it is anticipated that several cydes of review and publication may <br />be necessary to arrive at a final document. The Functional Specification document will be <br />part of a Task Memorandum which addresses the procedures, findings, conclusions, and <br />recommendations resulting from the performance of Subtasks 1.3 and 1.4. <br /> <br />. <br /> <br />lntroduction to Tasks 2 through 5 <br /> <br />There is an important logical break between Task 1 and Task 2. Task 1 will be <br />mainly concerned with describing what the Planning Model will be expected to do. <br />Beginning in Task 2, however, the emphasis will change to development of the detailed <br />computer code to accomplish the objectives elucidated in previous tasks. Subtask 1.4 is <br />analogous to an architectural rendering and Sub task 2.1 is analogous to a set of <br />construction blueprints. Because Tasks 2 to 5 will be dependent on the results of the <br />earlier tasks and because the results of those tasks are not currendy known, the following <br />task descriptions are, by necessity, generalizations. <br /> <br />Task 2: Programming, Data Development, lntegration, and Testing <br /> <br />Subtask 2.1: Programming Specification <br /> <br />The objective of this task is to define how the functional specification of Subtask 1.4 <br />will be implemented in computer software. This task will be a detailed (or "low-level") <br />design phase accomplished by the same engineers who will ultimately write the computer . <br />codes for the model. A major deliverable from this task will be a design document whose <br />