scispace - formally typeset
Search or ask a question

Showing papers in "Management Information Systems Quarterly in 1984"


Journal ArticleDOI
TL;DR: Three major issues in the design of group decision support systems are focused on: 1) system capabilities, 2) system delivery modes, and 3) system design strategies, and the relationship of these issues to system use and survival is discussed.
Abstract: This paper deals with a number of issues pertinent to the design of group decision support systems. It notes that the need for such systems, whether designed by users or vendors, is a consequence of the clash of two important forces: (1) the environmentally-imposed demand for more information sharing in organizations, and (2) the resistance to allocating more managerial and professional time to attending meetings. The paper focuses on three major issues in the design of these systems: 1) system capabilities, 2) system delivery modes, and 3) system design strategies, and discusses the relationship of these issues to system use and survival. The relevance of numeric information, textual information, and relational information in a decision-group context are examined, and various system capabilities for displaying and using such information are noted.

543 citations


Journal ArticleDOI
TL;DR: A Delphi study, using leading information systems professionals, was used to identify and rank ten key IS management issues for the 1980's, and the number one issue identified was improved IS planning, followed by facilitation and management of end user computing.
Abstract: Knowledge of the most important issues in the information systems field would help focus research and educational efforts. A Delphi study, using leading information systems (IS) professionals, was used to identify and rank ten key IS management issues for the 1980's. Measures were also taken to the amount of agreement achieved on these issues and rankings. The number one issue identified was improved IS planning, followed by facilitation and management of end user computing. This article describes the research approach involved and discusses the results.

393 citations


Journal ArticleDOI
TL;DR: From the political perspective, elements of the system design process can be interpreted as rituals which enable actors to remain overtly rational while negotiating to achieve private interests and this paper seeks to understand those rituals and to reveal their function in the systems design process.
Abstract: Developing computer-based information systems is usually conceived as a rational process, intended to achieve identifiable and agreed upon goals. From this perspective, certain elements in the system development process are believed to enhance its effectiveness. For example, handoffs between one project phase and another, feasibility studies conducted prior to development work, and the use of project teams and steering committees are recommended in most texts as activities instrumental to effective system design. Recently, the political view of organizations has assumed greater stature in organization theory. This perspective interprets organizational events not only from the rational standpoint, but also in terms of negotiation and conflicting goals. From the political perspective, elements of the system design process can be interpreted as rituals which enable actors to remain overtly rational while negotiating to achieve private interests. This paper seeks to understand those rituals and to reveal their function in the systems design process.

243 citations


Journal ArticleDOI
TL;DR: It is hypothesized that certain aspects of relationships with co-workers, project leaders, and users will also be significant correlates of job satisfaction and that the addition of role and leadership variables to job characteristics significantly increases the explained variance in job satisfaction.
Abstract: In the past, research examining the work-related correlates of job satisfaction in programmer/analysts has focused on the relationship between characteristics of the job itself and job satisfaction. It is hypothesized that certain aspects of relationships with co-workers, project leaders, and users will also be significant correlates of job satisfaction. Specifically, the relationship between job satisfaction, role conflict, role ambiguity, and quality of leadership provided by supervisors and peers is examined. A questionnaire measuring job characteristics, role conflict and ambiguity, leadership characteristics, and job satisfaction was administered to 118 programmer/analysts at four companies. The results indicate that both role and leadership variables correlated at least as highly with job satisfaction as job characteristics and that the addition of role and leadership variables to job characteristics significantly increases the explained variance in job satisfaction.

165 citations


Journal ArticleDOI
TL;DR: The evolving nature of information systems activities is discussed, a variety of alternative designs for organizing these activities are introduced, and some prototypal designs are presented.
Abstract: A number of recent articles have concluded that changes must occur in the manner information systems activities are organized This article discusses the evolving nature of information systems activities, introduces a variety of alternative designs for organizing these activities, and presents some prototypal designs Then, the implications to information systems managers of movement toward these new organizational forms are discussed The article concludes with a discussion of some of the critical tasks to be undertaken by information systems managers and researches in order that this transition toward and end user domination of many information systems activities can be successfully negotiated

142 citations


Journal ArticleDOI
TL;DR: In this article, the benefits of computer-based applications for data processing departments are considered, and the authors find that in no instances were these factors cited by senior data processing managers as primary success considerations.
Abstract: User development of computer-based applications (UDA) is a new phenomenon in organizations, and can provide benefits for both users and data processing departments. The benefits of UDA for DP departments are considered in this article. The UDA literature suggests that DP departments can expect to receive two major types of benefits: a decrease in the backlog of DP application development projects in the proportion of DP resources spent on application maintenance. However, this study, which was carried out in ten large Canadian business firms, found that in no instances were these factors cited by senior DP managers as primary success considerations.

117 citations


