Showing papers in "Management Information Systems Quarterly in 1978"
TL;DR: An MIS strategic planning process is conceptualized and illustrated as one which links the organization's "strategic planning set" to an MIS "strategy set."
Abstract: Planning for the information systems in an organization generally has not been closely related to the overall strategic planning processes through which the organization prepares for its future. An MIS strategic planning process is conceptualized and illustrated as one which links the organization's "strategy set" to an MIS "strategy set."
533 citations
TL;DR: Nine empirical studies which furnish data to test hypotheses derived from a descriptive model of implementation are summarized, hoped that hypothesis testing and models of implementation such as those proposed in [14] along with empirical studies will provide a better understanding of the variables associated with success.
Abstract: This article presents a model of factors associated with the successful implementation of a computer-based information system or OR/MS model. The model hypothesizes that two classes of variables, model quality and management support, influence attitudes and perceptions of a model or system. The research model also predicts that attitudes and perceptions, management support, system or model quality, decision style and situational and personal factors are related to successful implementation.
In general, the relationships in the model receive support from the data; however, further research is needed, particularly to provide more evidence on possible causal links in the model. Certain classes of variables are also difficult to relate to implementation success, including decision style and personal and situational factors.
If the evidence for the model is considered sufficient to take action, implementation strategies should concentrate on several key variables. First, the quality of the model must be high, both in terms of logic and user interface. Favorable attitudes and perceptions should be stressed during development of a model or system. Management support should be encouraged and solicited and the implementor should try to consider different decision styles. Finally, personal and situational factors are likely to be related to success.
The purpose of this article is to summarize the findings of nine empirical studies which furnish data to test hypotheses derived from a descriptive model of implementation. It is hoped that hypothesis testing and models of implementation such as those proposed in [14] along with empirical studies will provide a better understanding of the variables associated with successful implementation.
350 citations
TL;DR: This article provides an MIS evaluation framework and describes its application to a strategic planning information system.
Abstract: Management information systems are not generally evaluated in a systematic fashion. This article provides an MIS evaluation framework and describes its application to a strategic planning information system.
174 citations
TL;DR: The nature of cognitive styles and the effects of cognitive style differences on information system usage and design are explored and suggestions for assisting information system analysts in incorporating the users' cognitive styles differences into information systems design are presented.
Abstract: This article explores the nature of cognitive styles and the effects of cognitive style differences on information system usage and design. Some ideas are presented for clarifying the nature of cognitive styles, and a number of cognitive style models are discussed which are applicable to information system design and research. Suggestions are presented for assisting information system analysts in incorporating the users' cognitive styles differences into information systems design and some problems are indicated which could arise during implementation. Finally, experimental design factors are outlined for improving research into the cognitive styles area.
161 citations
TL;DR: Examples from a case-oriented survey of fifty-six decision support systems are cited to illustrate each of four implementation patterns that were observed in the sample, each of which has its own purpose and dynamics.
Abstract: Examples from a case-oriented survey of fifty-six decision support systems are cited to illustrate each of four implementation patterns that were observed in the sample. These four system development patterns are defined in terms of high or low degrees of (1) initiation by the user and (2) participation in the development process. A surprising finding is that systems initiated by users and implemented with their active participation account for less than one fourth of all cases. A qualitative analysis of the cases explains this finding by interpreting the four patterns in terms of six frequently observed system development situations, each of which has its own purpose and dynamics. Categorizing these situations under the headings "built for," "sold to," or "forced upon," key questions and concerns for various stakeholders in system development efforts are cited. A concluding quandary for management involves the choice of a project portfolio that is neither too risky nor too safe.
79 citations
TL;DR: This article suggests some alternative approaches and points out the need for new tools in the development of computer-based system replacement systems.
Abstract: Developing and installing a computer-based system in an organization can have major impacts on tasks performed by participants in that organization. In recent years, an increasing share of systems development effort has been directed toward system to support managerial decision-making. These systems require a far greater degree of individual change than did earlier, clerical replacement systems. Successful implementation often requires changes in the users' views of their jobs. The demands that these systems place on the implementation process cause many standard development approaches to be inadequate. This article suggests some alternative approaches and points out the need for new tools.
49 citations
TL;DR: This paper presents an example of an unsuccessful information systems development and the development failure is analyzed in case form, defined by nonuse of the system for its intended obiective and an exodus of key systems developers.
Abstract: This paper presents an example of an unsuccessful information systems development. The development failure is analyzed in case form, defined by nonuse of the system for its intended obiective and an exodus of key systems developers. Organizational deficiencies in the area of proiect planning and control are highlighted. Practitioners and academics can benefit from the analysis and avoid similar pitfalls in their own work by sharing these experiences.
49 citations
TL;DR: A framework for the classification of document-based information systems for use within a management context is developed, and the results of a literature survey undertaken to identify illustrative examples and to classify them according to the framework developed are reported.
Abstract: The role of document-based information systems in management has been relatively neglected. However, during the last few years, a certain number of document-based systems for use within a management context have been reported in the literature. A framework for the classification of these systems is developed here, and the results of a literature survey undertaken to identify illustrative examples, and to classify them according to the framework developed, are reported. Twenty-two illustrative systems are identified, described, and classified along two major lines of development. The convergence and integration of data and document processing techniques in support of management planning and control is also discussed.
45 citations
TL;DR: A set of the most fundamental principles that have emerged in the field to guide development information systems in organizations are identified, including such important areas as data management, data independence, and information system structure.
Abstract: This article draws together and examines research findings and practical industrial experiences related to computer-based information systems. Its purpose is to identify a set of the most fundamental principles that have emerged in the field to guide development information systems in organizations. It also presents a foundation from which further research efforts can be launched. The characteristics of computer-based information systems are examined as background. Technical and developmental principles are then examined, including such important areas as data management, data independence, and information system structure. Behavioral and organizational principles are discussed next, encompassing resistance to systems, user and management involvement in development activities, and integration of systems into the organization. Finally, the question of "where do we go from here" is raised to point out areas needing continued research and development.
34 citations
TL;DR: The development of useful and satisfactory computer-based information systems requires a good working relationship between the user and the analyst, but this relationship frequently is threatened by ineffective systems work.
Abstract: The development of useful and satisfactory computer-based information systems requires a good working relationship between the user and the analyst However, it appears that this relationship frequently is threatened by ineffective systems work It is caused by a set of perceptions and assumptions that users and analysts make which lead to dissatisfaction with the analyst This article explores some of the reasons for failures and shortcomings as well as insights into what can be done to improve the situation
32 citations
TL;DR: This article presents some general ideas on how various aspects of the sytems development life cycle might be measured as one means of assessing and controlling the quality of a system.
Abstract: This article presents some general ideas on how various aspects of the sytems development life cycle might be measured as one means of assessing and controlling the quality of a system. We feel that this is a fruitful area for research with potentially important industrial and research implications. We strongly urge further research and investigation into systems development quality control based on the framework established in this article.
TL;DR: A model which has been developed by industrial psychologists is designed to be used by managers to help them select the most appropriate decision-making process given a particular set of relevant circumstances.
Abstract: Research in the behavioral sciences has generally been finding that managers can be more effective by adapting their leadership style (i.e., the decision-making process) to fit the circumstances surrounding the decision to be made. This describes a model which has been developed by industrial psychologists. This model is designed to be used by managers to help them select the most appropriate decision-making process given a particular set of relevant circumstances. The model consists of a set of five decision-making processes, a set of simple questions managers can use to assess the circumstances surrounding their decision situations, and a procedure to help managers to choose among the alternative decision-making processes. It is proposed that this model can be useful in helping MIS project team leaders improve their teams' decision-making processes. To illustrate its usefulness, the model is applied to several decision problems facing a hypothetical MIS project team leader.
TL;DR: This article integrates recent literature with the authors' survey in an attempt to explain more precisely the potential role(s) of the internal auditor in the systems development process.
Abstract: The internal auditor's role during the design phase of an EDP application is unclear in many organizations. This article integrates recent literature with the authors' survey in an attempt to explain more precisely the potential role(s) of the internal auditor in the systems development process.
In practice, four roles appear to exist. In the order of their importance, they are: (1) audit of control adequacy, (2) audit of design process, (3) auditor as a user of the application, and (4) auditor participant in the design process. The rank ordering of these roles in practice is explainable in terms of three constraints upon internal audit involvement during the design phase. The identified constraints are those of audit approach, audit independence, and management objectives.
Although EDP manager reaction to internal audit involvement is generally favorable, it could be stronger. Upgrading of internal auditor expertise in EDP systems appears to be the key to improved acceptance.
Finally, the potential contribution to the MIS manager of internal audit involvement is noted, and means of constructive interaction are suggested.
TL;DR: The need for giving authority commensurate with the level of responsibility to attain success is stressed, which is essential for system projects to work.
Abstract: There are many theories on how to handle the implementation of data processing techniques. There are many more reasons why system projects do not work. This article stresses the need for giving authority commensurate with the level of responsibility to attain success.
TL;DR: Some of the psychological background of problem solving and group interaction is investigated, and a conceptual model is described to assist in harnessing and directing the authors' latent creative energy.
Abstract: Solutions to data processing design problems involve using a wide range of sophisticated technical tools. One way of more effectively using these tools is to further develop the human problem solving process by bringing together talented individuals and providing an atmosphere conducive to group interaction.
This article investigates some of the psychological background of problem solving and group interaction, and describes a conceptual model to assist in harnessing and directing our latent creative energy.
TL;DR: The background and development of TCR is described, as a vital part of its international distributed processing network, a worldwide corporate MIS called the Total Customer Relationship system, which provides management with easily accessible, comprehensive information on dealings with mUlti-national corporate customers around the world.
Abstract: The rapid growth of international banking in recent years has been accompanied by the growing problem of how to control the flow of vital management information, both customer and financial. The First of Boston's answer to this problem has been to develop, as a vital part of its international distributed processing network, a worldwide corporate MIS called the Total Customer Relationship system (TCR). TCR provides management with easily accessible, comprehensive information on dealings with mUlti-national corporate customers around the world. This article describes the background and development of TCR, as well as the consolidated reports produced by the system.
TL;DR: A mathematical model is presented which enables the evaluation of dollar assessments for reliability and maintenance of computer equipment and should help users to realistically negotiate vendor contracts that assure equipment performance.
Abstract: A mathematical model is presented which enables the evaluation of dollar assessments for reliability and maintenance of computer equipment. This cost model should help users to realistically negotiate vendor contracts that assure equipment performance. Alternatively, this framework may help the customer to achieve compensation if performance is not within satisfactory limits.