|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| N. Prywes, "Preparing for Future Needs," Computer, vol. 8, no. 6, pp. 70-72, June, 1975. | |||
| BibTex | x | ||
| @article{ 10.1109/C-M.1975.218999, author = {N. Prywes}, title = {Preparing for Future Needs}, journal ={Computer}, volume = {8}, number = {6}, issn = {0018-9162}, year = {1975}, pages = {70-72}, doi = {http://doi.ieeecomputersociety.org/10.1109/C-M.1975.218999}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - Computer TI - Preparing for Future Needs IS - 6 SN - 0018-9162 SP70 EP72 EPD - 70-72 A1 - N. Prywes, PY - 1975 KW - null VL - 8 JA - Computer ER - | |||
Developments now pending will alter the character of SP, as we presently know it, beyond recognition. SP is essentially a discipline for a programming shop that turns out programs in response to assignments. It enables better planning and control of software development work and improves productivity of the programmers. New technology will alter the roles of the chief programmer and the members of his team.
Citation:
N. Prywes, "Preparing for Future Needs," Computer, vol. 8, no. 6, pp. 70-72, June 1975, doi:10.1109/C-M.1975.218999
Usage of this product signifies your acceptance of the Terms of Use.

