|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| A.C.L. Barnard, "B74-18 Computer System Organization," IEEE Transactions on Computers, vol. 23, no. 2, pp. 220, February, 1974. | |||
| BibTex | x | ||
| @article{ 10.1109/T-C.1974.223907, author = {A.C.L. Barnard}, title = {B74-18 Computer System Organization}, journal ={IEEE Transactions on Computers}, volume = {23}, number = {2}, issn = {0018-9340}, year = {1974}, pages = {220}, doi = {http://doi.ieeecomputersociety.org/10.1109/T-C.1974.223907}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Computers TI - B74-18 Computer System Organization IS - 2 SN - 0018-9340 SP EP EPD - 220 A1 - A.C.L. Barnard, PY - 1974 KW - null VL - 23 JA - IEEE Transactions on Computers ER - | |||
Historians tell us that in ancient times the usual mode of operation of a Computer System Manufacturer was for an electronic engineer to emerge from his laboratory one day and tell the waiting programmer "Look! Here's our next model!" The engineer then disappeared to work on the next-but-one model, leaving the programmer to work around any deficiencies or awkwardness in the hardware design which had been handed to him. In modern times, the idea that a machine should be designed to fulfil a function, that the intended use of the machine should supply constraints on its design (rather than the converse), has received at least lip service in most quarters. Some manufacturers have even adopted it as a way of life.
Citation:
A.C.L. Barnard, "B74-18 Computer System Organization," IEEE Transactions on Computers, vol. 23, no. 2, pp. 220, Feb. 1974, doi:10.1109/T-C.1974.223907
Usage of this product signifies your acceptance of the Terms of Use.

