Prospects for an engineering discipline of software

Although software engineering is not yet a true engineering discipline, it has the potential to become one. Older engineering fields are examined to ascertain the character that software engineering might have. The current state of software technology is discussed, covering information processing as an economic force, the growing role of software in critical applications, the maturity of development techniques, and the scientific basis for software engineering practice. Five basic steps that the software engineering profession must take to become a true engineering discipline are described. They are: understanding the nature of expertise, recognizing different ways to get information, encouraging routine practice, expecting professional specializations, and improving the coupling between science and commercial practice.<<ETX>>

[1]  M. Postan,et al.  Social History of Engineering , 1961, Nature.

[2]  E. A. Avellone,et al.  Marks' Standard Handbook for Mechanical Engineers , 1916 .

[3]  CORPORATE Computer Science and Technology Board,et al.  Scaling up: a research agenda for software engineering , 1990, CACM.

[4]  Hans Straub,et al.  A History of Civil Engineering: An Outline from Ancient to Modern Times , 1964 .

[5]  F. J. Van Antwerpen,et al.  The Origins of Chemical Engineering , 1980 .

[6]  David Lorge Parnas,et al.  Education for computing professionals , 1990, Computer.

[7]  Thomas Estes,et al.  Cultural Literacy: Another View from the University of Virginia@@@Cultural Literacy: What Every American Needs to Know , 1989 .

[8]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[9]  William M. Waite,et al.  Software manual for the elementary functions , 1980 .

[10]  Jr. Brooks F.P..  No Silver Bullet Essence and Accidents of Software Engineering , 1987 .

[11]  Raj Reddy,et al.  Foundations and grand challenges of artificial intelligence , 1988 .

[12]  Kenneth G. Wilson.  Grand challenges to computational science , 1989, Future Gener. Comput. Syst..

[13]  NATO Science Committee , 1958, Nature.

[14]  Samuel C. Florman,et al.  The Existential Pleasures of Engineering , 1976 .

[15]  A B Marmor-Squires,et al.  DoD Related Software Technology Requirements, Practices, and Prospects for the Future , 1984 .

[16]  William F. Furter,et al.  History of chemical engineering , 1980 .

[17]  James Kip Finch,et al.  Engineering and Western civilization , 1951 .

[18]  Mary Shaw,et al.  What a software engineer needs to know. , 1989 .

[19]  Eugene Levin,et al.  Grand challenges to computation science , 1989, CACM.

[20]  Brian Randell,et al.  Software engineering : report on a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October 1968 , 1969 .

[21]  William James Cody,et al.  Software Manual for the Elementary Functions (Prentice-Hall series in computational mathematics) , 1980 .

[22]  E. D. H. join,et al.  Cultural Literacy: What Every American Needs to Know , 1987 .