|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| G.-C. Roman, "An Argument in Favor of Mechanized Software Production," IEEE Transactions on Software Engineering, vol. 3, no. 6, pp. 406-415, November, 1977. | |||
| BibTex | x | ||
| @article{ 10.1109/TSE.1977.231173, author = {G.-C. Roman}, title = {An Argument in Favor of Mechanized Software Production}, journal ={IEEE Transactions on Software Engineering}, volume = {3}, number = {6}, issn = {0098-5589}, year = {1977}, pages = {406-415}, doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.1977.231173}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Software Engineering TI - An Argument in Favor of Mechanized Software Production IS - 6 SN - 0098-5589 SP406 EP415 EPD - 406-415 A1 - G.-C. Roman, PY - 1977 KW - standardization KW - Control structure KW - mechanization KW - methodology KW - productivity KW - programming environment KW - program structure KW - transformational components VL - 3 JA - IEEE Transactions on Software Engineering ER - | |||
A new software engineering methodology called program control structuring is proposed. Its development is justified by the need to offer the designer the capability to improve the productivity and quality of software development in the conditions of a "highly imperfect" environment. Such an environment is shown to involve the use of transient and inexperienced programmers, frequent alterations to the design specifications, and continuous development. The philosophy behind program control structuring is that of minimizing the probability of error in the design and implementation of large programs by means of language-and problem-dependent standardization. The particular standardization approach used by program control structuring is shown to provide 1) a program structure that is simple and flexible, readily understood, easily developed, and inexpensively maintained, and 2) a high-quality and partially mechanizable structure-oriented documentation scheme. Subsequently, it is suggested that many of the standards are mechanizable in the immediate future as a necessary condition for achieving higher productivity and improved program quality. Finally, the mechanization of software production is proposed as a step needed to precede the development of automatic program generation systems.
Index Terms:
standardization, Control structure, mechanization, methodology, productivity, programming environment, program structure, transformational components
Citation:
G.-C. Roman, "An Argument in Favor of Mechanized Software Production," IEEE Transactions on Software Engineering, vol. 3, no. 6, pp. 406-415, Nov. 1977, doi:10.1109/TSE.1977.231173
Usage of this product signifies your acceptance of the Terms of Use.

