Laserfiche WebLink
PROJECT MANAGEMENT POLICY COMMITTEE <br /> Coordinate Activities <br /> Policy Decisions <br /> <br /> Maintain Standards Interface to Outside Agencie s <br /> <br /> Resource Staff <br /> Major Project Approvals <br /> Development <br /> Major Equipment Purchases <br /> Central Computer <br /> Central Databases <br />OPERATIONS COMMITTEE <br /> Develop Standards <br /> Exchange Information <br /> Develop Priorities <br />PARTICIPATING DEPARTMENTS <br /> Stewards for Data <br /> Input and Maintenance <br /> Integrate into Job Functions <br />Figure 3. <br /> Typical Agency DSS Development Organizational Structure <br />The Role of User Involvement <br />There are many people that can become involved in the design and use of a DSS. At a minimum, these <br />include the DSS users and their staffs, the DSS designers, the technical support people who work with <br />the DSS designers, and the developers of algorithms which get incorporated into the DSS. The preferred <br />DSS development approach involves successive prototypes and interactions with the DSS user groups. <br />Generally, a user will seldom be able to specify DSS requirements initially. User interaction with the <br />prototypes provides a mechanism for individual and corporate learning so that requirements evolve along <br />with the capacity to use the DSS. <br />User involvement in the design process, management support for the DSS design effort, and availability <br />of user training and feedback activities are but a few of the many requisites for successful DSS <br />implementation. It is especially important that potential users not regard it as too difficult to learn to use, <br />or too time-consuming to actually use, or as producing inaccurate, incomplete, or out-of-date results. <br />Perhaps of greatest concern is the feeling that the DSS interferes with the ?normal? way of thinking <br />about problems, requires significant changes in work patterns, or that it does not address the actual <br />problems that exist. <br />Outline of CRDSS User Survey and Purpose of Questions <br />It is with the above list of intentions that the user survey was conceived and designed. Background <br />information on the issues of concern to the CRDSS users (Appendix A), along with the literature review <br />on DSS design requirements and concerns, helped identify the types of information to be obtained as a <br />result of the survey. The user survey sought to obtain information on the following: <br />User description <br />? <br />Information needs and workflow review <br />? <br />5 <br />A 275 01.09.95 1.19-1 Johnson, Grigg, Tang <br />