Showing papers on "Implementation published in 1977"
01 Mar 1977
TL;DR: A model of high-performance computers is derived from instruction timing formulas, with compensation for pipeline and cache memory effects, to predict the performance of the IBM 370/168 and the Amdahl 470 V/6 on specific programs.
Abstract: A model of high-performance computers is derived from instruction timing formulas, with compensation for pipeline and cache memory effects. The model is used to predict the performance of the IBM 370/168 and the Amdahl 470 V/6 on specific programs,/and the results are verified by comparison with actual performance. Data collected about program behavior is combined with the performance analysis to highlight some of the problems with high-performance implementations of such architectures.
54 citations
01 Jan 1977
TL;DR: In this article, the authors examined the randomization process in twelve different social reform projects in the fields of health, education, and law, and made recommendations about issues which should be considered by program administrators and researchers before planning and implementing a true experimental evaluation.
Abstract: This study examines the randomization process in twelve different social reform projects in the fields of health, education, and law. All of the programs used the same type of evaluation plan: a true experimental design involving randomization of clients to treatment and control conditions. The implementation of this plan is discussed for each project. In addition, the projects are analyzed in terms of five aspects of the assignment process. The relationships between these aspects and the successful or unsuccessful implementations of the twelve evaluation designs are discussed. Finally, recommendations are made about issues which should be considered by program administrators and researchers before planning and implementing a true experimental evaluation
12 citations
TL;DR: The methodology of top‐down (structured) programming has emerged in the last few years as a practical approach to the problem of developing reliable software systems, but its implications on a specific language, PL/I, are discussed.
Abstract: The methodology of top-down (structured) programming has emerged in the last few years as a practical approach to the problem of developing reliable software systems. The methodology, however, places certain demands on the language used for actual system implementation. In this paper we discuss the implications of these demands on a specific language, PL/I. From this discussion the basic objectives of a PL/I support system are deduced. These objectives deal primarily with: (1) specifying intermodule relationships; (2) propagating module modifications; and (3) maintaining consistency in the realization of abstractions. Finally, the essential elements of a system that realizes these objectives are described.
3 citations
TL;DR: The NAPSS (Numerical Analysis Problem Solving System) project was an attempt to develop an interactive system, with a high‐level language resembling conventional mathematics, for solving problems in numerical analysis.
Abstract: The NAPSS (Numerical Analysis Problem Solving System) project was an attempt to develop an interactive system, with a high-level language resembling conventional mathematics, for solving problems in numerical analysis. This report uses NAPSS as an example to discuss some aspects of the design and implementation of the programming languages and software which comprise problem solving systems. Successful features as well as failures (with alternative proposals) are detailed in the areas of general language management, specific language features and the operating system interface. In general, a massive, coherent implementation of theoretical work being done at the frontiers of research has abundant opportunity for failure.