Pilot: A software engineering case study

Authors:
Thomas R. Horsley;William C. Lynch
Affiliations:
-;-
Venue:
ICSE '79 Proceedings of the 4th international conference on Software engineering
Year:
1979

Citing 7
Cited 6

Early experience with Mesa

Communications of the ACM
Ethernet: distributed packet switching for local computer networks

Communications of the ACM
A technique for software module specification with examples

Communications of the ACM
The impact of mesa on system design

ICSE '79 Proceedings of the 4th international conference on Software engineering
Experience with processes and monitors in Mesa (Summary)

SOSP '79 Proceedings of the seventh ACM symposium on Operating systems principles
An open operating system for a single-user machine

SOSP '79 Proceedings of the seventh ACM symposium on Operating systems principles
Pilot: An operating system for a personal computer (Summary)

SOSP '79 Proceedings of the seventh ACM symposium on Operating systems principles

Pilot: an operating system for a personal computer

Communications of the ACM
Practical use of a polymorphic applicative language

POPL '83 Proceedings of the 10th ACM SIGACT-SIGPLAN symposium on Principles of programming languages
A method of large-scale software development

ICSE '84 Proceedings of the 7th international conference on Software engineering
Experience with a modular typed language: PROTEL

ICSE '81 Proceedings of the 5th international conference on Software engineering
The impact of mesa on system design

ICSE '79 Proceedings of the 4th international conference on Software engineering
A retrospective on the development of Star

ICSE '82 Proceedings of the 6th international conference on Software engineering

Quantified Score

Hi-index	0.02

Visualization

Abstract

Pilot is an operating system implemented in the strongly typed language Mesa and produced in an environment containing a number of sophisticated software engineering and development tools. We report here on the strengths and deficiencies of these tools and techniques as observed in the Pilot project. We report on the ways that these tools have allowed a division of labor among several programming teams, and we examine the problems introduced within each different kind of development programming activity (ie. source editing, compiling, binding, integration, and testing).