John A. Mills
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.
- 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.Google Scholar
- 2 Brooks. F.P. Jr. The Mythical Man-Month-Essays on Software Engineering. Addison-Wesley. Reading, Mass., 1975. Describes many "real" aspects of developing a large software system, including the idea of system architect. Google ScholarDigital Library
- 3 Gunther. R.C. Management Methodology for Software Product Engineering. Wiley, New York, 1978. Defines the functions of the chief programmer. Google ScholarDigital Library
- 4 Hofstadter. D.R. Godel, Escher, Bach: At1 Eternal Golden Braid. Basic Books. New York. 1979. A philosophical exploration of the relationships among ideas: recursion. isomorphism. perception. etc. Provides food for thought for the system architect. Google ScholarDigital Library
Index Terms
- A pragmatic view of the system architect
Recommendations
Pragmatic research issues confronting HCI practitioners when designing for universal access
Many HCI products exclude potential users unnecessarily. Such exclusion often arises because of a mismatch between designers’ perceptions of the wants and needs of the end-user and their actual wants and needs. Sometimes the mismatch originates from the ...
Pragmatic approach to cost benefit analysis of user centered design
DUXU'13: Proceedings of the Second international conference on Design, User Experience, and Usability: design philosophy, methods, and tools - Volume Part IUser-centered design (UCD) is an effective method for understanding users' needs and improving usability. Introducing UCD to the existing development process increases new development activities, so it is important to analyze the cost benefits of UCD, ...
Reviews
David W. Burry
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 projects during the past six years,” is presented. In a short space, a fairly complicated software development model is detailed. There are no major departures from current thinking on software development. Perhaps as a reflection of the pragmatic viewpoint, there is a refreshing emphasis on “turf” and “accountability.” These are issues which this reviewer feels are often ignored in theoretical treatments. Unfortunately, the author has missed an important element of the pragmatic approach. Funk and Wagnalls' dictionary defines pragmatism as “the doctrine that thought or ideas have value only in terms of their practical consequences, and that results are the sole test of the validity or truth of ones belief.” This paper makes no attempt to apply this pragmatic validity test to the ideas presented. Although the reader easily senses that there are six years of practical experience underlying the author's beliefs, there is little attempt to convince us of their correctness by direct reference to this experience. I would not recommend this paper to someone looking for new ideas or new arguments (pragmatic or theoretical) for current ideas in software development. An individual looking for a short overview of a software development model with a practical orientation may find the paper suitable.
Access critical reviews of Computing literature here
Become a reviewer for Computing Reviews.
Comments