The Community for Technology Leaders
RSS Icon
Issue No.04 - October-December (1997 vol.19)
pp: 5-17
<p><it>In previous centuries, several technical fields that are now engineering disciplines exhibited problems analogous to those frequently observed in software development today. This paper presents selected examples of experiences from some of those fields, especially electrical telegraphy and telephony during the second half of the 19th and the early 20th centuries, and compares them with difficulties, major mistakes, and so on arising in software development today. It is the thesis of this paper that software development today is in a pre-engineering phase analogous in many respects to the pre-engineering phases of the now traditional engineering disciplines. From observations regarding similarities between experiences in those fields in the past and software development today, questions are raised regarding lessons software developers might learn from those earlier experiences of others—in particular, from the solutions they found to their problems. Some answers are suggested.</it></p>
Robert L. Baber, "Comparison of Electrical "Engineering" of Heaviside's Times and Software "Engineering" of Our Times", IEEE Annals of the History of Computing, vol.19, no. 4, pp. 5-17, October-December 1997, doi:10.1109/85.627895
1. R.L. Baber, Software Reflected: The Socially Responsible Programming of Our Computers.Amsterdam: North-Holland, 1982.
2. R.L. Baber, Praktische Anwendbarkeit mathematisch rigoroser Methoden zum Sicherstellen der Programmkorrektheit, Reihe Programmierung komplexer Systeme/PKS. Berlin: Walter de Gruyter, 1995.
3. C. Borgenstam and A. Sandström, Why Wasa Capsized, Wasa Studies 13, Statens sjöhistoriska museum, Stockholm, no dategiven (1984?).
4. G. Buchheim and R. Sonnemann eds., Lebensbilder von Ingenieurwissenschaftlern.Basel: Birkhäuser, 1989.
5. K. Fitzgerald, "Vulnerability Exposed in AT&T's 9-Hour Glitch," The Institute (a news supplement toIEEE Spectrum), vol. 14, no. 3, Mar. 1990.
6. R.W. Floyd, "Assigning Meanings to Programs," Proc. Symp. Applied Mathematics, Amer. Mathematical Soc., vol. 19, pp. 19-32,Providence, R.I., 1976.
7. H. Freitag ed., Electrical Engineering: The Second Century Begins.New York: IEEE Press, 1986.
8. C.A.R. Hoare, "An Axiomatic Basis for Computer Programming," Comm. ACM, 1969.
9. Inquiry Board, Ariane 5 Flight 501 Failure, Report by the Inquiry Board,Paris, July19 1996.
10. E. Joyce, "Software Bugs: A Matter of Life and Liability," Datamation, pp. 88-92, May15 1987.
11. C. Kaps, "Stundenlang kein Klingeln," Frankfurter Allgemeine Zeitung, S. 12, June28 1991.
12. Nancy G. Leveson and Clark S. Turner, "An Investigation of Therac-25 Accidents," IEEE Computer, pp. 18-41, July 1993.
13. J.L. Meriam, Mechanics: Part I Statics.New York: John Wiley&Sons, 1953.
14. moc, "Nachlässigkeit war der Grund für Desaster beim Erstflug derAriane 5," VDI Nachrichten (weekly newspaper of the Assoc. of German Engineers), July26 1996.
15. P.J. Nahin, Oliver Heaviside: Sage in Solitude.New York: IEEE Press, 1988.
16. P.G. Neumann (moderator), "Risks to the Public in Computers and Related Systems," ACM SIGSOFT Software Eng. Notes, various years. Also available on internet at URL
17. J.D. Ryder and D.G. Fink, Engineers&Electrons.New York: IEEE Press, 1984.
18. M. Shaw, "Prospects for an Engineering Discipline of Software," IEEE Software, Nov. 1990, pp. 15-24.
19. M. Thomas, "Should We Trust Computers?" BCS/UNISYS Annual Lecture, BCS, London, July4 1988.
20. K.L. Wildes and N.A. Lindgren, A Century of Electrical Engineering and Computer Science at MIT, 1882-1982.Cambridge, Mass.: MIT Press, 1985, p. 348. Project MAC had wider aims, captured in the alternative version of the acronym, Machine-Aided Cognition, for which see, e.g., Norberg and O'Neill, Transforming Computer Technology, and P.N. Edwards, The Closed World: Computers and the Politics of Discourse in Cold War America. Cambridge, Mass.: MIT Press, 1996.
21. "Softwarefehler kostet US-Airline 50 Millionen," Computerwoche, Sept.23 1988.
78 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool