INTRODUCTION TO DSS DEVELOPMENT was completed, it was refined and deployed to users. Then the next module was developed,

6.2 INTRODUCTION TO DSS DEVELOPMENT was completed, it was refined and deployed to users. Then the next module was developed,

refined, and added to the system; then the next; and so on. The system evolved as more and more subsystems could be feasibly developed within the budget and on time. And, as the team and managers learned more about business problems by working with users and managers throughout the development process, they were able to refine the way the older subsystems worked and use their newfound knowledge in developing the new modules. The IMERYS Case Application 6.1 was developed in a similar manner. As more was learned about the structure of the real system from DSS users and experts, the new knowledge was incorporated into the newer modules and the older ones were either updated or scheduled to be

updated. The large-scale HR InfoNet system was developed quickly by using a common in- house technology platform. HR InfoNet was created by a team consisting of IS specialists

and HR specialists. This was an institutional DSS designed to be used on a recurring basis by many employees, some of whom were not computer literate. Finally, the system continues to evolve because its success led managers and the team to see new ways to apply the ideas developed to other decision-making situations.

Development of a DSS, especially a large one, is a complicated process. It involves issues ranging from technical (e.g., hardware selection and networking) to behavioral (e.g., user interfaces and the potential impact of DSS on individuals, groups, and the entire organization). This chapter concentrates mainly on DSS software development

issues. Because there are several types and categories of DSS, there is no single best

approach to DSS development. There are many variations because of the differences in organizations, decision-makers, and the DSS problem area. Some DSS are designed to support a one-time decision, like the Scott Housing decision (Web Chapter), whereas the IMERYS DSS.fn Case Application 6.1 was developed for recurrent use. Some systems can

be developed in a few days in an OLAP package, spreadsheet, or another tool, while others, like the Osram Sylvania HR InfoNet, took several months and will continue to evolve over the next several years. We now explore issues involving DSS development time, managerial aspects, change management, and more.

67. 310 PART 1/

DECISION SUPPORT SYSTEMS "

USER INTERFACE PROTOTYPING LEADS TO DSS SUCCESS

Some years ago, I worked for an international consult-

menus, displays, and reports-so that the industrial

ing firm in Pittsburgh, Pennsylvania. I visited a large engineering chief could see how the system would look midwestern (U.S.) tractor manufacturer to determine its and work (many users view the user interface as the needs for an assembly line balancing method and to entire system). propose a decision support system. If the company

With the interface prototype, the client saw what accepted the proposal, I would implement it. Though

there are many methods for solving assembly line bal-

he was going to get. The prototype enhanced user and

ancing problems, this situation was different. Even managerial involvement, and guided their expectations. It was a focal point that led users and managers to feel though I was familiar with published work on line bal- that the proposed system would be exactly what they ancing, I discovered that the company's industrial had needed for several years. The proposal was engineers had developed a unique, remarkable, accepted, and the project was initiated and successfully effective approach that utilized information from their completed on time and under budget. The user-interface manufacturing methods database. I did not push prototype also was very useful to me as a system existing methods on them. Instead, I developed development guide. specifications for a unique system and included, as a major portion of the proposal, a prototype of the user Source: Jay E. Aronson. interface-a set of

--------------