John Zachman: Enterprise

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

“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

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

“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

Zachman (1994) cited in: Ronald G. Ross (2003) Principles of the Business Rule Approach. p. 35

“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

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

“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

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

“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

Zachman cited in: Egon Berghout and Dan Remenyi, Egon Berghout (2003) Proceedings of the 10th European Conference on Information Technology Evaluation - 2003. p. 503
In this quote the "framework" refers to the Zachman Framework

“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

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

“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 cited in: Carol O'Rourke, Neal Fishman, Warren Selkow (2003) Enterprise architecture using the Zachman Framework. p. 538

“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

“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