Commentary on James E. Tomayko, “Software as Engineering”
Jim Tomayko’s paper contains much of interest to me, and I think to others, too. It certainly provokes comments from an engineer who has made a livelihood of developing software products. The same questions have been posed to me again and again as the software man in an environment dominated by hardware people. I shall address only the three main themes of Jim’s paper: the art of software engineering, its scientific basis and the role of failure.
KeywordsSoftware Engineering Engineering Knowledge Operational Profile Text Editor Internal Design
Unable to display preview. Download preview PDF.
- 2.Elaine S. Hochman, Bauhaus: Crucible of Modernism (New York, 1997).Google Scholar
- 3.Karl R. Popper, Conjectures and Refutations: The Growth of Scientific Knowledge (London, 1963).Google Scholar
- 4.Michael R. Lyu, Handbook of Software Reliability Engineering (New York, 1996).Google Scholar
- 5.Robert L. Glass, Software Runaways (Englewood Cliffs, N.J., 1997).Google Scholar
- 6.John D. Musa et al., “The Operational Profile,” in Handbook of Software Reliability Engineering, ed. Michael R. Lyu (New York, 1996).Google Scholar