Showing papers on "Data management published in 1972"

The Knowledge Utilization Process in Management and Organization

Abstract: This article deals with the knowledge utilization process in management and organization and relates the concepts of knowledge flow to management education and development. Primary attention is giv...

A Tutorial on Data-Base Organization

Abstract: The purpose of this report is to clarify certain issues of data-base support. The main issues are data independence, security, integrity, search, and the integrated data base. The first section of the report is an introduction, which includes data-management history, trends, and terminology. The second section presents a theory of operational data based on the notions of entity sets and data maps. The third section is an exposition of data-bank design, emphasizing structure, search, and maintenance. The fourth section shows why data independence is a necessary feature of a viable data base system. The report should not be construed as representing a commitment or intention of IBM. The opinions expressed are personal and do not represent a corporate position. The intent of the report is tutorial, and the viewpoint is that of a systems programmer. Data independence Integrated data base Data integrity Search Data management Systems programming Data security 21 Programming

On the Impact of Management Science

Abstract: This article, based on a general-purpose citation indexing system for business periodicals, examines the degree to which TIMS and its publication, Management Science, have carried out the Institute's stated mission; namely, to identify, extend and unify scientific knowledge pertaining to management. The primary objective of the citation index is to illustrate Management Science's value-in-use to researchers in management and other business-related disciplines.

Implications of data independence on the architecture of database management systems

Abstract: Data independence is a relatively new concept in database management technology. In essence, the objective of data independence is the insulation of application programs from the underlying database management system. The remarkably widespread appreciation for the notion is in part a result of the vigorous discussion generated by the reports of the Data Base Task Group of CODASYL and the Joint GUIDE-SHARE Data Base Requirements Group. While the pros and cons have been discussed at some length, very little has been written or spoken on the implications of data independence on the architecture of database management systems. It is the purpose of this paper to identify and elaborate on some of the problems associated with the design of a data-independent system.

A system for large econometric models—management, estimation, and simulation

Abstract: A software system to build econometric models that have nonlinear relations requiring simultaneous solution is described. The system is presented in the context of a Canadian government research project that constructed a model of almost 1,600 equations. The system, which is designed to exploit the modular nature of the modelling process, contains programs that assist in the tasks of data management, estimation, solution, analysis, and reporting. Programs are provided to facilitate documentation of the model and error checking at the critical decision points of the model building process. Inputs of researchers generally are in the language familiar to economists and other social scientists, and little training has been required to integrate new researchers into the Canadian project. All parts of the system, which is fully documented, are operational. Some programs are operational on several systems.

System requirements analysis: A management tool

Abstract: Most of the equipment performance and data problems experienced on recent aerospace programs suggest inadequate consideration of performance and data requirements and the absence of a discipline to assure complete definition of system hardware and software elements. A system requirements analysis (SRA) technique is described which is a discipline for complete system definition and also provides a medium for effective program management. To demonstrate by example how this SRA technique provides thorough consideration of all program objectives, data management is considered as a unique system element relative to its influence on the definition of operational equipment and procedures. This includes assumption of scientific data objectives, as initiated by a principal investigator (PI).

Computer-Assisted Planning

Abstract: : The document reports results of applied research in four task areas: Computation and Communication Trade-Off Studies (CACTOS); vocal English data management; on-line graphic computation; and systems research and networking Work in these areas was directed toward the development of prototype facilities for a computer-assisted planning system These facilities include a computer- network modeling system (the CACTOS model); systems for man-machine communication and data management via speech, ordinary English, and data-tablet graphics; and an initial facility for data-sharing among existing data management systems within a computer network The work has also involved the continuing evolution of a sophisticated time-sharing system (ADEPT/ICOS) and the implementation of protocols for communication with other Hosts over the ARPA network

Information systems for management

Abstract: Deriving Long-Term Value from Context-Aware Computing Guruduth Banavar a , Jay Black b , Ramón Cáceres c , Maria Ebling c , Edie Stern d & Joseph Kannry e a The Pervasive Computing Infrastructure Department , IBM T.J. Watson Research Center b The School of Computer Science at the University of Waterloo , Ontario c Research staff members at the IBM T.J. Watson Research Center. d A Senior Technical Staff Member at IBM. e An Assistant Professor in Medicine as well as the Chief of the Division of Clinical Informatics, Director of the Center for Medical Informatics, and Director of IT for the Department of Medicine at Mount Sinai Medical Center. Published online: 21 Dec 2006.

Computers and urban society

Abstract: This brief survey of the use of computers in urban society covers the broad range of activities found in any city. The future scope of applications is limited only by the imagination and inventiveness of future system designers, programmers, analysts, and decision makers. The computer can be, if properly used, with respect for human dignity and civil liberty, a significant factor in improving the efficiency of the urban process. It is expected that the benefits of such computer usage will outweigh the costs and that we may look forward to an expansion of such usage.

Data Management and Allocation in ZBus Methods

Abstract: Data management and allocation is the systematic, efficient storage and retrieval of data. In impedance matrix (ZBUS) algorithms of power engineering, large blocks of data must be stored and accessed; core storage limitations often require that alternate media be employed as storage elements. The quantity of data in such algorithms makes data management philosophy highly desirable. In this paper, the scheduling of data allocation is considered. Expected retrieval time is improved in building ZBUS, and bus ordering is considered. The result is the more efficient use of peripheral storage.

Requirements for a generalized data base management system

Abstract: Several approaches to generalized data base management systems have been documented for the benefit of the data processing community. Perhaps the two most significant reports are Codasyl's Data Base Task Group Report issued in October, 1969, and revised in April, 1971, and the joint GUIDE/SHARE Data Base Management System Requirements. Each report brings with it its own distinct jargon to our already over-developed Tower of Babel. Although the reports often advocate similar solutions to the data management problem, there is a clear difference in emphasis and dominant philosophy. Perhaps the most immediately obvious difference between the two reports is that Codasyl has specified an actual COBOL syntax for the implementation of a data base management system (DBMS) and the GUIDE/SHARE report has simply defined the requirements the data processing community would impose on implementors of DBMS's.

An integrated command and procedural language for drug research

Abstract: A system to handle chemical and biological information has been developed* for use by scientists engaged in drug research. An initial service version of the system has been implemented on a DEC PDP-10 and terminals like the one shown below have been installed at several bio-medical research laboratories. The sys-tem's language includes both English-like commands oriented towards the needs of the scientist (e.g., "display streptomycin") and procedural statements modeled after PL/I. A prominent feature of the system is that it permits the user to integrate the commands with the procedural statements to define complex operations. The commands are designed to permit a scientist, who may not be an experienced computer user, to specify useful operations on his data in a natural way. Through step-by-step use of commands a scientist can, for example, enter a table of experimental data (stored by the system as a structured file), request summary statistics, and plot the data against a theoretical function. Commands deal with entities which are already familiar to medical researchers (graphs, molecules, tables of data, numbers , and text), so that users need not learn a new set of concepts in order to work with the system. An interesting aspect of the command syntax is that the user can specify command arguments by pointing to pictures displayed on his terminal screen. This feature can be used, for example, as a means of entering or updating molecules, graphs, and text. PL/l-like procedural statements can be intermixed with commands in all contexts. It is possible, for instance, to use a DO loop to turn a display of a molecule several times, or to write a procedure which checks the data in a table for consistency. Also, the same user-oriented data types used in commands can be refer-enced in procedures, and portions of these entities can be accessed and changed. A scientist can, for example, write a procedure which declares an argument of type "molecule," uses a command to compute the molecule's three-dimensional conformation, and then uses procedural statements to examine the coordinates of the atoms and determine spatial relationships within the molecule. This integration of the two components of the language on syntactic and semantic levels makes it possible for scientists to program their own extensions to the basic system. The implementation approach selected for the language was to develop, first, a base language which permits the definition of new statements and new data …

A machine independent fortran data management software system for scientific and engineering applications

Abstract: Increasing interest in management information systems had led to much activity in developing techniques and software for data management. Virtually all of the attention has been focused on the specific needs of commerce. Elaborate data structures have been developed for accessing the same information via many different attributes and considerable attention has been given to the acquisition of data from multiple terminals operated by unskilled clerks.

Data Management System Test Methodology Development

Abstract: : The document proposes a methodology to be employed in the testing of data management systems and submits some recommendations for the continued development of a DMS Test Methodology. The intent of the document was first to characterize a data management system by identifying the various attributes that should comprise a DMS and summarize the techniques that can be employed in implementing these capabilities. Secondly, the standard test techniques that can be used to measure the capabilities of the aforementioned attributes were examined and, a DMS Test Methodology was proposed. The report illustrates how the methodology would be employed in the solution of some typical DMS measurement problems. Finally, it was concluded that analysis, benchmark programs, and software monitors were the most useful test techniques available and warrant additional development.

A resource‐oriented time‐sharing monitor

Abstract: A design for a time-sharing monitor on a small-to-medium size computer is presented. A system objective is to achieve good resource utilization and thus be able to do more with limited resources. To this end, some assumptions are made about the user environment (information management applications), and some co-operation is required from application programmers. The design is machine independent, but 360 and Sigma 2 implementations are also described.

Parameters of Information-Seeking Behavior.

Abstract: : The research carried out under this contract represents an attempt to evaluate information seeking under realistic conditions relevant to the design of information systems and the training of information analysts. The research effort resulted in the accomplishment of four major experiments. Experiment I was designed to assess the effects upon information-seeking and decision-making performance of (a) self-versus controlled-pacing of information input, (b) the rate and variability of rate of information arrival, and (c) the number of decision modifications permitted. Experiment II was concerned with the effects upon information-seeking and decision-making performance of (a) the number of decision alternatives, (b) the a priori probabilities of each alternative being correct, and (c) the maount of information available for use in making a decision. Experiment III assessed the effects of (a) the amount of resources available for information purchase, and (b) the amount of information available (with more severe limits than in Experiment II). Experiment IV considered the effects of unknown limits to the availability of information. (Author)

Program Transferability - Data Access Representation for Secondary Storage

Abstract: : This report presents theoretical work which should lead fairly directly to analytical tools which can materially reduce the coat of transferring programs from one computer system to another. A unified, general description of data files and data access methods, called the data access representation, is developed which, it is asserted, is detailed enough to allow efficient use of complex I/O devices, yet simple enough to make possible the development of analytical tools to study and modify programs using the data access representation. As an example of such a tool, an algorithm is developed which will alter a program to compensate for any of a class of data file structure transformations similar to those required to transfer a data file from one I/O device to another. The data management routines of three important operating systems are then considered: IBM OS/360, CDC SCOPE, and HONEYWELL GECOS. Each is described in detail in terms of the data access representation.

A choice of language to support medical research

Abstract: The design of a private medical language was rejected. We did not know at this initial point what such a language should contain. Many programmer man-hours would be spent in discussion of the definition, the philosophy, and the methodology rather than in the implementation of a system. The lack of available experience would make the success of the product questionable. The programs written in such a language would not be as portable as the mobility of medical researchers seemed to require. Even now that languages for medicine are available, it is doubtful that there are language elements which make a language a specifically medical language.