Showing papers in "Information & Management in 1988"
••
TL;DR: The study shows that systems analysts' perceptions of information system failures can be largely accounted for by their professional and structural position in the systems development process and associated interests, which supports the view that a perception of IS failure is largely stakeholder-dependent.
212 citations
••
TL;DR: A content analysis of fourteen published cases showed the importance of an organization's existing systems in the use of information technology for competitive advantage, but there was little support for the literature's assertions that competitive pressure is a key factor motivating strategic uses of IT.
170 citations
••
TL;DR: Key human resource issues in IS for the 1990s were identified by separate Delphi studies of IS executives and human resource executives in Fortune 500 firms, however ranking differed considerably.
74 citations
••
TL;DR: It was found that end-users were more satisfied with their microcom computing activities when (1) the organizational microcomputing plan was incorporated in the information systems master plan, (2) there was an information center to support end-user activity and, (3) users had access to a hot-line to solve theirmicrocomputing problems.
70 citations
••
TL;DR: In-depth interviews with eighteen MIS practitioners produced numerous examples of these games and confirmed that practitioners can recognize them during MIS development and implementation and provided some practical implications for MIS professionals who know that they must face the political machinations within their organizations but do not necessarily know how to recognize them.
63 citations
••
TL;DR: Since many information systems are expensive, offer scale advantages, and are available to all members of an industry, cooperation through consortium development may make more sense than competition.
62 citations
••
TL;DR: A synopsis of research on the characteristics and culture of Chinese business methods is used as the basis for developing insights into the cultural aspects of information in Information Systems and Decision Support Systems.
60 citations
••
TL;DR: The motivation for integrated support in the production of software is analyzed, the history of environments for software development is reviewed, and the context for describing current research trends is provided.
50 citations
••
TL;DR: Evidence is presented that systems analysts attitudes vary considerably and although some of them have a technical orientation, others emphasize the behavioral and socio-political aspects of development.
43 citations
••
TL;DR: Competitive information systems appear as a more complex phenomenon than is generally proposed and their use in a competitive industry seems to be characterized more by a number of small interactive moves than one sustainable competitive breakthrough.
38 citations
••
TL;DR: An experiment was used to compare the impact of two very different communication modes during task-oriented group decision making activities using either face-to-face (simultaneous) or computer conferencing (nonsimultaneously) communication modes.
••
TL;DR: This paper proposes a framework for the integration of prototyping into structured system development, based on a new unified approach to the analysis and design phases.
••
TL;DR: The information reported here include: when computer systems were first introduced, the current applications, makes of systems, system development languages used, the size of the IS department, and its locations in the organization.
••
TL;DR: A case example of an inter-organizational system is being presented and the benefits that could be obtained from this prototype system and its descendants are discussed.
••
TL;DR: The growing use of microcomputers in the small business sector and the implications of these results for educators, equipment vendors, and researchers are discussed.
••
TL;DR: Implementation experiences with a particular methodology in different environments discussed here demonstrates that equivocality resolution during the implementation process is critical to realizing improved productivity.
••
TL;DR: Information Resource Management (IRM) as mentioned in this paper is an organizing framework for information practices that is based on the assumption that organizations are systems amenable to systematic control, and that information is a resource that can be managed in economically efficient ways.
••
TL;DR: It was discovered that, while computer managers are receptive toward this new tool, most have no definite plans to develop expert systems in the near future, which seems to be in conflict with other evidence about the growing numbers of Expert systems in business applications.
••
TL;DR: This work recommends the use of the graphical cost-benefit approach in conjunction with a cost transformation based on the utility model, which allows incorporation of risk and uncertainty consideration into the selection process.
••
TL;DR: Results of the study indicate that firms using structured systems design and programming techniques expended twice as much effort to implement the TEFRA requirements as those using non-structured approaches.
••
TL;DR: It is shown that a structured information exchange between the two is necessary if the required searches are to be completed and profit maximization achieved.
••
TL;DR: DS users see a strong positive correlation between their training and the use of a DSS to improve decision making, and significant relationships were also noted between perceptions of training and task structure differences.
••
TL;DR: The results indicate that five factors significantly affect the existence and selection of coordination mechanisms in IRM and create a need for an official IRM function as a coordination mechanism.
••
TL;DR: The issues related to application of expert systems in a small business are reviewed and their capabilities and limitations are discussed.
••
TL;DR: Research from a quasi-experimental investigation using actual system development projects shows that the two most important factors in a feasibility study are convincing the users that the system they get will actually meet their functional requirements, and also that thesystem will work effectively within the organizational environment.
••
TL;DR: The results indicated that project managers made a clear distinction between the types of projects that are appropriate for development using procedural languages and 4GL's.
••
TL;DR: It is recommended that the IS managers should critically re-evaluate and adjust their EUC strategies: an IC alone does not guarantee any success.
••
TL;DR: It is found that use decreases with ascending rank in an organization, but that use of office automation is made at all levels, and the ratio of applications used is surprisingly similar at all Levels.
••
TL;DR: Current practice in the introduction and management of LANs is investigated, including managers' perceptions of the benefits and drawbacks of the LAN, its perceived impact on users, justifying LANs to management, and the significant issues facing network managers in implementing LANs.
••
TL;DR: It is shown that a number of features facilitate building genuine DSS's, including the traditionally built DSS, the MIS prototype, and the spurious DSS.