|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ASCII Text | x | ||
| "Process Definition: Theory and Reality," IEEE Software, vol. 9, no. 6, pp. 103-105, November/December, 1992. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.1992.10068, author = {}, title = {Process Definition: Theory and Reality}, journal ={IEEE Software}, volume = {9}, number = {6}, issn = {0740-7459}, year = {1992}, pages = {103-105}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.1992.10068}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Process Definition: Theory and Reality IS - 6 SN - 0740-7459 SP103 EP105 EPD - 103-105 PY - 1992 KW - software development; software maintenance; General Electric Aerospace; process definition; graphical representation; software maintenance; software quality VL - 9 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.1992.10068
The approach taken by General Electric Aerospace to define the process it uses to develop and maintain software is outlined. It is shown that two major issues in process definition are deciding what information to include and what form of graphical representation to use. The lessons learned in developing and implementing this approach are discussed.
Index Terms:
software development; software maintenance; General Electric Aerospace; process definition; graphical representation; software maintenance; software quality
Citation:
"Process Definition: Theory and Reality," IEEE Software, vol. 9, no. 6, pp. 103-105, Nov.-Dec. 1992, doi:10.1109/MS.1992.10068
Usage of this product signifies your acceptance of the Terms of Use.