Journal ArticleDOI
TL;DR: Results are presented from an in-depth survey of users of 34 different DSS to show that the tasks performed most ineffectively in DSS development are planning, assessment of user needs, and system evaluation.
Abstract: Traditional project management and design methods used for data processing and MIS applications are ill-suited to decision support systems (DSS). The authors argue that effective management of DSS development requires: a) An explicit plan for the full development life cycle; b) Careful assignment of responsibility for DSS development; c) Appropriate user involvement and direction; and d) On-going user needs assessment and problem diagnosis A 13-stage tactical plan for DSS development, called the DSS development life cycle, is described. Results are presented from an in-depth survey of users of 34 different DSS to show that the tasks performed most ineffectively in DSS development are planning, assessment of user needs, and system evaluation. Results from the survey are also presented that show the factors responsible for DSS project approval, and the factors responsible for DSS success.

112 citations


Journal ArticleDOI
TL;DR: The nature of changes in management information technologies in the past half decade and their impact on a particular organization within the General Motors family are articulated.
Abstract: Advancements in management information technologies in the past half decade are bringing to organizations forms and functions unanticipated even a few years ago. The revolution in personal communication and computation power is changing organizational roles and tasks and is offering increased effectiveness and productivity to organizational designers who choose to take advantage of technological innovations. This article articulates the nature of those changes and their impact on a particular organization within the General Motors family.

108 citations


Journal ArticleDOI
TL;DR: This research focuses on evaluating the systems development activities of two MIS project teams, indicating a void of certain personality styles in project team one andRecommendations are made for assembling project teams based on these findings.
Abstract: A profusion of technology is insufficient to implement effective computer systems without the full utilization of human resources to develop such systems. The issue of fully developing and utilizing available human resources is currently receiving careful scrutiny in the MIS literature. One methodology for fully utilizing human resources has been maximizing productivity by stressing team effort. This research focuses on evaluating the systems development activities of two MIS project teams. Empirical evidence was gathered from interviews with MIS personnel and key users concerning strengths/weaknesses of the two project teams. Analysis was performed to determine the personality characteristics (as measured by the Myers-Briggs Type Indicator) of the MIS staff. The results of this analysis indicated a void of certain personality styles in project team one. This void correlated with weaknesses ascertained from the interview data for project team one. Project team two, with all four personality types represented, was evaluated as very successful. Recommendations are made for assembling project teams based on these findings.

101 citations


Journal ArticleDOI
TL;DR: Differences in the nature of development projects should affect the planning of the Information Systems Development Life Cycle, and a practical approach to ISDLC planning is suggested based on a structured procedure and a number of working forms.
Abstract: The Information Systems Development Life Cycle (ISDLC) is usually treated as a rigid sequence of activities This article asserts that differences in the nature of development projects should affect the planning of the ISDLC Two classes of factors affecting the ISDLC are identified: factors relating to the environment and factors relating to the development effort (eg in-house development vs canned software package) Each step along the ISDLC is decomposed into several dimensions relating to the activities that should be performed, the degree of control that should be exerted, to human resources, to other resources, and to the time factor The relationship between the six dimensions and the two classes of factors are explained Finally, a practical approach to ISDLC planning is suggested based on a structured procedure and a number of working forms It assists in preliminary planning of the development process as well as in periodic reviews and revisions whenever the project reaches a certain milestone

84 citations


Journal ArticleDOI
TL;DR: A tentative model of the dimensions affecting user involvement in the creation of a DSS is hypothesized and refined in light of the three case studies presented.
Abstract: Many authors have stressed that DSS development requires a high level of user involvement. Three DSS case studies are presented which illustrate that the level of user involvement can vary considerably. Based upon the existing literature, a tentative model of the dimensions affecting user involvement in the creation of a DSS is hypothesized. This model is then refined in light of the three case studies presented.

Journal ArticleDOI
D. H. Drury1
TL;DR: The empirical study described in this article examines the actual practices of companies in utilizing steering committees and indicates that some major structural and operating alternatives lead to maximizing steering committee benefits whereas others do not.
Abstract: One approach to plan and control data processing functions is to use a steering committee. This committee, composed of user, top management, and data processing representatives, is intended to bring a broad perspective to focus on systems issues. The empirical study described in this article examines the actual practices of companies in utilizing steering committees. Committee benefits are statistically tested. The results indicate that some major structural and operating alternatives lead to maximizing steering committee benefits whereas others do not. The article closes with an evaluation of the alternatives and the consequent strategies for using steering committees effectively.

Journal ArticleDOI
TL;DR: In this article, a set of dimensions which support the comparative examination of analysis methods are presented to clarify their similarities and differences, and a comparison technique supports professionals in the combination of tools to ensure complete analysis products.
Abstract: Though many analysis tools and techniques are available to systems professionals, none of them completely support the analysis process. Traditional techniques tend to clarify input and output detail, along with physical information flows. More current techniques tend to concentrate on considerations of system structure. This paper presents a set of dimensions which support the comparative examination of analysis methods. A number of methods are compared to clarify their similarities and differences. The comparison technique supports professionals in the combination of tools to ensure complete analysis products.

