Evolution Of Information Systems Research Articles

The evolution of a management information system in an outpatient mental health institute

To promote greater accountability, supervisors in mental health facilities will be required to monitor the activities of their organizations. The Outpatient Division of the Texas Research Institute of Mental Sciences has developed an administrative accounting based on management by objectives. The authors present the evolution, philosophy, and format of the system. The management style compatible with the system is also described.

Data structures and accessing in data-base systems, I: Evolution of information systems

The attention of the computer user community is increasingly focusing on data bases and computerized information systems because of two converging trends. Computerized information systems are coming to play an essential role in business operations, and the hardware and software technology for supporting information systems is in a period of rapid technical progress. In spite of this attention, there is still little common agreement as to what information systems are, the functions they perform, and — from a technical point of view -how they should be designed, implemented, installed, and used. These conditions arise naturally from the newness of the field and the ad hoc nature of existing Computerized implementations. A compounding factor is the wide variety of perspectives of those who discuss information systems — for example, the executive, the management consultant, the systems analyst, the mathematician, and the systems programmer. In this paper, we emphasize aspects of information systems that are of importance to systems analysts, systems designers, and implementors.

A Kernel System for information system development, evolution, and operation

We believe that the current boundaries and distinctions between operating systems, data base management systems (both “host language” and “self-contained”), programming language processors (both interpretive and compiled), programming support systems (library management, testing, and integration services), instructional systems, and certain other generalized data processing services, can and should be eliminated. That is, we believe that all these seemingly separate functions, which are currently separate for historical reasons as much as any other, can and should be addressed by a single integrated (but subsettable) “Kernel System”. We also believe that with the proper system architecture and implementation techniques (e.g., top-down and structured programming) and with the wholesale elimination of duplicated functions, a Kernel System can be built that would address the sum total of these functions and, at the same time, remain comparable in size and complexity to a typical self-contained data base management system alone. Further, such a structured Kernel System would be much better able to support the development, continued evolution, and operation of both itself and its applications.