|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Mary Shaw, "Prospects for an Engineering Discipline of Software," IEEE Software, vol. 7, no. 6, pp. 15-24, November/December, 1990. | |||
| BibTex | x | ||
| @article{ 10.1109/52.60586, author = {Mary Shaw}, title = {Prospects for an Engineering Discipline of Software}, journal ={IEEE Software}, volume = {7}, number = {6}, issn = {0740-7459}, year = {1990}, pages = {15-24}, doi = {http://doi.ieeecomputersociety.org/10.1109/52.60586}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Prospects for an Engineering Discipline of Software IS - 6 SN - 0740-7459 SP15 EP24 EPD - 15-24 A1 - Mary Shaw, PY - 1990 KW - engineering discipline; software engineering; software technology; information processing; economic force; critical applications; development techniques; scientific basis; expertise; routine practice; professional specializations; science; commercial practice; software engineering VL - 7 JA - IEEE Software ER - | |||
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.

