Software and Software Engineering. Bauer, F. L. SIAM Review, 15(2):469--480, April, 1973. ArticleType: research-article / Issue Title: Part 2: Anniversary Supplement / Full publication date: Apr., 1973 / Copyright © 1973 Society for Industrial and Applied Mathematics![Software and Software Engineering [link]](https://bibbase.org/img/filetypes/link.svg "link")
Paper abstract bibtex First, we give a short account of the preclassical (Babbage, Ludgate) and classical (Zuze, von Neumann, Wilkes) initial steps in establishing programming concepts. The net result of the 1945-1955 decade was a thorough underestimate of the role software would play in the next decade. This decade saw the explosion of the sales of computing machinery and correspondingly a rapidly growing demand for personnel "to be delivered with the computer." Nevertheless, the necessity for sound training was felt and before 1960, at many places steps were undertaken. In the third decade, starting about in 1965, we have the "software crisis." Since programmed systems, unlike hardware systems, do not demand costly raw materials, systems were built bigger and bigger, and, alas, not better. Unreliability, both with respect to deadlines and functional flaws, was one of the prominent net results. Software engineering is a term used to comprise a bundle of techniques and principles which help to overcome the software crisis. To gain ground, we need a better understanding of system behavior. For the decade 1975-1985, which we are approaching, we should hope for fundamental changes. They can only be brought about by education and the software problem should be looked at also as an educational problem. This needs considerable changes in the habits of instructors. A new generation, however, which is now under way at our universities, will be prepared to take over and to make programming a profession, software an industrial product.
@article{bauer_software_1973,
title = {Software and {Software} {Engineering}},
volume = {15},
issn = {0036-1445},
url = {http://www.jstor.org/stable/2028680},
abstract = {First, we give a short account of the preclassical (Babbage, Ludgate) and classical (Zuze, von Neumann, Wilkes) initial steps in establishing programming concepts. The net result of the 1945-1955 decade was a thorough underestimate of the role software would play in the next decade. This decade saw the explosion of the sales of computing machinery and correspondingly a rapidly growing demand for personnel "to be delivered with the computer." Nevertheless, the necessity for sound training was felt and before 1960, at many places steps were undertaken. In the third decade, starting about in 1965, we have the "software crisis." Since programmed systems, unlike hardware systems, do not demand costly raw materials, systems were built bigger and bigger, and, alas, not better. Unreliability, both with respect to deadlines and functional flaws, was one of the prominent net results. Software engineering is a term used to comprise a bundle of techniques and principles which help to overcome the software crisis. To gain ground, we need a better understanding of system behavior. For the decade 1975-1985, which we are approaching, we should hope for fundamental changes. They can only be brought about by education and the software problem should be looked at also as an educational problem. This needs considerable changes in the habits of instructors. A new generation, however, which is now under way at our universities, will be prepared to take over and to make programming a profession, software an industrial product.},
number = {2},
urldate = {2011-04-16TZ},
journal = {SIAM Review},
author = {Bauer, F. L.},
month = apr,
year = {1973},
note = {ArticleType: research-article / Issue Title: Part 2: Anniversary Supplement / Full publication date: Apr., 1973 / Copyright © 1973 Society for Industrial and Applied Mathematics},
pages = {469--480}
}
Downloads: 0
{"_id":"dwG7GFG9QdZEKBuh2","bibbaseid":"bauer-softwareandsoftwareengineering-1973","downloads":0,"creationDate":"2017-01-26T00:06:42.696Z","title":"Software and Software Engineering","author_short":["Bauer, F. L."],"year":1973,"bibtype":"article","biburl":"http://bibbase.org/zotero/quinn_d","bibdata":{"bibtype":"article","type":"article","title":"Software and Software Engineering","volume":"15","issn":"0036-1445","url":"http://www.jstor.org/stable/2028680","abstract":"First, we give a short account of the preclassical (Babbage, Ludgate) and classical (Zuze, von Neumann, Wilkes) initial steps in establishing programming concepts. The net result of the 1945-1955 decade was a thorough underestimate of the role software would play in the next decade. This decade saw the explosion of the sales of computing machinery and correspondingly a rapidly growing demand for personnel \"to be delivered with the computer.\" Nevertheless, the necessity for sound training was felt and before 1960, at many places steps were undertaken. In the third decade, starting about in 1965, we have the \"software crisis.\" Since programmed systems, unlike hardware systems, do not demand costly raw materials, systems were built bigger and bigger, and, alas, not better. Unreliability, both with respect to deadlines and functional flaws, was one of the prominent net results. Software engineering is a term used to comprise a bundle of techniques and principles which help to overcome the software crisis. To gain ground, we need a better understanding of system behavior. For the decade 1975-1985, which we are approaching, we should hope for fundamental changes. They can only be brought about by education and the software problem should be looked at also as an educational problem. This needs considerable changes in the habits of instructors. A new generation, however, which is now under way at our universities, will be prepared to take over and to make programming a profession, software an industrial product.","number":"2","urldate":"2011-04-16TZ","journal":"SIAM Review","author":[{"propositions":[],"lastnames":["Bauer"],"firstnames":["F.","L."],"suffixes":[]}],"month":"April","year":"1973","note":"ArticleType: research-article / Issue Title: Part 2: Anniversary Supplement / Full publication date: Apr., 1973 / Copyright © 1973 Society for Industrial and Applied Mathematics","pages":"469--480","bibtex":"@article{bauer_software_1973,\n\ttitle = {Software and {Software} {Engineering}},\n\tvolume = {15},\n\tissn = {0036-1445},\n\turl = {http://www.jstor.org/stable/2028680},\n\tabstract = {First, we give a short account of the preclassical (Babbage, Ludgate) and classical (Zuze, von Neumann, Wilkes) initial steps in establishing programming concepts. The net result of the 1945-1955 decade was a thorough underestimate of the role software would play in the next decade. This decade saw the explosion of the sales of computing machinery and correspondingly a rapidly growing demand for personnel \"to be delivered with the computer.\" Nevertheless, the necessity for sound training was felt and before 1960, at many places steps were undertaken. In the third decade, starting about in 1965, we have the \"software crisis.\" Since programmed systems, unlike hardware systems, do not demand costly raw materials, systems were built bigger and bigger, and, alas, not better. Unreliability, both with respect to deadlines and functional flaws, was one of the prominent net results. Software engineering is a term used to comprise a bundle of techniques and principles which help to overcome the software crisis. To gain ground, we need a better understanding of system behavior. For the decade 1975-1985, which we are approaching, we should hope for fundamental changes. They can only be brought about by education and the software problem should be looked at also as an educational problem. This needs considerable changes in the habits of instructors. A new generation, however, which is now under way at our universities, will be prepared to take over and to make programming a profession, software an industrial product.},\n\tnumber = {2},\n\turldate = {2011-04-16TZ},\n\tjournal = {SIAM Review},\n\tauthor = {Bauer, F. L.},\n\tmonth = apr,\n\tyear = {1973},\n\tnote = {ArticleType: research-article / Issue Title: Part 2: Anniversary Supplement / Full publication date: Apr., 1973 / Copyright © 1973 Society for Industrial and Applied Mathematics},\n\tpages = {469--480}\n}\n\n","author_short":["Bauer, F. L."],"key":"bauer_software_1973","id":"bauer_software_1973","bibbaseid":"bauer-softwareandsoftwareengineering-1973","role":"author","urls":{"Paper":"http://www.jstor.org/stable/2028680"},"downloads":0,"html":""},"search_terms":["software","software","engineering","bauer"],"keywords":[],"authorIDs":[],"dataSources":["sEHiQiuaak2HNiigP"]}