Fernando J. Corbató
- 1 Brooks, F.P., Jr. No silver bullet. IEEE Comput. (Apr. 1987), 10-19. Google Scholar
Digital Library
- 2 Corbat6, FJ. Sensitive issues in the design of multi-use systems. Unpublished lecture transcription of Feb. 1968, Project MAC Memo M-383.Google Scholar
- 3 Corbat6, F.J., and Clingen, C.T. A managerial view of the Multics system development. In Research Directions in Software Technology, P. Wegner, Ed., M.I.T. Press, 1979. (Also published in Tutorial: Software Management, DJ. Reifer, Ed., IEEE Computer Society Press, 1979; Second Ed., 1981; Third Ed., 1986.)Google Scholar
- 4 Corbat6, F.J., Clingen, C.T., and Saltzer, J.H. Multics: The first seven years. In Proceedings of the SJCC (May 1972), pp. 571-583.Google Scholar
- 5 Corbatfi, F.J., Daggett, M.M., and Daley, R.C. An experimental timesharing system. In Proceedings of the Spring Joint computer Conference (May 1962).Google Scholar
- 6 CorbatO, F.J., Daggett, M.M., Daley, R.C., Creasy, R.}., He!lwig, J.D., Orenstein, R.H., and Horn, L.K. The Compatible Time-Sharing System: A Programmer's Guide. M.i.T. Press, June 1963. Google ScholarDigital Library
- 7 CorbatO, F.J., and Vyssotsky, V.A. Introduction and overview of the Multics system. In Proceedings FJCC (1965).Google ScholarDigital Library
- 8 Daley, R.C. and Neumann, P.G. A general-purpose file system for secondary storage. In Proceedings FJCC (1965).Google ScholarDigital Library
- 9 David, E.E., Jr. and Fano, R.M. Some thoughts about the social implications of accessible computing. In Proceedings FJCC (1965).Google ScholarDigital Library
- 10 Glaser, E.L., Couleur, J.F. and Oliver, G.A. System design of a computer for time-sharing applications. In Proceedings FJCC (1965).Google ScholarDigital Library
- 11 Neumann, P.G., a Multics veteran, has become a major contributor to the literature of computer-related risks. He is the editor of the widelyread network magazine "Risks- Forum," writes the "Inside Risks" column for the CACM, and periodically creates digests in the ACM Software Engineering Notes.Google Scholar
- 12 Organick, E.I. The Multics System: An Examination of ig~ Structure. MIT Press, t972. Google ScholarDigital Library
- 13 Ossanna, J.E, Mikus, L. and Dunten, S.D. Communications and input-output switching in a Multiplex computing system. In Proceedings FJCC (1965).Google ScholarDigital Library
- 14 Parnas, D.L. Software aspects of strategic defense systems. Am. Sci. (Nov. 1985). An excellent critique on the difficulties of producing sohware for large-~ale systems.Google Scholar
- 15 Ritchie, D.M. and Thompson, K. The UNIX time-sharing system. Commun. ACM 17, 7 (July 1974), 365-375. Google ScholarDigital Library
- 16 Vyssotsky, V.A., and Corbat6, F.J. Structure of the Multics Supervisor. In Proceedings FJCC, 1965.Google ScholarDigital Library
Index Terms
- On building systems that will fail
Recommendations
How Do Systems Fail?
2020 Annual Reliability and Maintainability Symposium (RAMS)Summary & ConclusionsModern systems are changing quickly and becoming more complex through increased connectivity, smaller packaging, higher performance requirements, more components, the inclusion of complex software and Artificial Intelligence (...
Fail-in-place network design: interaction between topology, routing algorithm and failures
SC '14: Proceedings of the International Conference for High Performance Computing, Networking, Storage and AnalysisThe growing system size of high performance computers results in a steady decrease of the mean time between failures. Exchanging network components often requires whole system downtime which increases the cost of failures. In this work, we study a fail-...
Reviews
Thomas C. Richards
All systems will fail. The question is not whether some mishap will happen, but rather what to do when it does occur. In this Turing Award address, Corbato´ examines the problems associated with the development of ambitious or complex systems and identifies why they always fail. Sources of complexity that contribute to this failure include the number of personnel required, the levels of management, the lack of willingness to report bad news, and the inability of any one person to understand the complete system. He offers solutions to each of these problems, including simplicity in design, use of metaphors, constrained languages for design, anticipation of errors, design for modification, cross education of team members, and learning from past mistakes. Frenkel's interview, conducted after Corbato´'s Turing Award lecture, complements it. The questions and answers provide a comprehensive overview of the development of the time-sharing systems CTSS and Multics, and a good overview of some of the individuals involved in these efforts. One of the most interesting parts of this interview is the support (or lack of interest) of some of the major computer manufacturers in the 1960s, including GE, IBM, and DEC. The support of Bell Labs for Multics and its eventual disengagement are examined. The relationship between UNIX and Multics is discussed in some detail, as are the problems in the development of these systems. The discussion concludes with an examination of the transition from mainframes to workstations and PCs. This interview will appeal to people interested in the historical development of time-sharing systems.
Access critical reviews of Computing literature here
Become a reviewer for Computing Reviews.
Comments