John Zachman Quotes

21 Sourced Quotes

When the rate of change increases to the point that real time required to assimilate change exceeds the time in with change must be manifest, the enterprise is going to find itself in deep yogurt.

John Zachman
Most programming tools and techniques focus on one aspect or a few related aspects of a system. The details of the aspect they select are shown in utmost clarity, but other details may be obscured or forgotten.

John Zachman
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
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.

John Zachman
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
(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
Business System Planning (BSP) and Business Information Control Study (BICS) are two information system planning study methodologies that specifically employ enterprise analysis techniques in the course of their analysis. Underlying the BSP and BICS analysis are the data management problems that result from systems design approaches that optimize the management of technology at the expense of managing the data.

John Zachman
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
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 architec- ture 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
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. 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. Top down implies perspective - that is, the perspective of the highest levels of management as opposed to the operational levels of management.

John Zachman
John Zachman introduced a framework for information systems architecture (SA) that has been widely adopted by systems analysts and database designers. It provides a taxonomy for relating the concepts that describe the real world to the concepts that describe an information system and its implementation. The ISA framework has a simple elegance that makes it easy to remember, yet it draws attention to fundamental distinctions that are often overlooked in systems design. This paper presents the framework and its recent extensions and shows how it can be formalized in the notation of conceptual graphs.

John Zachman
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
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
The Information Age is unfolding just as predicted by many of the sociological prognosticators of this century. Information issues are on everyone's mind and on multitudes of lips. It is hard to pick up a newspaper or current affairs magazine without seeing a feature on the internet, web pages, e-mail, television terminals or some other new technology. In fact, technology innovation is relentless and escalating and technology stocks continually drive the stock market to high after high. There is no field of human endeavor that is exempt from the onslaught of information technology.

John Zachman
A framework as it applies to enterprises is simply a logical structure for classifying and organising the descriptive representations of an enterprise that are significant to the management of the enterprise as well as to the development of the enterprise's system [with the aim of] rationalising the carious concepts and specifications in order to provide for clarity of professional communication, to allow for improving and integrating development methodologies and tools, and to establish credibility and confidence in the investment of systems resources.

John Zachman
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

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

John Zachman
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
Business System Planning (BSP) and Business Information Control Study (BICS) are representative of enterprise analysis tools that are growing in importance and are likely to become mandatory for ant business that continues to grow and evolve.

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

John Zachman
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