Gordon B. Davis

User acceptance of information technology: toward a unified view

Information technology (IT) acceptance research has yielded many competing models, each with different sets of acceptance determinants. In this paper, we (1) review user acceptance literature and discuss eight prominent models, (2) empirically compare the eight models and their extensions, (3) formulate a unified model that integrates elements across the eight models, and (4) empirically validate the unified model. The eight models reviewed are the theory of reasoned action, the technology acceptance model, the motivational model, the theory of planned behavior, a model combining the technology acceptance model and the theory of planned behavior, the model of PC utilization, the innovation diffusion theory, and the social cognitive theory. Using data from four organizations over a six-month period with three points of measurement, the eight models explained between 17 percent and 53 percent of the variance in user intentions to use information technology. Next, a unified model, called the Unified Theory of Acceptance and Use of Technology (UTAUT), was formulated, with four core determinants of intention and usage, and up to four moderators of key relationships. UTAUT was then tested using the original data and found to outperform the eight individual models (adjusted R2 of 69 percent). UTAUT was then confirmed with data from two new organizations with similar results (adjusted R2 of 70 percent). UTAUT thus provides a useful tool for managers needing to assess the likelihood of success for new technology introductions and helps them understand the drivers of acceptance in order to proactively design interventions (including training, marketing, etc.) targeted at populations of users that may be less inclined to adopt and use new systems. The paper also makes several recommendations for future research including developing a deeper understanding of the dynamic influences studied here, refining measurement of the core constructs used in UTAUT, and understanding the organizational outcomes associated with new technology use.

Anytime/anyplace computing and the future of knowledge work

Considering the implications and consequences of the always-connected lifestyle.

Information systems curriculum recommendations for the 80s: undergraduate and graduate programs

The recommendations of the 1972 and 1973 ACM Curriculum Committee on Information Systems programs have been influential in the development of degree programs at the bachelors, masters, and doctoral levels. The earlier curriculum has been revised and updated based on advances in the field over the past nine years. The report discusses the continuing need for education related to the definition, analysis, design, construction, and management of information systems in organizations. The structure of both bachelors and masters level programs are described and courses are defined. Course outlines include rationale for the courase, course objectives, instructional modes, and a list of topics. Each topic is weighted in terms of suggested percent of time devoted to the subject.

IS '95: guidelines for undergraduate IS curriculum

This paper provides an overview report of the first joint curriculum development effort for undergraduate programs in information systems. The curriculum recommendations are a collaborative effort of the following organizations: ACM, AIS, DPMA, and ICIS. After a summary of the objectives and rationale for the curriculum, the curriculum model is described. Input and output attributes of graduates are delineated. Resource requirements for effective IS programs are then identified. Lastly, there is a proposal for maintaining currency of the curriculum through electronic media.

Diagnosis of an information system failure

Abstract In diagnosing an episode of information system application failure, the IS professional and others doing the analysis face two challenges: (1) relevant data must be identified, collected, and organized; and (2) the data must be analyzed and interpreted to form a coherent picture of the perspectives, actions, and events which resulted in the troubled or failed system. This article provides a diagnostic framework and interpretive process for performing a diagnosis. The premise underlying the diagnostic framework is that an information system is a social system has uses information technology. The social and technical dimensions in the diagnosis of an information system are represented in a two-dimensional framework. Once the data and comments about the failure have been organized in the framework, the process of interpretation follows procedures based on interpretive methods (hermeneutics). The framework and associated interpretive process assist those doing a diagnosis in applying two powerful bodies of knowledge to failure diagnosis — socio-technical systems and interpretive methods. The article describes the framework and interpretive process, explains the rationale for them, and demonstrates their use for a case situation.

Three stage model of MIS planning

Abstract Planning an information system that will meet the information needs of an organization is a difficult task. Thr process of formulating the plan is not well-defined in the information system literature. This article proposes a three-stage model for planning the Management Information System (MIS). The three stages are strategic MIS planning, organizational information requirements analysis, and resource allocation. This model clarifies many ill-defined issues of MIS planning. Several methodologies that have been proposed for MIS planning are surveyed and classified to the stage of the MIS planning model in which they are useful. Recommendations are made for applying the model.

Can humans detect errors in data? Impact of base rates, incentives, and goals

There is strong evidence that data items stored in organizational databases have a significant rate of errors. If undetected in use, those errors in stored data may significantly affect business outcomes. Published research suggests that users of information systems ~Robert Zmud was the accepting senior editor for this paper. ISRL Categories: AD05, BG03, HC0201

Information Systems Conceptual Foundations: Looking Backward and Forward

The academic field of information systems has developed because organizations use a specialized body of knowledge about information and communications systems. Teaching and research support these organization needs. The field may be defined in terms of observed information systems in organizations and also in terms of the function or field of activity for system planning, development, management, and evaluation. Since the systems deal with capture, repositories, processing, and communication of data, information, and knowledge, these are also defined.

Determining management information needs: a comparison of methods

This paper reports on a comparison of the decision analysis (topdown) and data analysis (bottom-up) methods for determining management information needs in the preparation of management-oriented information system applications. Information requirements were developed using the two alternative methods for four decisions in each of four small colleges. The information requirements obtained by the two methods were evaluated by the college executives as to value and other attributes. The results indicate: l. The methods perform better in some functional areas (e.g ., administrative) than in others (e.g ., academic). 2. The type of decision, programmed or nonprogrammed, affected the value and attributes of information obtained. The decision analysis approach provided a higher valued set of information requirements for programmed decisions than data analysis;for relatively nonprogrammed decisions. both methods were about equal in providing information requirements. The value and attributes assigned to the information requirements were higher for programmed decisions than for nonprogrammed decisions. 3. Information analysis techniques cannot be considered apart from organizational contexts in which they are to be applied.

Determining information requirements: A contingency method for selection of a requirements assurance strategy

If the information requirements for an information system application can be established accurately and completely and then documented clearly and unambiguously, there is a high probability that the application can be successfully designed and implemented. Information requirements determination consists of two major processes: 1.(1) eliciting requirements and 2.(2) requirements assurance. Many techniques, procedures, and methodologies have been proposed for these two processes. This paper describes the selection of a strategy for information requirements assurance. Selection of the appropriate strategy depends on environmental and project contingencies. Contingencies determine the level of uncertainty to be resolved in order to ensure an accurate and complete statement of information requirements. Based on the level of uncertainty, the strategy for assurance may be to accept the requirements as stated or to follow either a linear, iterative, or experimental assurance process. The approach to strategy selection is illustrated by a contingency analysis worksheet for evaluating requirements uncertainty and by examples.