“The term architecture is used here to describe the attributes of a system as seen by the programmer, i. e., the conceptual structure and functional behavior, as distinct from the organization of the data flow and controls, the logical design, and the physical implementation. i. Additional details concerning the architecture”

—  Fred Brooks

Gene Amdahl, Gerrit Blaauw, and Fred Brooks (1964) "Architecture of the IBM System." in: IBM Journal of Research and Development Vol 8 (2) p. 87-101.

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "The term architecture is used here to describe the attributes of a system as seen by the programmer, i. e., the concept…" by Fred Brooks?
Fred Brooks photo
Fred Brooks 20
American computer scientist 1931

Related quotes

Gene Amdahl photo

“The term architecture is used here to describe the attributes of a system as seen by the programmer, i. e., the conceptual structure and functional behavior, as distinct from the organization of the data flow and controls, the logical design, and the physical implementation. i. Additional details concerning the architecture”

Gene Amdahl (1922–2015) American physicist

Gene Amdahl, Gerrit Blaauw, and Fred Brooks (1964) " Architecture of the IBM System http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.72.7974&rep=rep1&type=pdf." in: IBM Journal of Research and Development Vol 8 (2) p. 87-101

Gerrit Blaauw photo

“The design of a digital system starts with the specification of the architecture of the system and continues with its implementation and its subsequent realisation… the purpose of architecture is to provide a function. Once that function is established, the purpose of implementation is to give a proper cost-performance and the purpose of realisation is to build and maintain the appropriate logical organisation.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Source: Specification of Digital Systems (1978), p. 29

“The software architecture of a system or a family of systems has one of the most significant impacts on the quality of an organization's enterprise architecture. While the design of software systems concentrates on satisfying the functional requirements for a system, the design of the software architecture for systems concentrates on the nonfunctional or quality requirements for systems. These quality requirements are concerns at the enterprise level. The better an organization specifies and characterizes the software architecture for its systems, the better it can characterize and manage its enterprise architecture. By explicitly defining the systems software architectures, an organization will be better able to reflect the priorities and trade-offs that are important to the organization in the software that it builds.”

Scott W. Ambler (1966) Canadian software engineer/consultant/author

James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35

“With increasing size and complexity of the implementations of information systems, it is necessary to use some logical construct (or architecture) for defining and controlling the interfaces and the integration of all of the components of the system.”

John Zachman (1934) American computer scientist

Source: A Framework for Information Systems Architecture, 1987, p. 276, cited in: CM Pereira (2004), "A method to define an Enterprise Architecture using the Zachman Framework". in: SAC '04 Proceedings of the 2004 ACM symposium on Applied computing. pp. 1366-1371

Gerrit Blaauw photo

“In computer design three levels can be distinguished: architecture, implementation and realisation; for the first of them, the following working definition is given: The architecture of a system can be defined as the functional appearance of the system to the user, its phenomenology.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Although the term architecture was introduced only ten years ago in computer technology (Buchholz), the concept of architecture is as old as the use of mechanism by man. When a child is taught to look at a clock, it is taught the architecture of the clock. It is told to observe the position of the short and the long hand and to relate these to the hours and the minutes. Once it can distinguish the architecture from the visual appearance, it can tell time as easily from a wrist watch as from the clock on the church tower.
The inner structure of a system is not considered by the architecture: we do not need to know what makes the clock tick, to know what time it is. This inner structure, considered from a logical point of view, will be called the implementation, and its physical embodiment the realisation.
Source: Computer architecture (1972), p. 154

August-Wilhelm Scheer photo

“The creation and implementation of integrated information systems involves a variety of collaborators including people from specialist departments, informatics, external advisers and manufacturers. They need clear rules and limits within which they can process their individual sub-tasks, in order to ensure the logical consistency of the entire project. Therefore, an architecture needs to be established to determine the components that make up the information system and the methods to be used to describe it. The ARIS architecture developed in this book is described in concrete terms as an information model within the entity-relationship approach. This information model provides the basis for the systematic and rational application of methods in the development of information systems. It also serves as the basis for a repository in which the enterprise's application - specific data, organization and function models can be stored. The ARIS architecture constitutes a framework in which integrated applications systems can be developed, optimized and converted into EDP - technical implementations. At the same time, it demonstrates how business economics can examine and analyze information systems in order to translate their contents into EDP-suitable form.”

August-Wilhelm Scheer (1941) German business theorist

August-Wilhelm Scheer, I. Cameron (1992) Architecture of integrated information systems: foundations of enterprise modelling. Abstract.

Dana Arnold photo

“‘Architecture’ may at first appear to be a more fixed and finite term. It has a threedimensional, tangible, useable form. But questions remain about what can be considered architecture and what cannot, and by this I mean that we usually understand architecture to incorporate aesthetic as well as functional consideration into its structure. Anything that does not fall into this category can be described as ‘just a building’. This may seem too simple. Can architecture be determined solely by the use of refined architectural style – high or polite architecture instead of vernacular?”

Dana Arnold (1961) Middlessex uni prof

Source: Reading Architectural History (2002), Ch. 1 : Reading the past : What is architectural history?

Frank Lloyd Wright photo

“So here I stand before you preaching organic architecture: declaring organic architecture to be the modern ideal.”

Frank Lloyd Wright (1867–1959) American architect (1867-1959)

An Organic Architecture (1939)

Freeman Dyson photo

“The bottom line for mathematicians is that the architecture has to be right. In all the mathematics that I did, the essential point was to find the right architecture. It's like building a bridge. Once the main lines of the structure are right, then the details miraculously fit. The problem is the overall design.”

Freeman Dyson (1923) theoretical physicist and mathematician

"Freeman Dyson: Mathematician, Physicist, and Writer". Interview with Donald J. Albers, The College Mathematics Journal, vol 25, no. 1, (January 1994)

“Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of a company's operation model… The key to effective enterprise architecture is to identify the processes, data, technology, and customer interfaces that take the operating model from vision to reality.”

Jeanne W. Ross (1958) American computer scientist

Source: Enterprise architecture as strategy, 2006, p. 47

Related topics