John Zachman Quotes

John A. Zachman is an American business and IT consultant, early pioneer of enterprise architecture, Chief Executive Officer of Zachman International , and originator of the Zachman Framework. Wikipedia  

✵ 16. December 1934
John Zachman: 23   quotes 0   likes

Famous John Zachman Quotes

“[Zachman reasons that] an analogous set of architectural representations is likely to be produced in building any complex product.”

Source: A Framework for Information Systems Architecture, 1987, p. 281 as cited in: San Murugesan, Yogesh Deshpande (2001) Web Engineering: Managing Diversity and Complexity of Web. p, 126

“Decentralization without structure is chaos.”

Source: A Framework for Information Systems Architecture, 1987, p. 276 cited in: Robert Mylls (1994) Information engineering: CASE, practices and techniques. p. 8

“Soon, the enterprise of the information age will find itself immobilized if it does not have the ability to tap the information resources within and without its boundaries.”

Source: Extending and Formalizing the Framework for Information Systems Architecture, 1992, p. 613, cited in: Nik Bessis, Fatos Xhafa (2011) Next Generation Data Technologies for Collective Computational Intelligence. p. 84

John Zachman Quotes

“• Top down implies level of detail that is, looking at the highest level of summarization and then decomposing hierarchically to lower levels of detail as required.”

Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 34

“There is a set of architectural representations produced over the process of building a complex engineering product representing the different perspectives of the different participants.”

Source: A Framework for Information Systems Architecture, 1987, p. 283. cited in: Stephen L. Montgomery (1994) Object-oriented information engineering: : analysis, design, and implementation. p. 279

“[In Mr. Zachman's view] the architect's drawings [represent] a transcription of the owner's perceptual requirements.”

In the 1987 article Zachman states: The architect’s drawings are a transcription of the owner’s perceptual requirements.
Source: A Framework for Information Systems Architecture, 1987, p. 278 cited in: David C. Hay (2003) Requirements Analysis: From Business Views to Architecture. p. 5

“To keep the business from disintegrating, the concept of information systems architecture is becoming less of an option and more of a necessity”

Source: A Framework for Information Systems Architecture, 1987, p. 276, cited in: Jaap Schekkerman (2003) How to Survive in the Jungle of Enterprise Architecture. p. 131

“It is not adequate merely to produce running code. In the long term, enterprise value lies in the models themselves. They have intrinsic value in their own right, as they constitute the baseline for managing change”

Zachman cited in: Carol O'Rourke, Neal Fishman, Warren Selkow (2003) Enterprise architecture using the Zachman Framework. p. 538

“The analytical approach employed by both BSP and BISC is "top down". The implications of the words "top down" are multiple and varied, and all apply to these analysis. For instance:”

Top down implies scope - that is, looking at the business as a whole as opposed to looking at pieces or subparts of it.
Business Systems Planning and Business Information Control Study: A comparison, 1982

“Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures. Some examples of such popular offerings include”

Planning Methodologies: Stage Assessment, Critical Success Factors, Strategy Set Transformation, etc.
Design Approaches: Structured Analysis, Entity-Relationship Approaches, etc.
Tools and Techniques"Problem Statement Language/Problem Statement Analyzer (PSL/PSA), Prototype Development Methodology, Structured Analyses and Design Techniques, etc.
From an historical perspective, BSP and BICS likely will be looked back on as primitive attempts to take an explicit, enterprise-level architectural approach to information systems.
Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 32

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

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

Similar authors

Herbert A. Simon photo
Herbert A. Simon 58
American political scientist, economist, sociologist, and p…
Martin Lewis Perl photo
Martin Lewis Perl 9
American scientist
Steve Jobs photo
Steve Jobs 150
American entrepreneur and co-founder of Apple Inc.
Jerome Isaac Friedman photo
Jerome Isaac Friedman 6
American physicist
Richard Feynman photo
Richard Feynman 181
American theoretical physicist
Hans Bethe photo
Hans Bethe 2
German-American nuclear physicist
Bill Gates photo
Bill Gates 92
American business magnate and philanthropist
Robert A. Heinlein photo
Robert A. Heinlein 557
American science fiction author
Reinhold Niebuhr photo
Reinhold Niebuhr 65
American protestant theologian
Douglas Adams photo
Douglas Adams 317
English writer and humorist