“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

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 "Although many popular information systems planning methodologies, design approaches, and various tools and techniques d…" by John Zachman?
John Zachman photo
John Zachman23
American computer scientist 1934

Related quotes

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

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

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

“The software architecture of a system or a family of systems has one of the most significant impacts on the quality of an organization's enterprise architecture. While the design of software systems concentrates on satisfying the functional requirements for a system, the design of the software architecture for systems concentrates on the nonfunctional or quality requirements for systems. These quality requirements are concerns at the enterprise level. The better an organization specifies and characterizes the software architecture for its systems, the better it can characterize and manage its enterprise architecture. By explicitly defining the systems software architectures, an organization will be better able to reflect the priorities and trade-offs that are important to the organization in the software that it builds.”

Scott W. Ambler (1966) Canadian software engineer/consultant/author

James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35

“Enterprise Engineering is defined as that body of knowledge, principles, and practices having to do with the analysis, design, implementation and operation of an enterprise. In a continually changing and unpredictable competitive environment, the Enterprise Engineer addresses a fundamental question: “how to design and improve all elements associated with the total enterprise through the use of engineering and analysis methods and tools to more effectively achieve its goals and objectives”…”

Donald H. Liles (1947) American engineer

Source: The Enterprise Engineering Discipline (1996), p. 1

“An enterprise architecture can be thought of as a "blueprint" or "picture" which assists in the design of an enterprise. The enterprise architecture must define three things. First, what are the activities that an enterprise performs? Second, how should these activities be performed? And finally, how should the enterprise be constructed? Consequently, the architecture being developed will identify the essential processes performed by a virtual company, how the virtual company and the agile enterprises involved in the virtual company will perform these processes, and include a methodology for the rapid reconfiguration of the virtual enterprise.”

Donald H. Liles (1947) American engineer

William Barnett, Adrien Presley, Mary Johnson, and Donald H. Liles (1994) "An architecture for the virtual enterprise." Systems, Man, and Cybernetics, 1994.' Humans, Information and Technology'., 1994 IEEE International Conference on. Vol. 1. IEEE, 1994

“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 architecture (EA) promotes the belief that an enterprise, as a complex system, can be designed or improved in an orderly fashion achieving better overall results than ad-hoc organisation and design. EA is a co-operative effort of designers, analysts and managers and uses enterprise models in the process… enterprise models carry meaning. This resulted in requirements for the enterprise engineering process, which—if not met—can limit the viability of the process. The analysis of the same factors resulted in requirements for improved Enterprise Modelling Tools.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus (2003) "Enterprise models for enterprise architecture and ISO9000: 2000." Annual Reviews in Control 27.2 : 211-220.

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

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

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

“In enterprise modelling, we want to define the actions performed within an enterprise, and define constraints for plans and schedules which are constructed to satisfy the goals of the enterprise. This leads to the following set of informal competency questions:”

Mark S. Fox (1952) Canadian computer scientist and Professor of Industrial Engineering

Temporal projection - Given a set of actions that occur at different points in the future, what are the properties of resources and activities at arbitrary points in time?
Planning and scheduling - what sequence of activities must be completed to achieve some goal? At what times must these activities be initiated and terminated?
Execution monitoring and external events - What are the effects of the occurrence of external and unexpected events (such as machine breakdown or the unavailability of resources) on a plan or schedule?
Time-based competition - we want to design an enterprise that minimizes the cycle time for a product. This is essentially the task of finding a minimum duration plan that minimizes action occurrences and maximizes concurrency of activities.
Source: Methodology for the Design and Evaluation of Ontologies (1995), p. 3-4

Related topics