Ackerman, A. F., & Acharya, S. (2012, June), Software Engineering Education Needs More Engineering  Paper presented at 2012 ASEE Annual Conference & Exposition, San Antonio, Texas. 10.18260/1-2--21923

\bibitem{asee_peer_21923}
  Ackerman, A. F., \& Acharya, S. (2012, June), \emph{Software Engineering Education Needs More Engineering}
  Paper presented at 2012 ASEE Annual Conference \& Exposition, San Antonio, Texas.
  10.18260/1-2--21923

A. Frank Ackerman and Sushil Acharya.  "Software Engineering Education Needs More Engineering".  2012 ASEE Annual Conference & Exposition, San Antonio, Texas, 2012, June.  ASEE Conferences, 2012.  https://peer.asee.org/21923 Internet.  11 Jan, 2025

\bibitem{asee_peer_21923}
  A. Frank Ackerman and Sushil Acharya.
  "Software Engineering Education Needs More Engineering".
  \emph{2012 ASEE Annual Conference \& Exposition, San Antonio, Texas, 2012, June}.
  ASEE Conferences, 2012.
  https://peer.asee.org/21923 Internet.  11 Jan, 2025

@INPROCEEDINGS{asee_peer_21923
author = "A. Frank Ackerman and Sushil Acharya"
title = "Software Engineering Education Needs More Engineering"
booktitle = "2012 ASEE Annual Conference \& Exposition"
year = "2012"
month = "June"
address = "San Antonio, Texas"
publisher = "ASEE Conferences"
note = {https://peer.asee.org/21923}
number = {10.18260/1-2--21923}
}

TY  - CPAPER
AB  -             Software Engineering Education Needs More EngineeringThe term “software engineering” first appeared in the professional literature in the proceedingsof the North Atlantic Treaty Organization (NATO) conference in 1976. At that conference it wasrecognized that something more than computer science and programming was necessary tosuccessfully build the ever larger and more complex software systems that were required fordefense, government, and industry. These systems had become just as costly and took just aslong to build, test, install, and maintain as a battleship, a refinery, or a census. In fact, thecomputers and software that controlled these large systems were becoming ever more critical tothe success of these traditional systems or processes. The art of computer programming haddeveloped rapidly in academic departments and research laboratories without any associationwith traditional engineering. It was natural then, to approach the “software problem” by applyingtraditional engineering practices. Thus was “software engineering” born. This paper willconsider each of the major engineering practices in turn and evaluate the extent to which eachpractice is taught in academic software engineering programs. The IEEE/ACM, SoftwareEngineering 2004, Curriculum Guidelines for Undergraduate Degree Programs in SoftwareEngineering will be used to study recommended courses and knowledge areas. This paper willreport on the extent to which each practice is actually performed in industry in so far as suchpractices have been reported in the literature. It will be shown that while much progress has beenmade in applying traditional engineering practices to software engineering, we are not quite yetat the point where “software engineers” can be admitted to the ranks of professional engineers. Inaddition we will discuss what we need to do in academia to close the gap between softwareengineers and professional engineers.
AU  - A. Frank Ackerman
AU  - Sushil Acharya
CY  - San Antonio, Texas
DA  - 2012/06/10
PB  - ASEE Conferences
TI  - Software Engineering Education Needs More Engineering
UR  - https://peer.asee.org/21923
DO  - 10.18260/1-2--21923
ER  -