The Unix Progamming Environment

Kernighan, Brian W.; Mashey, John R.

doi:10.1109/c-m.1981.220408

Cited by 70 publications

(7 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The earliest "environments" were little more than small collections of stand-alone tools that could be used in a loosely coordinated fashion to help accomplish software engineering goals. Unix [36] is a good example of such an environment. It provides tools, like editors, compilers, debuggers, and other utilities (e.g., awk, sed, grep, find), whose inputs and outputs can be interconnected loosely, at the developer's discretion, via pipes and redirection.…”

Section: A Brief Historymentioning

confidence: 99%

Software engineering tools and environments

Ossher

Harrison

Tarr

2000

Proceedings of the Conference on the Future of Software Engineering

View full text Add to dashboard Cite

The development of methodologies, formalisms, and tool and environment support for separation, extraction and integration of concerns. Linguistic and tool support for morphogenic software: software that is malleable for life, sufficiently adaptable to allow context mismatch to be overcome with acceptable effort, repeatedly, as new, unanticipated contexts arise. The development of new methodologies, formalisms, and processes to address nontraditional software lifecycles, and the tool and environment support to facilitate them. The development of new methodologies, formalisms, processes and tool and environment support to address the engineering of software in new, challenging domains, such as pervasive computing and e-commerce. The adoption or adaptation of XML, Enterprise Java Beans and sophisticated message brokering for integration of both tools and commercial applications. The AuthorsBill Harrison has been with IBM in its system development divisions since 1966 and was one of the initial designers of the [then] OS/360 Time-Sharing Option (TSO). Since 1970, he has been associated with the IBM Thomas J. Watson Research Laboratory. His career at IBM has included several periods with different research focus: the design and implementation of operating systems, the design of programming languages, compilers and program analysis and optimization, the design of software development environments exploiting mixed text and graphic styles to improve the human interaction with the a full-life-cycle process of industrial software development. More recently, he has worked on technology for the design and development of component-based software, including co-authoring the Subject-Oriented Programming approach to developing of suites of related applications and application components, Message-Oriented programming for reducing the fragility of object-oriented software by removing the objects from the clients' view of method call, and MessageCentral, a project that aims to provide a technology base for assisting with component integration by automatically creating the interface and conversion glue needed when software components use mismatching definitions for the messages they interchange. Bill received a B.S. degree in Electrical Engineering from MIT, Cambridge, Mass., in 1968, a M.S. degree from Syracuse University, Syracuse, N.Y., in 1973, and a M.Ph. [Master of Philosophy in Computer Science) degree from Syracuse University, Syracuse, N.Y., in 1979. He is the author of several dozen journal and conference papers and presentations and has been active in influencing computer software standards, including ANS X3-273, ISO 13719 and ISO Draft 13719-1, and several adopted OMG Specifications. He holds a Japanese patent (7-21751) for technology in human-interface design and was an IEEE Distinguished Lecturer on Software Environments for the years 1987-1990. 261 Harold Ossher joined the IBM Thomas J. Watson Research Center as a Research Staff Member in 1986. He currently manages a group that conducts research and technology tr...

show abstract

Section: A Brief Historymentioning

confidence: 99%

Software engineering tools and environments

Ossher

Harrison

Tarr

2000

Proceedings of the Conference on the Future of Software Engineering

View full text Add to dashboard Cite

show abstract

“…Examples of loosely integrated environments include SPS [Boeh84], Toolpack [Cowe83], STVOS [Hall80], UNIX [Kern8l], and ARGUS [Stuc83], 4.0…”

Section: Binding the Tools In An Environmentmentioning

confidence: 99%

Characteristics and functions of software engineering environments

Houghton¹,

Wallace²

1985

View full text Add to dashboard Cite

As part of the program to provide information to Federal agencies on software tools for improving quality and productivity in software development and maintenance, data was collected on software engineering environments. Software engineering environments surround their users with software tools necessary for systematic development and maintenance of software. The purpose of this report is to characterize software engineering environments by type and by their relationship to the software life cycle and by their capabilities, limitations, primary users, and levels of support. This report provides examples of existing software engineering environments that are available commercially or in research laboratories. KEYWORDS framing environments; human factors; life cycle coverage; programming environments; software analysis; software engineering; software engineering environments; software support; software tools. FOREWORD Under the Brooks Act, the National Bureau of Standards Institute for Computer Sciences and Technology (ICST) promotes the cost effective selection, acquisition, and utilization of automatic data processing resources within Federal agencies. ICST efforts include research in computer science and technology, direct technical assistance, and the development of Federal standards for data processing equipment, practices, and software.ICST has published several documents on software tools as part of this responsibility and the growing recognition that the use of software tools and software engineering environments can reduce the effort necessary to develop and maintain computer software. The guidance is designed to assist Federal agencies in automating and standardizing their software development and maintenance projects. This report presents the results of the analysis of data and experience accumulated on software engineering environments. It characterizes environments and describes their features to enable readers to gain an understanding of how environments can aid software development and maintenance process. Future ICST documents will provide guidance in selecting and using software engineering environments.Certain commercial products are identified in this paper for clarification of specific concepts. In no case does such identification imply recommendation or endorsement by the National Bureau of Standards, nor does it imply that the material identified is necessarily the best for the purpose.

show abstract

“…This is not to say that there are no good tools. Indeed, there are a number of sophisticated and effective tools [22,27,30] and there are several programming environments, notably Unix [21], INTER-LISP [36], and Multics [II], that include a substantial number of such tools. Our point is that there are few settings in which the tools actually work effectively in harmony with one another and in support of a software development methodology.…”

Section: Software Toolsmentioning

confidence: 99%

The future of programming

Wasserman

Gutz

1982

Commun. ACM

View full text Add to dashboard Cite

The nature of programming is changing. These changes will accelerate as Improved software development practices and more sophisticated development tools and environments are produced. This paper surveys the most likely changes in the programming task and in the nature of software over the short term, the medium term, and the long term.In the short term, the focus is on gaius in programmer productivity through improved tools and hitegrated development environments. In the medium term, programmers will be able to take advantage of libraries of software components and to make use of packages that generate programs automatically for certain kinds of common systems. Over the longer term, the nature of programming will change even more significantly as programmers become able to describe desired functions in a nonprocedural way, perhaps through a set of rules or formal specification languages. As these changes occur, the job of the application programmer will become increasingly analysis-oriented and software developers will be able to attack a large number of application areas which could not previously be addressed effectively.

show abstract

The Unix Progamming Environment

Cited by 70 publications

References 17 publications

Software engineering tools and environments

Software engineering tools and environments

Characteristics and functions of software engineering environments

The future of programming

Contact Info

Product

Resources

About