The programmer's workbench—a machine for software development

Article Properties
Abstract
Cite
Ivie, Evan L. “The programmer’s workbench—a Machine for Software Development”. Communications of the ACM, vol. 20, no. 10, 1977, pp. 746-53, https://doi.org/10.1145/359842.359856.
Ivie, E. L. (1977). The programmer’s workbench—a machine for software development. Communications of the ACM, 20(10), 746-753. https://doi.org/10.1145/359842.359856
Ivie EL. The programmer’s workbench—a machine for software development. Communications of the ACM. 1977;20(10):746-53.
Journal Categories
Science
Mathematics
Instruments and machines
Electronic computers
Computer science
Science
Mathematics
Instruments and machines
Electronic computers
Computer science
Computer software
Technology
Electrical engineering
Electronics
Nuclear engineering
Electronics
Computer engineering
Computer hardware
Description

Is a dedicated machine the key to better software development? This paper proposes the concept of a Programmer's Workbench: a specialized computer dedicated solely to software development and maintenance. The author challenges the traditional assumption that development must occur on the same machine as the final system. The paper outlines the general concept of a dedicated workbench, exploring areas where this approach could be beneficial, including improved programming environments and increased efficiency. It argues that separating the development function can lead to significant advantages, particularly when the production machine's environment is inadequate. An operational system utilizing this concept is described, providing a practical example of how a Programmer's Workbench can be implemented. The findings have implications for software engineering, highlighting the potential for specialized tools to enhance productivity and quality in software development projects.

Appearing in Communications of the ACM, this paper addresses a key topic in computer science and software engineering. The concept of a Programmer's Workbench aligns with the journal's mission to publish innovative ideas and practical solutions for the computing community. The article's focus on improving software development efficiency makes it relevant to the journal's readership.

Refrences
Citations
Citations Analysis
The first research to cite this article was titled The Oregon Report Software Engineering: The Turning Point and was published in 1978. The most recent citation comes from a 2008 study titled The Oregon Report Software Engineering: The Turning Point . This article reached its peak citation in 1981 , with 7 citations.It has been cited in 21 different journals. Among related journals, the IEEE Transactions on Software Engineering cited this research the most, with 4 citations. The chart below illustrates the annual citation trends for this article.
Citations used this article by year