Laserfiche WebLink
<br />. <br /> <br />EXHIBIT A <br />SECTION 8 <br />SCOPE OF SERVICES <br /> <br />. <br /> <br />. <br /> <br />This section describes the services the project team proposes to provide to CWCB, <br />The proposed problem-centered design/cognitive walk-through evaluation <br />technique/methodology to be employed in the study is presented. Lastly, the specific work <br />tasks and the products of each task are described. <br /> <br />Evaluation Methodology <br /> <br />The project team will employ a problem-centered design/cognitive walk-through <br />approach for the CRDSS feasibility srudy and conceptual design. The methodology, originally <br />developed and published by Clayton Lewis, has been successfully used in a number of studies <br />and system designs by CADSWES, which include the TV A needs assessment study, the <br />Yuma study, RSS/MODM, and the South Platte Water Rights System. The problem-centered <br />design/cognitive walk-through procedure is an iterative process that converges to a detailed, <br />well documented conceptual design (or desig'lls) or a system. <br /> <br />. <br /> <br />The methodology begins with a series of "brainstorming" sessions involving potential <br />system users in the client organization. The purpose or these sessions is to identify and <br />"walk-through" the typical problems confronted by people in the user organization. The <br />documentation of each problem includes at least two characteristics. The first is a description <br />of the decision that must be made to solve the problem, The second is the definition of a <br />series of tasks that must be performed to make the decision. For the problem definition step <br />to be successful, it is necessary that a mix of people from the client organization extensively <br />participate so that the problem specifications will be sufficiently rich to caprure the essence <br />of the organization's decision needs, <br /> <br />After the initial list or problems is compiled. each problem description is reviewed by <br />the client organization to ensure that the problem descriptions are representative and correct. <br />The problem descriptions are rerined by walking-through them until the client organization <br />feels they are satisfactory. Although the methodology is done at the minute detail level. the <br />designer keeps an eye toward drawing generalizations from the specifics of each problem. <br />Experience has shown that the process converges rapidly in that each new problem requires <br />only marginal additions to the tasks needed to solve the problem. The problem descriptions <br />serve as one of the primary sources of documentation used in the remainder of the feasibility <br />study/conceptual design. <br /> <br />From the problem descriptions, a detinition of the system needs is created. <br />Specifically, a well developed set of problem descriptions provides invaluable information <br />such as who makes which decisions, who is impacted by the decisions, where the decisions <br />are made and impacts felt. what are the data used in making the decision, where do the data <br />exist, what models are needed in making the decision. where do the models exist, what <br /> <br />. <br /> <br />-1- <br />