COBOL Cripples The Mind!: Academia and the Alienation of Data Processing

This paper writes a social history of the programming language COBOL that focuses on its reception in academia. Through this focus, the paper seeks to understand the contentious relationship between data processing and the academy. In historicizing COBOL, the paper also illuminates the changing nature of the academy-industry-military triangle that was a mainstay of early computing

The impacts and benefits of using CASE tools in the system development life cycle

The basic idea underlying computer-aided software engineering (CASE) technology is to increase a systems developer\u27s productivity by providing a set of well-integrated, labor-saving tools that transform computer-based information systems (CBIS) development into an automated process. Two major issues of interest are addressed by this article. The first issue includes subjects related to the corporate data processing environment when adopting CASE technology for developing CBIS applications. The second issue includes subjects related to examining the impacts and benefits of using CASE technology as an automated development CBIS application tool within the system development life cycle

Portability of large COBOL programs

Issued as Interim report, Semi-annual progress report, Final technical report, and Final fiscal report, Project no.G-36-61

A general framework for positioning, evaluating and selecting the new generation of development tools.

This paper focuses on the evaluation and positioning of a new generation of development tools containing subtools (report generators, browsers, debuggers, GUI-builders, ...) and programming languages that are designed to work together and have a common graphical user interface and are therefore called environments. Several trends in IT have led to a pluriform range of developments tools that can be classified in numerous categories. Examples are: object-oriented tools, GUI-tools, upper- and lower CASE-tools, client/server tools and 4GL environments. This classification does not sufficiently cover the tools subject in this paper for the simple reason that only one criterion is used to distinguish them. Modern visual development environments often fit in several categories because to a certain extent, several criteria can be applied to evaluate them. In this study, we will offer a broad classification scheme with which tools can be positioned and which can be refined through further research.

The feasibility of using TAE as the UIL for the space station and for other internal NASA tasks and projects

This description of the Transportable Applications Executive (TAE) is intended to serve to test the feasibility of its use as the Space Station User Interface Language (SSUIL). TAE was developed by the Space Data and Computing Division, Space and Earth Sciences Directorate of NASA/GSFC, and by Century Computing, Inc. in 1980. TAE is an executive program which ties a system of application programs into a single easily operated whole and supports users' operations of programs through a consistent friendly and flexible interactive user interface. TAE also supplies the interface between the user and the various application programs in a particular computer system. It appears to be an effective user interface for infrequent as well as for expert users

Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 6: Implementation schedule, development costs, operational costs, benefit assessment, impact on company organization, spin-off assessment, phase 1, tasks 3 to 8

A baseline implementation plan, including alternative implementation approaches for critical software elements and variants to the plan, was developed. The basic philosophy was aimed at: (1) a progressive release of capability for three major computing systems, (2) an end product that was a working tool, (3) giving participation to industry, government agencies, and universities, and (4) emphasizing the development of critical elements of the IPAD framework software. The results of these tasks indicate an IPAD first release capability 45 months after go-ahead, a five year total implementation schedule, and a total developmental cost of 2027 man-months and 1074 computer hours. Several areas of operational cost increases were identified mainly due to the impact of additional equipment needed and additional computer overhead. The benefits of an IPAD system were related mainly to potential savings in engineering man-hours, reduction of design-cycle calendar time, and indirect upgrading of product quality and performance