ACM Home Page
Please provide us with feedback. Feedback
A pragmatic view of the system architect
Full text PdfPdf (1.15 MB)
Source
Communications of the ACM archive
Volume 28 ,  Issue 7  (July 1985) table of contents
Pages: 708 - 717  
Year of Publication: 1985
ISSN:0001-0782
Author
John A. Mills  Bell Communications Research, Piscataway, NJ
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 54,   Citation Count: 3
Additional Information:

abstract   references   cited by   index terms   review  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/3894.3897
What is a DOI?

ABSTRACT

A whole-system designer, fire fighter, mediator, and jack-of-all-trades, the system architect brings unity and continuity to a development project—offsetting the inevitable compartmentalization of modern modular designs.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Aron. I.D. The Program Developmtvt Process: Part II, the Programming Team. Addison-Wesley, Reading, Mass.. 1983. Establishes the system architect as designer of the framework and externals of a system.
 
2
 
3
 
4



REVIEW

"David W. Burry : Reviewer"

As one would expect from the title, “no attempt is made in this paper to be theoretical.” Instead, a view of the role of the system architect, “based on the author's own experience as a system architect on three separate projec  more...