Journal ArticleDOI
TL;DR: It is argued that information systems maintenance is a more complex and integrated task that portrayed in the literature, which involves not only the maintenance of the applications software, but also all the other elements in an operational system.
Abstract: This article argues that information systems maintenance is a more complex and integrated task that portrayed in the literature It involves not only the maintenance of the applications software, but also all the other elements in an operational system The literature relating to the maintenance of each element is reviewed to reveal substantial underdevelopment in some areas and fragmentation between elements The present practice of focusing upon the maintenance of particular individual elements is criticized and a new focus upon changes in the information inputs to the systems development process is proposed Alternative methods of managing the maintenance operation are examined and the implications of these methods in terms of designing the procedures, staffing the maintenance function, and the need for communication are discussed

Journal ArticleDOI
TL;DR: The results show that firms are using intelligent terminals, satellites, microwave, local area networks, etc., and they are using these technologies for electronic mail, decision support system activities, and limited use of video teleconferencing.
Abstract: This paper presents results obtained from a survey of major business firms in a la rge metropolitan area done as part of a telecommunications systems research project. The goal of this study involved determining the telecommunication technologies and services currently used by business firms. The results show that firms are using intelligent terminals, satellites, microwave, local area networks, etc., and they are using these technologies for electronic mail, decision support system activities, and limited use of video teleconferencing. Information resource management in most of these firms is centralized. Hands-on use of terminals by managers and professional does not appear as widespread as commonly publicized to date.

Journal ArticleDOI
TL;DR: The authors argue that DSS language evaluation and selection should be a multi-step process involving most, if not all of the following: End User Needs Assessment and Problem Diagnosis, Feature Analysis and Capability Review, and Programmer Productivity and End User Orientation Analysis.
Abstract: Today managers and policy makers are confronted with an overwhelming range of choices of computer software to develop decision support systems (DSS). The authors argue that DSS language evaluation and selection should be a multi-step process involving most, if not all of the following: 1. End User Needs Assessment and Problem Diagnosis 2. Critical Success Factor Identification 3. Feature Analysis and Capability Review 4. Demonstration Prototype Development 5. External User Surveys 6. Benchmark and Simulation Tests 7. Programmer Productivity and End User Orientation Analysis The objectives of each of these activities are described, as well as specific procedures for accomplishing them. In addition, the authors discuss the usefulness of a multi-disciplinary task force to accomplish the DSS language evaluation and selection process.

Journal ArticleDOI
TL;DR: This methodology must be amended to include a strong requirement for technical architecture at the start, and for thorough systems testing at the finish.
Abstract: Many distributed information processing systems will fail because of people and organizational problems ᾢ not technical problems. These problems can be addressed by careful skill and organizational planning, by added attention to training, and by an enhanced project management methodology. This methodology must be amended to include a strong requirement for technical architecture at the start, and for thorough systems testing at the finish. Distributed systems are more complex and, to be successful, will require more work and mod expertise in the central systems staff, not less. Economies of scale will keep most of the work and expertise within the central staff.

Journal ArticleDOI
TL;DR: This article presents a systematic methodology for requirements analysis in database design by means of a diagram that depicts any temporal or causal relationships, as well as logical operators, that maybe present in the process underlying the activity.
Abstract: This article presents a systematic methodology for requirements analysis in database design. The procedure begins with an interview with the user/decision maker. The responses collected during the interview are analyzed to represent, by means of a diagram, the data and processing requirements for the activity under consideration. The diagram uses two fundamental constructs, events and states, as building blocks. It depicts any temporal or causal relationships, as well as logical operators, that maybe present in the process underlying the activity. The representation is compact and easy to follow. An experimental study is described to illustrate the applicability of the methodology.

Journal ArticleDOI
TL;DR: This paper looks at recent literature regarding decision model deficiencies, evaluates selected financial simulation model packages, and suggests design needs for expanding the use of decision models to a broader range of firms.
Abstract: Computer design models often provide useful results as management planning tools. However, these tools are frequently limited to firms with staffs of specialists who can assimilate the technical nature of the models. For other firms, the success of decision models such as simulation have not been demonstrated. This paper looks at recent literature regarding decision model deficiencies, evaluates selected financial simulation model packages, and suggests design needs for expanding the use of decision models to a broader range of firms.


Journal ArticleDOI
TL;DR: Requirements, Needs, and Priorities (RNP) combines the more effective concepts of CSF, BSP, and ATT with the traditional requirements analysis while minimizing the time and effort required to reach project definition.
Abstract: Critical Success Factors (CSF), Application Transfer Team (ATT), Business Systems Planning (BS), and Executive Application Survey (EAS) are some of the more highly publicized methods used to perform requirements definition for information systems. A key element in these techniques, and often the most difficult to secure, is the total manpower commitment required to perform them correctly. These analysis methods are attractive to management, but we have not always been successful in selling those approaches to senior executives due to the time commitments they require. Requirements, Needs, and Priorities (RNP) combines the more effective concepts of CSF, BSP, and ATT with the traditional requirements analysis while minimizing the time and effort required to reach project definition. The objective is to bring executive recognition of MIS need from a maybe perspective to one of definite yes or no. This article will describe the RNP procedure and explain the components for successfully executing a study.