John A. Zachman | |
---|---|
Born | December 16, 1934 |
Alma mater | Northwestern University |
Occupation | business and IT consultant |
John A. Zachman (born December 16, 1934) is an American business and IT consultant, [1] early pioneer of enterprise architecture, Chief Executive Officer of Zachman International (Zachman.com), and originator of the Zachman Framework.
Zachman holds a degree in Chemistry from Northwestern University. He served for a number of years as a line officer in the United States Navy, and is a retired Commander in the U.S. Naval Reserve. [2]
He joined IBM Corporation in 1964 and held various marketing-related positions in Chicago, New York and Los Angeles. He became involved with Strategic Information Planning methodologies in 1970. [3] and in 1973 he was assigned responsibility for the Business Systems Planning (BSP) program in IBM’s Western Region. [4] In 1984 he began to concentrate on Information Systems Architecture. In 1989 at IBM he joined the CASE Support organization of the Application Enabling Marketing Center, where he worked as a consultant in areas of Information Systems Planning and Architecture. [3] He retired at IBM in 1990, having served them for 26 years. Afterwards he co-founded, with Samuel B. Holcman, the Zachman Institute for Framework Advancement, which was discontinued in December, 2008.
He is a Fellow for the College of Business Administration of the University of North Texas. He serves on the Advisory Board for Boston University’s Institute for Leading in a Dynamic Economy (BUILDE), the Advisory Board for the Data Resource Management Program at the University of Washington and the Advisory Board of the Data Administration Management Association International (DAMA-I). [2]
In May 2002 he was awarded a Lifetime Achievement Award from the Advisory Board of the Data Administration Management Association International. [5] He was awarded the 2004 Oakland University, Applied Technology in Business (ATIB), Award for IS Excellence and Innovation. [2]
John Zachman is one of the founding developers of IBM's Business Systems Planning (BSP), [6] and worked on their Executive team planning techniques (Intensive Planning). In 1987 he originated the Zachman Framework a standard for classifying the descriptive representations (models) that comprise enterprise architecture.
Business System Planning (BSP) is a method for analyzing, defining and designing an information architecture of organizations. It was first issued by IBM in 1981, though the initial work on BSP began in the early 1970s. [7] At first, it was for IBM internal use only. Later it was made available to customers [7] and this method became an important tool for many organizations. It is a very complex method dealing with data, processes, strategies, aims and organizational departments which are interconnected.
Business Systems Planning (BSP) and Business Information Control Study (BICS) according to Zachman (1982), [8] are both "information system planning methodologies that specifically employ enterprise analysis techniques in the course of their analyses. Underlying the BSP and BICS analyses are the data management problems that result from systems design approaches that optimize the management of technology at the expense of managing the data". The methodologies have similarities and differences, and strengths and weaknesses. The "choice between using one or the other methodology is strongly influenced by the immediate intent of the study sponsor, tempered by the limiting factors currently surrounding the BICS methodology". [8]
The Zachman Framework according to Zachman (2008) [9] is "a schema - the intersection between two historical classifications that have been in use for literally thousands of years".
More specifically, the Zachman Framework is "an ontology - a theory of the existence of a structured set of essential components of an object for which explicit expressions is necessary and perhaps even mandatory for creating, operating, and changing the object (the object being an Enterprise, a department, a value chain, a "sliver," a solution, a project, an airplane, a building, a product, a profession of whatever)". [9]
According to Zachman, "this ontology was derived from analogous structures that are found in the older disciplines of Architecture/Construction and Engineering/Manufacturing that classify and organize the design artifacts created in the process of designing and producing complex physical products (e.g. buildings or airplanes). It uses a two dimensional classification model based on the six basic interrogatives (What, How, Where, Who, When, and Why) intersecting six distinct perspectives, which relate to stakeholder groups (Planner, Owner, Designer, Builder, Implementer and Worker). The intersecting cells of the Framework correspond to models which, if documented, can provide a holistic view of the enterprise". [10]
Zachman had published three books, several articles [11] and forewords to more than a hundred books on related subjects. A selection:
Articles:
John Florian Sowa is an American computer scientist, an expert in artificial intelligence and computer design, and the inventor of conceptual graphs.
The Zachman Framework is an enterprise ontology and is a fundamental structure for Enterprise Architecture which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications. The first are primitive interrogatives: What, How, When, Who, Where, and Why. The second is derived from the philosophical concept of reification, the transformation of an abstract idea into an instantiation. The Zachman Framework reification transformations are: Identification, Definition, Representation, Specification, Configuration and Instantiation.
Clive Finkelstein is an Australian computer scientist, known as the "Father" of information technology engineering.
The Open Group Architecture Framework (TOGAF) is the most used framework for enterprise architecture as of 2020 that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. TOGAF is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.
A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.
An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.
Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.
Information FrameWork (IFW) is an enterprise architecture framework, populated with a comprehensive set of banking specific business models. It was developed as an alternative to the Zachman Framework by Roger Evernden.
Jean Leonardus Gerardus (Jan) Dietz is a Dutch Information systems researcher, Emeritus Professor of Information Systems Design, and part-time Professor of Enterprise Engineering at the Delft University of Technology, known for the development of the Design & Engineering Methodology for Organizations. and his work on enterprise ontology.
The three-schema approach, or three-schema concept, in software engineering is an approach to building information systems and systems information management that originated in the 1970s. It proposes three different views in systems development, with conceptual modelling being considered the key to achieving data integration.
Enterprise engineering is the body of knowledge, principles, and practices used to design all or part of an enterprise. An enterprise is a complex socio-technical system that comprises people, information, and technology that interact with each other and their environment in support of a common mission. One definition is: "an enterprise life-cycle oriented discipline for the identification, design, and implementation of enterprises and their continuous evolution", supported by enterprise modelling. The discipline examines each aspect of the enterprise, including business processes, information flows, material flows, and organizational structure. Enterprise engineering may focus on the design of the enterprise as a whole, or on the design and integration of certain business components.
A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of a whole system from the perspective of a related set of concerns.
Business systems planning (BSP) is a method of analyzing, defining and designing the information architecture of organizations. It was introduced by IBM for internal use only in 1981, although initial work on BSP began during the early 1970s. BSP was later sold to organizations. It is a complex method dealing with interconnected data, processes, strategies, aims and organizational departments.
Enterprise architecture planning (EAP) in enterprise architecture is the planning process of defining architectures for the use of information in support of the business and the plan for implementing those architectures.
NIST Enterprise Architecture Model is a late-1980s reference model for enterprise architecture. It defines an enterprise architecture by the interrelationship between an enterprise's business, information, and technology environments.
Steven Howard Spewak was an American management consultant, author, and lecturer on enterprise architectures, known for the development of Enterprise Architecture Planning (EAP).
The first publication to use the exact term enterprise architecture was a National Institute of Standards Special Publication on the challenges of information system integration. The overview states "This panel addressed the role of architectures and standards in support of management throughout an enterprise."
Jaap Schekkerman is a Dutch computer scientist and founder of the Institute For Enterprise Architecture Developments (IFEAD) in the Netherlands. He is particularly known for his 2003 book How to Survive in the Jungle of Enterprise Architecture in which he compared 14 Enterprise Architecture Frameworks.
Roger Evernden is a British enterprise architect, musician, composer, writer and speaker.
The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.
Wikiquote has quotations related to: John Zachman |