Commentary on James E. Tomayko, “Software as Engineering”

  • Albert Endres
Conference paper

Abstract

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.

Keywords

Dust Pyramid 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Terri Maginnis, “Engineers Don’t Build,” IEEE Software 17/1 (2000): 34–9.CrossRefGoogle Scholar
  2. 2.
    Elaine S. Hochman, Bauhaus: Crucible of Modernism (New York, 1997).Google Scholar
  3. 3.
    Karl R. Popper, Conjectures and Refutations: The Growth of Scientific Knowledge (London, 1963).Google Scholar
  4. 4.
    Michael R. Lyu, Handbook of Software Reliability Engineering (New York, 1996).Google Scholar
  5. 5.
    Robert L. Glass, Software Runaways (Englewood Cliffs, N.J., 1997).Google Scholar
  6. 6.
    John D. Musa et al., “The Operational Profile,” in Handbook of Software Reliability Engineering, ed. Michael R. Lyu (New York, 1996).Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Albert Endres
    • 1
  1. 1.SindelfingenGermany

Personalised recommendations