Book Contents

Ch. 4
Designing and Developing Decision Support Systems

Chapter Contents
Previous Page
Next Page

DSS Project Participants

A complex DSS built using either an SDLC or a prototyping approach requires a team development approach. Once the system is developed a group may also be needed to maintain the system. Some large-scale DSS are built with teams of 2-3 people or with a larger group of 10 or more. Members of DSS teams are drawn from many areas in an organization, including the Information Systems group.

Any DSS development project requires a mix of complementary skills. Usually one does not find all of the needed skills in one person. So in most situations it is necessary to assemble the right mix of contributors for a DSS project team.

Figure 4.2. Participants on a DSS development team.

The key DSS development roles identified by Sprague (1980), O’Neil et al. (1997) and others are listed below in order of increasing technical expertise. Figure 4.2 summarizes the various roles. A given individual may be assigned more than one role.

Executive sponsor. This is a senior manager who has access to other senior executives and has the influence to help resolve major resource and political problems. The sponsor is occasionally actively involved in the development tasks.

Potential DSS users. This is the person or group responsible for solving the problem and making the decisions that the DSS will support. Users are often non-technical people in functional areas of a business like marketing and finance.

DSS builder or analyst. This is the expert who makes the technical decisions about the software tools(s) to use, the hardware platform(s) to use, the models and/or databases to incorporate into the DSS, and how they will be integrated with each other. This is generally a person with a great deal of experience who understands both the business problem and the available technologies. We also use the term project manager for this development role.

Technical support person. This is the person who integrates existing packages into one overall system and carries out custom programming that contributes directly to DSS functionality. His or her responsibility begins with the packages that will comprise part of the DSS and ends with a functional DSS for the user. A number of MIS professionals are involved as technical support staff including data warehouse architects, application architects and developers. A data quality analyst is often involved in building data-driven DSS. The data quality analyst is concerned with data integration, metadata and data scrubbing.

Toolsmith or technical specialist. This role focuses on the tools and technologies that will be used in the construction of the DSS and the packages that will be combined to create the DSS. He or she is an expert on these tools and packages and their effective use. This is the person who creates underlying capabilities, often not visible to the user, but required for the technical support personnel to carry out their more user-oriented jobs effectively. Data administrators, systems administrators, networking specialists and database administrators are often consulted on DSS projects.

The composition of the DSS team will change over the development cycle so the project manager needs to provide direction and motivation for the DSS team. Also, the executive sponsor needs to maintain an active commitment to the project. Losing a project sponsor can harm and even "doom" a DSS project.


DSSResources.COMsm is maintained and all its pages are copyrighted (c) 1995-2002 by D. J. Power (see home page). Please contact This page was last modified Wednesday, May 30, 2007. See disclaimer and privacy statement.