“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

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "In the early ‘80’s, there was little interest in the idea of Enterprise Reengineering or and the use of formalisms and …" by John Zachman?
John Zachman photo
John Zachman 23
American computer scientist 1934

Related quotes

August-Wilhelm Scheer photo

“The creation and implementation of integrated information systems involves a variety of collaborators including people from specialist departments, informatics, external advisers and manufacturers. They need clear rules and limits within which they can process their individual sub-tasks, in order to ensure the logical consistency of the entire project. Therefore, an architecture needs to be established to determine the components that make up the information system and the methods to be used to describe it. The ARIS architecture developed in this book is described in concrete terms as an information model within the entity-relationship approach. This information model provides the basis for the systematic and rational application of methods in the development of information systems. It also serves as the basis for a repository in which the enterprise's application - specific data, organization and function models can be stored. The ARIS architecture constitutes a framework in which integrated applications systems can be developed, optimized and converted into EDP - technical implementations. At the same time, it demonstrates how business economics can examine and analyze information systems in order to translate their contents into EDP-suitable form.”

August-Wilhelm Scheer (1941) German business theorist

August-Wilhelm Scheer, I. Cameron (1992) Architecture of integrated information systems: foundations of enterprise modelling. Abstract.

“When software applications became larger and larger, people such as Shaw and Garlan coined the term software architecture. This notion of architecture deals with the key design principles underlying software artefacts. In the 1980s and 1990s, people became aware that the development of information technology (IT) should be done in conjunction with the development of the context in which it was used. This led to the identification of the so-called business/IT alignment problem. Solving the business/IT alignment problem requires enterprises to align human, organizational, informational, and technological aspects of systems. Quite early on, the term architecture was also introduced as a means to further alignment, and thus analyzes and solves business? IT alignment problems, Recently, the awareness emerged that alignment between business an IT is not enough, there are many more aspects in the enterprise in need of alignment. This has led to the use of the term architecture at the enterprise level: enterprise architecture.”

Erik Proper (1967) Dutch computer scientist

Martin Op 't Land, Erik Proper (2009) Enterprise Architecture: Creating Value by Informed Governance. p. 26-27

Grady Booch photo

“Model Driven Architecture is a style of enterprise application development and integration, based on using automated tools to build system independent models and transform them into efficient implementations.”

Grady Booch (1955) American software engineer

Attributed to Grady Booch in: Tarek M. Sobh (2008) Advances in Computer and Information Sciences and Engineering. p. 457

“The Generic Enterprise Reference Architecture and Methodology is about those methods, models and tools which are needed to build the integrated enterprise. The architecture is generic because it applies to most, potentially all types of enterprise. The coverage of the framework spans Products, Enterprises, Enterprise Integration and Strategic Enterprise Management, with the emphasis being on the middle two. The proposal for the architecture follows the architecture itself improving the quality of the presentation and of the outcome. De nitions of Generic Enterprise Reference Architecture, Enterprise Engineering/ Integration Methodology, Enterprise Modelling Languages, Enterprise Models, and Enterprise Modules are given. It is proposed how the above could be developed on the basis of previously analysed architectures (and other results too), such as the Purdue Enterprise Reference Architecture, the GRAI Integrated Methodology, CIM-OSA, and TOVIE.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus and Laszlo Nemes (1996) "A framework to define a generic enterprise reference architecture and methodology." Computer Integrated Manufacturing Systems Vol 9 (3) p. 179

“Enterprise engineering is rooted in both the organizational sciences and the information system sciences. In our current understanding, three concepts are paramount to the theoretical and practical pursuit of enterprise engineering: enterprise ontology, enterprise architecture, and enterprise governance.”

Erik Proper (1967) Dutch computer scientist

Preface
Advances in Enterprise Engineering II (2009)

James Martin (author) photo

“Information Engineering is the application of an interlocking set of formal techniques for the planning, analysis, design, and construction of information systems on the enterprise wide basis or across a major sector of the enterprise.”

James Martin (author) (1933–2013) British information technology consultant and writer

Source: Information Engineering (1989), p. 1; cited in Karl E. Kurbel (2008) The making of information systems [electronic resource]. p. 176

“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 (1934) American computer scientist

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

“CIMOSA provides a Reference Architecture (known as the CIMOSA cube) from which particular enterprise architectures can be derived. This Reference Architecture and the associated enterprise modelling framework are based on a set of modelling constructs, or generic building blocks, which altogether form the CIMOSA modelling languages.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus, Kai Mertins, Günter Schmidt (1998) Handbook on Architectures of Information Systems. p. 244

“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 (1934) American computer scientist

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

Russell L. Ackoff photo

“The effectiveness of any model used to describe and understand behavior of a particular system as a whole ultimately depends on the degree to which that model accurately represents that system. Nevertheless, there have been and are situations in which application of deterministic or animate models to social systems have produced useful results for a short period of time. However, in a longer run, such mismatches usually result in less than desirable results because critical aspects of the social systems were omitted in the less complex model that was used.”

Russell L. Ackoff (1919–2009) Scientist

Ackoff (1999, p. 34) cited in: Michael C. Jackson (2000) Systems Approaches to Management. p. 234.
1990s

Related topics