“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

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

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 "With increasing size and complexity of the implementations of information systems, it is necessary to use some logical …" by John Zachman?

John Zachman 23

American computer scientist 1934

Related quotes

“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.

“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

Fred Brooks (1931) American computer scientist

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.

“General systems theory (in the narrow sense of the term) is a discipline concerned with the general properties and laws of “systems”. A system is defined as a complex of components in interaction, or by some similar proposition. Systems theory tries to develop those principles that apply to systems in general, irrespective of the nature of the system, of their components, and of the relations or “forces” between them. The system components need not even be material, as, for example, in the system analysis of a commercial enterprise where components such as buildings, machines, personnel, money and “good will” of customers enter.”

Ludwig von Bertalanffy (1901–1972) austrian biologist and philosopher

Source: 1960s, Robots, Men and Minds (1967), p. 69

“In computer design three levels can be distinguished: architecture, implementation and realisation; for the ﬁrst of them, the following working deﬁnition 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

“Model Driven Architecture is a style of enterprise application development and integration, based on using automated tools to build system independent models and transform them into efficient implementations.”

Grady Booch (1955) American software engineer

Attributed to Grady Booch in: Tarek M. Sobh (2008) Advances in Computer and Information Sciences and Engineering. p. 457

“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

“[In the year 1957] I have just returned from an exciting meeting of the American Society for Engineering Education where I heard a paper on the new discipline of systems engineering. It is no longer sufficient for engineers merely to design boxes such as computers with the expectation that they would become components of larger, more complex systems. That is wasteful because frequently the box component is a bad fit in the system and has to be redesigned or worse, can lead to system failure. We must learn how to design large-scale, complex systems from the top down so that the specification for each component is derivable from the requirements for the overall system. We must also take a much larger view of systems. We must design the man-machine interfaces and even the system-society interfaces. Systems engineers must be trained for the design of large-scale, complex, man-machine-social systems.”

A. Wayne Wymore (1927–2011) American mathematician

Systems Movement: Autobiographical Retrospectives (2004)

“The architecture of a system can be defined as the functional appearance of the system to the user.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Blaauw (1972) cited in: Gerritt A Blaauw (1976) Digital system implementation. p. 6

“Architecture is defined as the art and science of creating buildings. Systems engineering may be similarly defined as the art and science of creating systems.”

Derek Hitchins (1935) British systems engineer

Source: Advanced Systems Thinking, Engineering and Management (2003), p. 309; partly cited in: Kurt A. Richardson, Wendy J. Gregory, Gerald Midgley (2006) Systems Thinking and Complexity Science. p. 39

“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.”

Help us to complete the source, original and additional information

John Zachman 23

Related quotes

Related topics