John Zachman: Architecture

John Zachman is American computer scientist. Explore interesting quotes on architecture.
John Zachman: 46 quotes0 likes

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

John Zachman

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

“In the early ‘80’s, there was little interest in the idea of Enterprise Reengineering or and the use of formalisms and models was generally limited to some aspects of application development within the Information Systems community. The subject of "architecture" was acknowledged at that time, however, there was little definition to support the concept. This lack of definition precipitated the initial investigation that ultimately resulted in the "Framework for Information Systems Architecture." Although from the outset, it was clear that it should have been referred to as a "Framework for Enterprise Architecture," that enlarged perspective could only now begin to be generally understood as a result of the relatively recent and increased, worldwide focus on Enterprise "engineering."”

John Zachman

Source: Concepts of the Framework for Enterprise Architecture, 1993, p. 1

“The older disciplines of Architecture and Manufacturing have accumulated considerable bodies of product knowledge through disciplined management of the "product definition" design artifacts. This has enabled enormous increases in product sophistication and the ability to manage high rates of product change over time. Similarly, disciplined production and management of "Enterprise definition" (i. e. the set of models identified in the Framework for Enterprise Architecture) should provide for an accumulation of a body of Enterprise knowledge to facilitate enormous increases in Enterprise sophistication and accommodation of high rates of Enterprise change over time.”

John Zachman

Source: Concepts of the Framework for Enterprise Architecture, 1993, p. 3

“It is only the advent of an automated model storage facility or repository that brings any of this into the realm of feasibility and makes architecture a reality. It does not mean to suggest that all of these ideas will be immediately available in any particular repository product. It only means that they come into the realm of feasibility as repository technology becomes a reality.”

John Zachman

Source: Extending and Formalizing the Framework for Information Systems Architecture, 1992, p. 615

“(Enterprise Architecture is) the set of descriptive representations (i. e., models) that are relevant for describing an Enterprise such that it can be produced to management's requirements (quality) and maintained over the period of its useful life.”

John Zachman

Zachman (1987) cited in: Antonio Laganà, Marina L. Gavrilova, Vipin Kumar (2004) Computational Science and Its Applications -- ICCSA 2004. p. 604

“A significant observation regarding… architectural representations is that each is of a different nature than the others. They are not merely a set of representations, each of which is an increasing level of detail than the previous one. Level of detail is an independent variable, varying within each architectural representation.”

John Zachman

Zachman (1986) as cited in: Peter Bernus, Kai Mertins, Günter Schmidt (2005) Handbook on Architectures of Information Systems. p. 544

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

John Zachman

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

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

John Zachman

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

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

John Zachman

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

“The world contains entities, processes, locations, people, times, and purposes. Computer systems are filled with bits, bytes, numbers, and the programs that manipulate them. If the computer is to do anything useful, the concrete things in the world must be related to the abstract bits in the computer. Zachman’s framework for information systems architecture (ISA) makes that link. It provides a systematic taxonomy of concepts for relating things in the world to the representations in the computer.”

John Zachman

Source: Extending and Formalizing the Framework for Information Systems Architecture, 1992, p. 590

“Issues of quality, timeliness and change are the conditions that are forcing us to face up to the issues of enterprise architecture. The precedent of all the older disciplines known today establishes the concept of architecture as central to the ability to produce quality and timely results and to manage change in complex products. Architecture is the cornerstone for containing enterprise frustration and leveraging technology innovations to fulfill the expectations of a viable and dynamic Information Age enterprise.”

John Zachman

Source: Enterprise Architecture: The Issue of The Century, 1997, p. 1-2

“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