Colorado Water Resources & Power Development Authority Jan 2003

• Year: 2003
• Title: Board of Directors Meeting
• Author: Colorado Water Resoures & Power Development Authority
• Description: Board of Director Meeting Jan 24, 2003
• Publications - Doc Type: Other

completed) from the SWAA and CI contractors. The Contractor will note formats, fields, relationships, field
• population densities, and available documentation associated with each data source. The Contractor has been
provided with the WQCD's spatial data library through their efforts on the Contaminant Inventory project and the
distributed databases (excluding the compliance databases) were provided to the Contractor on June 14, 2002
(except for the PCS). It is assumed that the final databases will be provided to the Contractor by November 15,
2002 (except for the CI project.data).
Task 2: Develop Functional Requirements
Note: this entire task is a Pre -PDR task which has been completed by EnecoTech and accepted by WQCD.
Pre -PDR (entire task)
Prior to the assignment of the contract to Contractor, Hydrosphere delivered a draft Functional Specification
Document (FSD). The Contractor will revise and complete the FSD.
The objective of this task is to develop more of the details behind the concept definition and produce a functional
requirements document. The Contractor's project team will meet with the client team to discuss in more detail the
parameters of the project, from both design and functionality perspectives. The findings from this meeting will then
be developed into a set of Functional Requirements that will be presented to the client team for review,
modification, and, ultimately, approval. These Functional Requirements define what the system is intended to do as
well as the success criteria for the development phase. The Functional Requirements will be developed by
completing the following tasks:
Task 2.1 Project Summary and Purpose Statement
Based on the concept definition, create a project summary, a purpose statement, and a rough feature list. In this task,
• the development team details in writing its understanding of the requirements of the client team.
Task 2.2 Clarify Requirements
Review relevant facts, assumptions, projectsummary, purpose statement, and feature list. This task gives the client
team the opportunity to clarify the requirements of the proposed system, ensuring that the development team
thoroughly understands the needs of the client team.
Task 2.3 Create Functional Specification Document
Finalize and approve relevant facts, assumptions, project summary, .purpose statement, and feature list. This stage
signifies that the development team and the client team are in complete agreement on the purpose and basic features
of the software.
Final deliverables include:
♦ A Purpose Statement;
♦ A Project Summary; and
♦ A Functional Requirements Document (including a Context Diagram).
Note that activities during this task may result in modifications in the scope and costs currently described for Tasks
3-13.
Task 2.4 Determine Milestone Deliverables
Jointly determine with the WQCD the acceptability criteria for subsequent PDR and CDR milestones. This will
involve two meetings with the WQCD.
Second Amendment SA SWAP MOU -final 01/16/03 Page 5 of 13